Stuttgart Showdown Stuttgart, Cologne, Hamburg, New Berlin, Sigma-13, Honshu, Hokkaido, Kyushu Convoy interception event Farmer's Alliance vs LWB
DATE & TIME
Sep 29, 19:30 UTC
OVERVIEW
In the aftermath of the Rheinland Civil War, Imperial fighters formerly affiliated with the LWB felt abandoned and betrayed. The government they had fought for failed to follow through on their promises to evict Synth from Stuttgart, caving to basic economic reality over ideological purism. Before long, many took up arms again - making a deal with the devil in the process. Envoys from Rheinland went to Kusari to beg the Farmer's Alliance for aid, stressing their mutual goal in destroying Synth's agricultural empire.
The Alliance agreed, however there were strings. The LWB were not equal partners in this relationship; the FA provided weapons, ships and credits, scrupulously laundered to remove Samura's fingerprints. But they also called the shots. FA commanders were installed, and local LWB insurgents quickly found that they were little more than pawns, protecting the interests of Kyushu rather than the farmers of Stuttgart. Resentment slowly simmered, but came to a boil through the Treaty of Oerlikon. This free trade agreement allowed Gallic foodstuffs to flood into Rheinland, instigating a fierce price war with Synth.
Synth is burning cash hand over fist to lock Gallic agricorps out of the Rheinland market. This suits the Farmer's Alliance perfectly well, as the increased focus on competition within Rheinland is throttling exports to Kusari. The FA have explicitly banned the LWB from targeting Gallic food shipments due to this. It is having a devastating effect on the few remaining independent farmers of Stuttgart who don't have the reserves for this race to the bottom. Resentment becomes rage. Already there have been instances of fragging. FA commanders unexpectedly killed when munitions detonate aboard their ships, or components fail.
The Farmer's Alliance feel their control is slipping - they need to make an example. That example comes when Sabine Schroder stabs to death a Farmer's Alliance technician aboard Darmstadt. She is subdued and dragged away to a moored transport. The local Alliance commander declares that she is to be transported to Kagoshima Depot, where the Alliance's Elders will render judgement - likely a public execution. Schroder becomes a lightning rod for the LWB's resentment, impotence and rage. The crews of the cruisers Schwarzwald and Greifswald revolt, vowing to free Schroder and liberate their movement from Kusari's yoke. DETAILS
Incentives:
A Farmer's Alliance Raba frigate will be controlled by a staff member. It will depart Darmstadt carrying a Prisoner, and follow the convoy route through Jump Holes to Kyushu.
Farmer's Alliance and LWB will have mutual PvP bounties on each other.
Rule Changes:
Farmer's Alliance and LWB will have a 10 minute respawn timer in event systems so long as the transport is alive.
Possible Outcomes:
The LWB are breaking free of the Farmer's Alliance and will become an independent NPC faction.
Whether the convoy arrives at Kagoshima determines Schroder's fate.
Restarts:
Restarts will be enabled three hours before the event begins.
eventFAbmbStuttgart
eventFAbmbSigma13
eventFAvhfStuttgart
eventFAvhfSigma13
eventLWBvhfCologne
eventLWBvhfNewBerlin
eventLWBvhfSigma13
eventLWBbmbCologne
eventLWBbmbNewBerlin
eventLWBbmbSigma13
Rewards: Custom Title
Requires an INRP write-up about the event from the point of view of your character. Can be submitted as a report within a relevant faction channel, comm section or as part of a story thread.
Custom Roundel [Pending implementation] Requires an INRP write-up about the event from the point of view of your character. Can be submitted as a report within a relevant faction channel, comm section or as part of a story thread. Qualifying players will be eligible to claim a LWB Sichel or Sense sporting custom holo-roundels commemorating the LWB's independence.
Bug Levels Inverness PvE & Combat Event (Part 1) Crayter, LSF, Order vs Militants, Technocracy, Vagrants
DATE & TIME
Sep 24 - Sep 29
OVERVIEW
The Liberty Security Force have spent some months discreetly scouting Inverness with assistance from Crayter Republic pathfinders. They have grown increasingly certain that their concerns were well founded - a Nomad presence is indeed hidden somewhere within the system, likely within the East Avelmore Nebula. They are now mustering reinforcements for a reconnaissance in force, with the objective of locating and destroying the Nomad base, and capturing pilots for interrogation.
The Vagrants are aware of the predators stalking the clouds. They have not been idle, seeding the nebula with traps and enveloping the Hive in sensor-cloaking fields. These technologies are ravenous, and leeching power from the subspace grid indefinitely will likely draw the ire of the Nomad Mindshare. As a result, the Vagrants have pushed for a quick resolution by stirring up a hornet’s nest of proxies to wittingly or unwittingly do their bidding.
First, the forces of the Technocracy bristle at Liberty and Crayter’s intrusion, and the infringement of what they consider their inviolable territory. Technocrats initially responded by jamming or otherwise interfering with LSF operations, filling their sensors with ghosts and junk data. As the Liberty task force prepares for a significant military operation, the Technocracy’s Phalanx have steeled themselves for the need to respond directly with their own forces to ensure Valravn Citadel’s safety.
Indoctrinated thralls of the Vagrants have also exploited Technocrat expertise by leaking fabricated LSF data onto the local nets of Freeport 14 and Invergordon, setting out a Liberty plan for occupation that plays on the residents’ deep-seated fears and suspicions. Liberty’s refusal to comment on the Tuscaloosa’s classified operations in response has left a void for this misinformation to flourish, with the Zoners fearing the worst. The result has been predictable, with enraged combatants flocking to the banner of the Militants aboard the Carrier Praia.
The final complication is the presence of The Order. They have long had a cell in Coronado, cooperating with the Crayter Republic to study the moon Jericho. Crayter has covertly informed them of the LSF’s activities and concerns in Inverness, hoping The Order’s expertise will be able to tip the balance. The Order moved quickly to assemble a strike force, with the objective of sanitizing Inverness, so reinforcements can then deploy quickly towards Ontario to assist the Battleship Atum with cornering the illusive Wyoming. How the LSF will react to this "assistance" remains to be seen.
DETAILS
Incentives:
All event IDs will earn bounties and points for killing the other side's NPCs and players.
The purchase price of pilots and alien remains will be increased at nearby NPC bases owned by event IDs, with the Order and Vagrants having the largest bonus.
Config:
The PvE config will only be active during peak server hours (4pm-11:59pm UTC) during the week. However, it will run uninterrupted throughout the weekend.
Daily PvE score will affect the next day's PvP bonus by increasing it for the "losing" side.
Vagrants will have larger PvP and PvE bonuses than other IDs.
Rule Changes:
Carriers, Battleships, and Dreadnoughts will have their respawn timer increased to 2 hours for the duration of the event (in Inverness only).
Possible Outcomes:
All scoreboards will be used to determine the flavor of the ongoing storyline. However, they will not affect the outcome of the storyline.
Recorded INRP interactions and reports may be used to create news and rumors as part of future story beats.
Rewards: Custom Title
Requires an INRP write-up about the event from the point of view of your character. Can be submitted as a report within a relevant faction channel, or as part of a story thread.
Sci Data
Requires placement on a winning PvP or PvE leaderboard. This reward will be evenly split between ALL characters on the leaderboard, based on their individual contribution.
Alien Materials
Requires #1 placement on a PvP or PvE leaderboard, with the final score combined across all of your characters within that leaderboard. You must select one of the options from the list below.
Cogratulations to the defenders for securing the winning leaderboard! They will receive 400 sci data, split across all characters according to their contribution to the total score.
I have outlined the alien material winners below based on currently available information. Please list all characters you played under one leaderboard if you believe you exceeded these numbers. I will be updating this as time allows. (note that the final scores may be higher due to me working with an outdated score backup. Details here)
With tomorrow's restart, there will be a rather big overhaul of POB access management. Aim of those changes is to stop ooRP behavior of supplying bases with straight up hostile IFF'd ships, while leaving a way to allow such 'unorthodox' docking permission via POB Requests.
Whitelisting Hostile Ships
With this rework, making a ship dockable on a POB via adding to a whitelist will no longer be possible. If you're red to Outcasts on your Samura transport, adding your ship to the whitelist will still result in the base flashing red. Such behavior will still be possible, but only via 'SRP Whitelist', which will be governed by Admins via POB requests. Provide adequate roleplay, and there will be no issues
Defense Modes
There will now be three defense modes, down from five.
Command Syntax
All base access related functionalities will now be part of the /access command.
/access list <srp|whitelist|blacklist>
/access clear <srp|whitelist|blacklist>
/access add <name|tag|faction> <srp|whitelist|blacklist> <entry>
/access remove <name|tag|faction> <srp|whitelist|blacklist> <entry>
Yes, we will now allow Exact Shipnames to be added to POB config. No more do you need to worry about Jason.Bourne2 getting unauthorized access to your base!
A few examples:
/access remove faction blacklist fc_c_grp - remove corsairs from the blacklist
/access add name whitelist Steve - Adds Steve to the name whitelist. A ship named Steve2 would not be let in
/access add tag blacklist [XxX] - blocks access for ships with names starting with "[XxX]"
Another QOL improvement is that factions no longer are added/removed via numerical hash you had to generate, but now accept their nickname, such as br_m_grp for BMM. Those are easily findable using DarkStat or FLStat.
As mentioned previously, "/access add X srp" will only be available to Server Admins.
Limitations
Each of the whitelist and blacklist access lists will have a limit of 20 entries to avoid bloating the POB configs that means up to 20 whitelisted names, 20 whitelisted tags, 20 blacklisted names etc etc. Existing stations with more than 20 entries of a given kind will keep them, but you will be unable to add more until you go below the limit.
TL;DR: New command syntax, it will be no longer possible to enable docking for hostile/nodock rep ships without Admin Intervention. For example, no more Bowex ships docking on Molly bases, except for approved "SRP" docking requests.
During transition to the new system, bases with Defense Modes 2 and 4 will be moved to Defense Mode 1, those with Defense Modes 1 and 5 will move to Defense Mode 2, bases with Defense Mode 3 will remain as is.
EDIT: Almost forgot, dockable POBs will now always show as green, undockable POBs will show as white or red.