Need for Speed III, Aboveground Shikoku & TBD Racing Event Open participation
DATE & TIME
Jun 14-15, 6-8PM UTC
OVERVIEW
The ~monthly racing event is back, with further improvements! Join one of the established teams, or go at it alone for the chance at a smaller prize. Take a look at the new racing discord for tips, strategies, and boasting about leaderboards. Stream your gameplay and provide commentary for an extra bonus, regardless of your performance.
For anyone new to racing, the idea is simple: fast ships, short bursts of cruise, judicious use of afterburners and engine kill. Grab yourself a light fighter, pick up a racing engine from a station listed below, and come out onto the track!
DETAILS
Racing Overview
The races will be split into three parts: Warm-up, Qualifiers, and the Main Event. The first race will occur on the Golden Dragon track in Shikoku on Saturday, and the second on the highest voted track on Sunday (vote in the discord).
Warm-up (30 mins): any ships can race to get used to the track and shake off the rust.
Qualifiers (30 mins): registered players/teams race for the whole duration to set the best single lap time they can.
Main Event (up to 30 mins): all participants race for the fastest completion of a set number of laps for the best (fastest) overall time. Everyone can join, but you will only be near the front if you do well during the Qualifiers.
Points are earned both by individuals and teams. The structure is outlined below:
/race solo <lapCount> [raceNum] - immediately starts a solo race. Must have the first ring of the track selected. If there is more than 1 route for the track, specify the number.
/race host [raceNum] - host a race lobby. The host is also a racer. Must have the first ring of the track selected. If there is more than 1 route for the track, specify the number.
/race join [spectator] - joins the lobby of the targeted player (participants work as well as host) as racer(default) or spectator(if specified)
/race setlaps <lapCount> - sets the lap count for the race. Host only
/race start - begins the race. Host only
/race disband - disbands the lobby if the race hasn't started yet. Host only
/race withdraw - removes you from the race and forfeits your standing
/race status - prints real-time stats of the race (times, checkpoints), triggers automatically when the leading player finishes a lap.
/race info - prints info about the race (host name, loop count, participants)
Remember that racing engines are necessary to participate in the races.
Interfering with ongoing races is forbidden. This includes deliberate bumping by the racers.
PvP around the racetracks is forbidden during the event.
RP is not required around the racetracks during the event.
Temporary unstable jump holes will be spawned to connect the racetracks during the event. They do not exist in the roleplay environment.
Rewards
1st place player: 20 mil.
2nd place player: 10 mil.
3rd place player: 5 mil.
All team points will contribute to their Season Score, with rewards (and accolades) to be collected at the end of the Season by the top 8 teams. The current Season is Summer.
Note: players who won individual rewards during the last racing event will only be eligible for team points. The reward money will instead go to the next eligible player on the leaderboard.
Streams
Anyone streaming the event gets 4mil for each day.
Betting
Each of the teams below will have an in-game account where players can send money to bet on the team. The total bet amounts will be updated daily to represent the perceived odds of them doing well. Betting will close before the start of the first race.
Payouts will be sent to the accounts that sent the money, with the amount determined by the latest odds. Odds will be generated based on the bet on each team out of the combined total bet amount across all teams.
E.g. if you bet 1mil on a team with 1/10 odds, you will get 10mil if they win, 5mil if they get second place, 2.5mil if they get third place, and nothing if they place lower.
TEAMS Teams must have at least 2 players. Unique names are encouraged!
TalesofTerror Global RP Event The Wild and The Nomads
DATE & TIME
June 9th - August 10th
OVERVIEW
With the surfacing of Omega-58 and all the horrors that have been nursing within for a decade, the Omegas have become a much less secure region than they already were. Rumors of solitary ships disappearing without any trace or premise have been growing more and more common, with very few brave souls daring to venture into the open space without a pair of hired guns or a reliable partner. Whispers in the crowd grow tense as some individuals with wild imagination begin to paint a picture of all the inhumane horrors that the kidnapped pilots might be getting subjected to and spreading them as folktales and murmur. Efforts conducted by superiors of local groups and gangs to suppress such thoughts don't ever truly come to total fruition, and fewer those who deem it worth the time and risk to explore those rumors in hopes of uncovering some hidden mystery behind them.
Yet in every folktale there is a bit of truth. The tarnished screams of metal and matter of The Midden will never be heard by the rest of the Sector, yet they echo still from within the perverted technological amalgams that emerge from Omega-58.
DETAILS
RULES - READ THEM CAREFULLY
This is an RP event focused around player storybuilding and interaction. The event's topic is "Hybridization of Technology by the Nomads and The Wild".
Participants are required to write a Story for their Hybrid Ship - its origin, how it came into the possession of the Nomads and The Wild and what kind of Hybridization it received. The story can consist of multiple threads on the forums and multiple events taking place in the game.
It is ABSOLUTELY MANDATORY to follow the established canons of Nomad and Wild Lore. You may expand on them, but you may not contradict them. For reference, follow Jammi's Lore Bits on Nomad Infiltration and The Daam-K'Vosh, as well as all the available ingame content about Omega-58.
The part where the ship gets into possession of the Nomads and The Wild must take place ingame and be recited on the Forums, with Visual Evidence (Screenshots (edited or not) or Videos) embedded into the Story itself.
Existing Wild, Nomad and Hybrid characters may participate in the event, but the ship's abduction has to take place during it. The ship cannot already be in their possession, nor will the abductions that happened prior to the Event's starting date count.
Players are encouraged to pre-arrange and script such events, but be warned that if we find your plot to be too convenient. it will not be received too fondly. "I found it in the asteroid field" will not count. Be genuine and give it effort. No need to rush things.
Stories must be submitted for a review after the Event has ran its course using one of the forms below.
Every player may submit only one story for a review. A group of players must choose a player to represent them in a submission form and they may also submit only one story.
Player Factions may opt in for multiple ships in a single submission form, though that will raise the plank of roleplay quality expectations. They may request a max of Four Snubcraft Vessels in a single request, and up to Two Transports, Gunboats or Cruisers. Battleships, Battlecruisers, Bustards, Amaterasus, Longhorns, Bulwarks and Hegemons are exempt from this rule and may only be requested in singular quantity. Player Factions eligible for requests containing multiple ships - Wilde. ; Noth- ; K'Hara|
Capital Assets (Cruisers and Above) can only be included in a story made by a group of players and will require equal roleplaying effort from all the participants. Every participating player must be mentioned in the submission form.
If a Group Submission Template is used, the ship will be shared between all the players included in the template. They and only they may have access to the ship. Further changes will have to be submitted in a Player Request or negotiated with the Staff.
If another player is found to be given access to the ship or/and its assets without consulting or notifying the Staff, the ship and its assets will be deleted, with additional punishments dispensed according to the Staff's discretion. Treat it as you would an SRP ship.
Individual Submission Template:
Code:
Your Ship's Ingame Name: here
Your Ship's Class: here
Relevant Roleplay: [links]
Group Submission Template:
Code:
Names of Players Participating in the Story:
The Ship's Ingame Name:
The Ship's Class:
Relevant Roleplay: [links]
REWARDS
Rather than the amount of things you do, the rewards will be based on the quality of your story. It will be judged by the people who live and breathe Nomad Lore, and the decided quality score will warrant a certain degree of rewards.
Quality Score - Satisfactory
Players who receive a Satisfactory Score may request a Nomad Engine for their ship. Keep in mind that the requested engine must be of the same class as the ship itself (For instance, a Rabisu's Engine for a Valkyrie).
Quality Score - Good
Players who receive a Good Score may request a Nomad Engine for their ship, as well as a set of "ENTROPY" weapons for it if it's a snub. Ships requesting a set of "ENTROPY" codenames will be shiplocked.
Quality Score - Exceptional
Players who receive an Exceptional Score may request a Nomad Engine for their ship and a techcell exempt for Nomad Weapons, as well as a set of "ENTROPY" codenames if the ship in question is a snub. Like with the "Good" score, it will also mean that the ship will have to be locked.
Rewards for Good and Exceptional scores are subject to negotiation.
Q&A Section
Any questions related to the concept or the rules of this event will be answered here. Highly recommend to take a look if you're unsure of what you can and can't do.
Code:
Q: After I receive the Nomad Engine, can I move it to a different ship?
A: No.
Code:
Q: Can a single player participate in multiple stories?
A: Yes. Even if they're writing a story of their own, they can still participate in a group effort.
Code:
Q: Does my ship have to be Wild ID/IFF after its story is written?
A: This goes without saying. Yes. Your ship must be a complete entity within the Wild communion for it to pass.
Code:
Q: I have a ship that I want to use in this event, it's not fresh new and it has an existing story. May it still be subjected to hybridization?
A: Of course! As long as the ship gets into possession of The Nomads and The Wild during the Event, the story will be acceptable.
Code:
Q: Can the ship that is being hybridized be a ship from any human faction?
A: Yes. Any HUMAN faction will do. Gammu AI ships can't be hybridized in the manner the event suggests.
Code:
Q: Is the hybridized ship considered as overt? Do the engines and ENTROPY weapons make it so?
A: Yes, at all times, it is going to be a fully overt vessel.
Code:
Q: Can a Wild character submit their ship for hybridization, or would you rather have a "clean" human be taken, and then converted with their ship?
A: Though an existing Wild character can be a part of the event, the ship itself has to be a fresh catch by the Wilds and/or the Nomads. It could be an existing one, but it can't already be in their possession prior to June 9th.
Code:
Q: For purposes of collective effort, do the players of one group have to be from the same faction? Can only Official Factions participate in this?
A: No! One group can contain players of both Official and Unnoficial factions (i.e. Group 1 that targets a Bismarck can contain characters from both K'Hara| and Noth-). Untagged characters may also participate, unless the group is opting in for a request that contains multiple ships. Then it can only be the players of factions mentioned in the rules, but they can still do it together.
Code:
Q: Is it mandatory for the abduction part to happen in Omega-58?
A: Not at all, it can happen literally anywhere.
This notice is a general warning that explains the server staff’s current position on “PvP baiting”.
2.0 - Every ship must have one ID equipped, and play in a way that represents the role of that ID. Your ID explains what you can do and where. Some IDs have a 'Zone of Influence' (ZOI) where extra actions are permitted. All IDs have a ZOI in systems containing an NPC station of the same affiliation.
IDs that specify a Zone of Influence let you know what you can do and where. The rules also allow you to defend your allies (by NPC diplomacy or group membership), unless you are in a capital ship outside your Zone of Influence.
This warning has been primarily prompted by two recent situations:
Convoys of DTR capital ships regularly roaming outside their ZoI, i.e. Liberty, to “defend “ their smugglers.
LSF capital ships appearing at the Reincarnation siege yesterday, to “defend” the Core there.
PvP baiting is when a player is in a location where they do not have any right to initiate an attack, but either antagonises their opponents into attacking them, or places themselves in a situation / location where it is inevitable that they will be attacked.
This isn’t a new idea, and is something that was severely punished in the past as it is effectively a method of circumventing ID restrictions. While we're not saying that was the intent in the two situations above, they are illustrative of the concept.
This thread serves as a reminder not to do this, as we will be considering future occurrences as breaches of rule 2.0.
Some examples:
A BAF fighter flies to Ile-de-France and repeatedly insults Gallic Navy players until they attack him. This is PvP baiting because he is goading a fight while trying to hide behind “self-defence” rules.
A group of Unioners and Rogue Scyllas raid New Berlin. Even if they do not shoot first, the Rogues are PvP baiting because they are out of ZoI, are flying a ship class that is not allowed to defend allies outside ZoI, and have placed themselves in a situation where combat is inevitable.
A fleet of Corsair battleships sit outside Manhattan to "observe". Despite sending messages that are "polite" / non-antagonizing, this is PvP baiting because they are aware that their presence in such a sensitive location will inevitably provoke an attack.
While resolving outstanding development tickets, it has come to my attention that NPC freelancers currently have no name range defined for large vessels. This is why Freelancer pirate trains spawn with the name "unknown unknown", for example.
I figure it's time we fix this, and as a bit of fun, I'd like to crowdsource some suggestions. This will be the pool of names Freelancer NPC large vessels (transports and gunboats, effectively) will be able to pull from.
Those could be place names from regions Sirius already draws from, i.e. the nations associated with the Houses. Bespoke ship names are also fine, however if I see any memes or anime references, I will move heaven and earth to bring a ban down on your head.
I'm also going to provisionally be adding the prefix IFV for Independent Freelance Vessel (or possibly just a blank space) unless there are any other suggestions.
![[+]](/forums/images/collapse_collapsed.png "[+]")
Point Structure
