Heya!
So I think this might be just a slight lack of knowledge of how our event system works or a misunderstanding of it. And that seems to be a decently pervasive thing in our community.
There is a publicly accessible event guidelines file but I’ll explain it anyways. (The event guidelines on the forums are also kind of outdated and bad, its on the list of things that I want to do this year I promise)
I’m just gonna explain how it works without getting into anything else so if anyone is looking for drama/dramabaiting or anything like that look elsewhere.
I’m also trying to be as transparent about it as possible but if anyone is gonna try and take this good gesture in bad faith and are gonna try to run with it my wrath will be swift and merciless.
Broadly speaking we have 3 types of events. Cosmetic events, Minor events and major events.
Types of events
Cosmetic events
Cosmetic events are events like changing the colour of a xeno, giving the captain a funny hat or giving the CL a big gold bar to bribe the CO with.
While technically a different kind of event I also lump Objective events in here. They are events like giving the CL an objective or breaking something on the ship and telling MTs to go fix it.
Fax response events I also lump into this category. Fax events are just responses to faxes ingame like sending a bodyguard to the CL who got their assault case dismissed by MPs or sending in a provost inspection team after getting a fax about something on the Almayer that needs their attention.
The goal of all of these types of event is that they are supposed to add RP or flavour into a round. But they are also supposed to have little to no impact on the round itself.
These events shouldn’t include stuff like making a really big shotgun that does double damage or sending in a WY squad to capture the queen because the CL sent such nice faxes.
All of these events can be run by any staff member who is not a trial-moderator at any time and they dont need authorization. ERTs might need authorization though if they aren’t purely reactionary, IE you want to send 3 pizza delivery persons to surprise the marines at briefing.
You also dont need to log most cosmetic events, although if you give any objectives or send any ERTs you should be logging it.
Minor events
Minor events are allowed a bit more impact on the round and can start to include stuff like event characters, spawned in items that people dont usually have access to or a small extra part of the map that gets spawned in.
The goal of these types of events is to create fun and RP opportunities for players while having only a slight impact on round balance and flow. Its fine if these events give minor boons to one of the sides but they shouldn’t be big gamechangers.
These events need to get logged right before, during or after the event was run (we really dont care when as long as its not a week after the fact or something like that)
They can also require authorization. Admins and above are free to run these events whenever they like without asking for authorization. Moderators and Smods should be asking for Authorization first.
Major events
Major events are events that have a major alteration to roundflow and affect a lot of players. They are events like Spawning in two tanks and giving xenos multiple special xenos to have some sort of epic battle, swapping out a faction with another one like having the Almayer manned by the UPP instead of the USCM or a greenshift where marines land on a planet without any xenos to fight.
The goal of these events is basically always to just create a big fun scenario for the players of the server.
The events are allowed to give clear advantages or disadvantages to one side (Although keeping things fair is most fun for everyone and encouraged) and affect basically all players on the server.
These major events always require logging.
They also also require authorization for anyone who isnt a part of management.
Something to note also, that kind of goes for all events but especially for major ones, if there is a large departure from the lore/setting that should also be included in the authorization request.
Now those are decent summaries of the types of events, there are some if’s but’s and when’s but this broadly covers it all.
I mentioned logging and authorization a couple of times and I dont think there is any harm in describing how that works.
Logging:
By logging we mean documenting the fact that an event happened around X time. We have a specific channel for this and whenever someone runs an event that requires logging they should log it either just as they are about to run it, during the event when they have some spare time or after they completed the event.
Logging it isnt complicated and it’s just a short message saying something like “Spawned in a UPP Ambassador to RP with the CO” or “Ran [Link to the authorization request]”
Sometimes if an event grows out of scope you’ll want to log any extra stuff that you did like “Sent in a UPP extraction team after the Ambassador got arrested”
That stuff is just to clarify what you did basically. Thats the entire purpose behind logging.
Authorization:
A couple of event types require authorization and we have a discord forum thingie for that.
In there we ask for staff members to give the general idea of their event and to ask for authorization for it. If its really silly or a really large departure from the lore/setting they should also include that.
When it comes to how much we want people to sketch out it really isnt that much. Basically just a really short description of what they’re planning to do. The average length of a request is around 4-5 sentences.
Now for the actual authorization usually its just “Authed, go for it” but sometimes there will be questions or caveats. Something like “Dont run this on highpop”, “How are you planning to deal with marines shooting the ambassador that you are sending to the Almayer?” or “Can you do this another way like doing X instead of X?”
While I dont have any cold, hard, data the approval rate for events is very high. I’d estimate about 75-90%.
We also try to be decently accommodating as management by getting to the event auths quickly, and I always tell people that if they need an event authed right there and then to hammer home that its for the current round (by putting it in the title or something) and we’ll try to be extra fast in getting to it.
There is also some other stuff that can be done to help out like giving someone rolling auth (to run an event multiple times) and relaxing event standards at times like christmas, april fools, etc.
ANYWAYS this is all kinda just a ploy to give my, biased, opinion. I think that while there are some slight rough edges the event system as it stands works really well and would not need any adjustment to try and make it more accommodating since those would probably cause more issues than they would resolve.
I dont think I missed anything in how I described the event system. But its also kinda late as of writing this so I might have been sloppy on something really minor idk.