The Staff team has deliberated on the matter of a few POBs that have been set up in Omicron Iota over the last few months. Many of them have been low quality RP POBs set up specifically for use in the PVE zone set up there - but with little justification inRP to exist except to break immersion and cause deliberate annoyance to Nomad players. As such, POB deployment in the Nomad systems (Omicrons Iota, Psi, and Major) are not permitted short of an SRP, and any that still exist in those systems will be handled on a case-by-case basis by administration.
I'm going to make new friends this Christmas, but I love Discovery Drama!
I would like to apologize to the Admins / Staff that are nice guys / gals, some are not, and I'd like to Thank them for the effort they put into this mod and community but this decision is harsh and needs to be revised, based on the community you're dealing with and especially the faction.
This is not a rant about faction wide activity and maintaining it, this is about getting SERVER WIDE activity, reeling in New Players, which has diminished as the holidays are starting.
PVE areas are a great way for guys to chill, shoot stuff, get some credits and some new weapons. They generate faction and server wide activity. "Hey man, I got a space GTA, come join me! We'll shoot some stuff, get you a nice ship and pimp it with weapons!"
Let's Delve: Omicron Iota PoB Drama:
Reasons why players will deploy PoBs in Iota:
1. PVE area is in a Jump Drive Restricted System - you cannot jump in.
2. Iota is heavily defended by weapon platforms that hurt, especially capital ships.
3. PVE area drops 2 weapons: 1 BC Concussion Turret that shreds and 1C Defensive Mortar that hurts!
4. Need to repair / restock: unlike other encounter areas where you can repair and restock relatively quickly and safely, Iota PVE area is "who the hell placed it here" located. Closest restock for a non-Nomad player are Cairo or Capetown in Omicron Zeta (about some 100K+ away, passing through see point 1.) Especially for Caps. Snubs can do it while Docked on said Cap, except for ammo.
This would sum up the "Why".
WHAT HAPPENED:
- PoB was deployed
- Nomad faction sees people logging in Iota, starts searching for PoB.
- Finds PoB, Siege declared, destroyed
Rinse, Repeat, Rinse, Repeat.
- Rage on Discord, Contact and complain to Devs/Admins
- Not a single shred of maturity: We let you have 1 PoB there, but from time to time we will be fighting you guys. We do not siege that PoB, but you let us dock there with alts so we can use it to farm the encounter.
NOW:
- Who generates Server Wide activity?
- Who denies Server Wide activity by restricting access?
- What happened to Rule 1.?
This is the only faction that actively DEMANDS / COERCES a set of system restricted only for them and anyone entering that is not a nomad / wild is hunted down. This generates activity and interaction, but up to a point. Pas that point, its toxic. Faction Seek professional help
Suggestions:
- Move the encounter area
- Have a serious chat with 1IC of Nomad / Wilde Factions.
Server wide activity is for everyone. If any other faction would start locking down systems, the server would be in uproar.
This isn't space GTA. Violating the game lore and ID restrictions for the sake of "generating server activity" is a lazy excuse for what essentially is POB spamming.
As the original post says, it's out not outright banned though. If you want to put a POB there to farm PvE encounters, you are welcome to provide the appropriate amount of RP to justify that move in an SRP.
Hot take time. I have no stake in this but this is just my opinion as someone who has been heavily involved in the Edge Worlds in the past.
Don't like POB? Shoot POB. This seems lazy to me. How is this any different to POB constructions in places like Alaska, Tohoku, Thuringa etc. It's a slippery slope. People would complain even if these were SRP'd. I don't think a singular faction should get special treatment. This trend of Iota/Nomad systems being super speshul and therefore people shouldn't go there just makes me unironically think the system should just be deleted if the activity isn't supposed to occur there at all (same line of thought where the system just has anti-activity hazards). These things are just pixels at the end of the day. I think it's just a bit lazy how Nomad players flock to Staff to make changes rather than enforce their own role.
(12-23-2024, 12:48 PM)Seapanda Wrote: This isn't space GTA. Violating the game lore and ID restrictions for the sake of "generating server activity" is a lazy excuse for what essentially is POB spamming.
What lore or ID restrictions does it violate (unless there's ships farming that shouldn't, which in that case Admins should ruthlessly nuke those)? All the tools to resolve this or create activity for it pre-exist in the server environment already without the need for rules to make things messy.
(12-23-2024, 01:43 PM)LuckyOne Wrote: Agree with Lyth just let the players sort those out. Though one must notice the Holiday mode for POBs does not help that.
Well we could look at a solution halfway if it pleases people: something tells me the crew operating a POB in Omicron Iota wouldn't be getting time off....
Quote:This isn't space GTA. Violating the game lore and ID restrictions for the sake of "generating server activity" is a lazy excuse for what essentially is POB spamming.
1: I did not say anything about game lore or ID restrictions
2: The moment RP appears on the forums about a PoB in Iota, 5 minutes later you see 2 ships searching for it with a siege declared later > Read again carefully and think about WHAT HAPPENED.
3: How's the server population going with all the "lore" and "ID" Restrictions going? I see a decline in what used to be a uptick in the previous years.
The moment "lore" and "ID restrictions" get heavy regulated without any laxity - within moderate boundaries - is a nice pivotal moment which will see even more players flocking in to play! Cause everyone loves rules and restrictions! Obviously no.
![[Image: Lythrilux.gif]](https://sig.grumpybumpers.com/host/Lythrilux.gif)
