Administrators should not be allowed to set the map to Sokoban and just then log off and leave it unattended.

[carlarc]

Recently, on Manuel, someone set the map to Sokoban. I don't know who, it likely doesn't matter. Apparently Xzero was on during the round and in the pregame lobby. The round ID is 240464.

The round quickly spun into chaos. A changeling was murderboning people in 'maintenance', someone plasmaflooded, the SM exploded. These are pretty egregious things to happen in MRP, and there was no admin on.

I strenously object to the notion of setting the map to an event station, especially the most chaotic one available, one which is entirely a shitpost, and then just leaving the shift unadministrated. I don't think this should be allowed in administrative policy.

There is nothing wrong with a Sokoban shift. The map may even have been voted for, though I don't know that. But this is creating an extremely impactful event and then just leaving it to be unadministrated, which isn't right. Various alarm-worthy events happened that would have seriously benefitted from an admin taking a peek to see what's up, but this didn't happen.

If you make an event but then Real Life and you have to leave, that's okay, but I think you should have to make this clear in whatever administrative channels there are, and request someone come online to oversee the round in your stead. (Unless your fucking dad is dying or something)

[carlarc]

To clarify, the policy I want here is just:

Administrators cannot create a major event and then leave it unattended.
Changing the map to an unsupported Map Depot station counts as a major event.

[carlarc]

This is the map for those that are unaware (headmin didnt know, unforgivable) (the server had ~40 pop)

[MooCow12]

A map like that probably would lead to a need of administrative oversight / moderation ya lol.

An admin pulling a funny lever and then leaving the others to have to compensate is kind of hilarious though.

[DrAmazing343]

We are currently looking into the matter, but this is already covered by our admin conduct policy. I apologize for the poor experience— we will speak to those involved.

[Justice12354]

Major event is not defined here. Is spawning in a giant blue carp with the objective to lay some fat rhymes on the Cap in the middle of the bar a major event? Because, if so, I don't think administrative supervision is required for this event in specific (I can probably come up with a better example where there's no need for an online admin and it affects a good chunk of the station). While I agree that for "high pop in small map" events admin activity is crucial, making this a policy is meh since this is already a valid complaint based on our (flimsy) event conduct imo.

[TheLoLSwat]

this should be moved to complaints

[Vekter]

This is pretty solidly just a complaint policy thread, given that you also have an admin complaint open for the same thing.

I'm going to dispense with whether or not you're being even remotely reasonable given this specific situation (you're not) and just address the broader policy concept here - Absolutely fucking not. Event stuff is already generally handled in admin conduct and we typically handle issues with admins doing bad events either through complaints or feedback. I don't appreciate the idea that I can get sniped by headmins for having to take a shit in the middle of an event.

If this ends up being policy and I have to be glued to my PC every waking second of running an event, I'm either quitting or never running an event again.

[NecromancerAnne]

I mean, sometimes you could have an event going and real life gets in the way to force you to stop, it's happened to me at least twice.

Maps aren't events though. They're just a map. It isn't persistence station which needs an admin to shut it down at the end, after all. I don't think you can be held accountable for setting a round to a map, and sokoban is a totally functional (if extremely squat) map. It's not like they plopped you into an empty open field and then told you to get fucked.

[TheFinalPotato]

All constricting events in this way will do is remove them from the community. None of the things you list are counter to roleplay, using a plasmaflood as an example of a rulebreak or issue is insane.
Rounds are allowed to be stupid and chaotic, admins should be given the same privilege.
I don't know how recent recently is but I think you would be better served venting your frustrations by like baking or something rather then trying to make One Particular Thing against policy.

[NamelessFairy]

One which is entirely a shitpost

Just for clarity purposes this is false. The map was initially created as a sort of response to other compact stations which usually take shortcuts such as stacking machines ontop of eachother or other non-player attainable map components. Its namesake is because this developed into a moving block puzzle especially in engineering and atmospherics, particularly on medium to higher pop levels where you need to communicate to move crates/canisters/emitters around without disrupting eachother. I would consider it more of a challenge map when played at higher pops similar to other teamwork focused maps like shipstation, this isn't to say if it requires supervision or not and I have always supervised it when I was running it but just for clarity purposes.

[DrAmazing343]

No policy change is needed here. I would advise any other folks who have issues with this to admin complaint as necessary, and we will handle things there.

Burger +1
Timber +1