Event Policy - Revision history

Huhm: Event Policy WIP

2026-05-05T15:09:17Z

Event Policy WIP

← Older revision		Revision as of 15:09, 5 May 2026
Line 1:		Line 1:
			=== This document is a WORK IN PROGRESS ===

	====== The Purpose of Events ======		====== The Purpose of Events ======
	Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.		Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.
Line 6:		Line 8:
	=== Core Rules ===		=== Core Rules ===
	1. Do not directly interfere in another admin's event without explicit permission from that admin.		1. Do not directly interfere in another admin's event without explicit permission from that admin.

	2. Do not run events back to back with another event, especially Major events.		2. Do not run events back to back with another event, especially Major events.

Line 54:		Line 57:
	The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.		The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

	==== Faxes ====		===== Faxes =====
	These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.		These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

Line 66:		Line 69:
	* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.		* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

	==== Emergency Response Team (ERT) ====		===== Emergency Response Team (ERT) =====
	ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.		ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

Line 79:		Line 82:

	\|		\|
			\|}

			==== Admin Memes (Admemes) ====
			Admemes are small events that are usually low impact, spawn and forget occurrences. These typically require no oversight once set in motion. These should be logged if they affect the round in a larger capacity.

			Admins are expected to remain in round until the conclusion of admemes in the event that something does go wrong. If you cannot remain in round then you must log it in the event channel. Junior Admins and above can perform admemes according to their discretion. Junior admins must log all admemes.
			{\| class="mw-collapsible mw-collapsed"
			\| <strong></strong>
			\|-
			\|
	\|}		\|}

Huhm: Protected "Event Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2026-05-05T14:27:38Z

Protected "Event Policy" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 14:27, 5 May 2026
(No difference)

Huhm at 14:23, 5 May 2026

2026-05-05T14:23:47Z

← Older revision		Revision as of 14:23, 5 May 2026
Line 5:		Line 5:

	=== Core Rules ===		=== Core Rules ===
	~~{\| class="mw-collapsible mw-collapsed"~~		1. Do not directly interfere in another admin's event without explicit permission from that admin.
	~~\| <strong></strong>~~
	\|-
	\| 1. Do not directly interfere in another admin's event without explicit permission from that admin.
	2. Do not run events back to back with another event, especially Major events.		2. Do not run events back to back with another event, especially Major events.

Line 28:		Line 25:

	11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.		11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
	\|}
	----		----

	=== Event Types ===		=== Event Types ===
	All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.		All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

Huhm: Huhm moved page Event policy to Event Policy without leaving a redirect

2026-05-05T14:22:00Z

Huhm moved page Event policy to Event Policy without leaving a redirect

← Older revision	Revision as of 14:22, 5 May 2026
(No difference)

Huhm: Created Event Policy pt 1

2026-05-05T14:21:03Z

Created Event Policy pt 1

New page

====== The Purpose of Events ======
Events serve the purpose of increasing player engagement by providing fresh, interesting, and dynamic content. Events are never solely for admin enjoyment but that can be a side effect of events.

Events which intentionally exclude players, or encourage players to harass or antagonize others without any meaningful way to be handled in character should be avoided. Events are '''FOR THE PLAYERS.'''

=== Core Rules ===
{| class="mw-collapsible mw-collapsed"
| <strong></strong>
|-
| 1. Do not directly interfere in another admin's event without explicit permission from that admin.
2. Do not run events back to back with another event, especially Major events.

3. Events should never be purposefully exclusive to any member of crew, and should not encourage harassment or misconduct towards others

4. Events that leave crew with no resolution or means to combat the situation in a clear manner should be avoided.

5. There should always be player driven reason for an event to occur. Examples are a player prayer, game mode playtest, or player vote before the rounds. Major events can happen regardless with a 24 or more hour warning through the discord using Discord events.

6. Always log events. They are there to help you.

7. Never do events that are deathmatch. Examples are adding many antagonists or creating 'slop' rounds. Combat focused events are fine given that sufficient effort is given to ensure good roleplay.

8. In the case of events which are not meant to end the round, said events should always seek to minimize round removal.

9. Trial Admins should not run events of any scale without full admin oversight. Any events need to be logged for the sake of tracking and training purposes.

10. Junior Admins may only perform events that are administrative or 'Admemes'. Junior Admins may still develop and run major events as long as there are at least TWO full Admins to assist and approve.

11. Failure to log events when logging is required will lead to an admin review which may result in a strike. A repeated pattern of failing to log events will result in automatic assumption of wrongdoing and result in disciplinary action. Logging events is there to protect you.
|}
----
=== Event Types ===
All event types can be logged; however, it is only required in the specific instances outlined in this document. Failure to log an event when logging is required will lead to admin review. '''ALL''' events that involve an admin playing a character or entity that is not physically at Central Command must be logged. Players should be given the chance to play event characters, not admins.

==== Administrative ====
{| class="mw-collapsible mw-collapsed"
| <strong></strong>
|-
|Administrative events are normal and expected outcome of adminning. Reporting these is not required and should be done in cases where you expect there may be dissent with how something was done. Junior admins and above have full authority to conduct and approve administrative events according to their judgement.

# Answering Prayers
# Answering Faxes
# Sending ERT
# Enforcement of Non-Codified but publicly announced Admin Rulings
# Spawning a CC Intern to handle faxes. It is the admin's responsibility to ensure each intern does not cause issues.

===== Prayers =====
These are to ensure that players who interact with the prayer system have a consistent experience. Prayers are a roleplay mechanic and if you, as an admin, do not want to be bothered by prayers, do not answer them.

''When answering a Prayer with an Item or Smite:''

* Prayers should be answered literally. This can be either granting what the player intended, or by applying a literal interpretation in the form of a monkey's paw answer. '''Monkey's Paws are NEVER in direct contradiction''' with the literal wording of the prayer.
* If this answer of the prayer may have an effect on round flow, take into consideration on if granting it is reasonable.
* If you asked for an offering, grant the item when the offering is received with no strings attached. This is void if the offering WAS strings (IE, pledge yourself to my cause.)
* You may tell the player that their prayer has angered you. If the player continues to use prayers, further negative responses to them do not have to follow prayer guidelines.
* You may otherwise answer with subtle messages that make sense contextually with the prayer. If in round information is provided, it should be given in a riddle, puzzle, or some other cryptic format.
The god in charge of the altar where the player prays may be taken into account when decided how to answer the prayer, but the above guidelines should still be followed.

==== Faxes ====
These are to ensure that players who interact with the fax system have a consistent experience. Faxes are a roleplay mechanic and well-made responses to them can enhance their experience.

''When answering a Fax from a player:''

* Consider the amount of effort. If there are faxes with effort put in, these should be taken more seriously.
* Central Command should take complaints raised against Command Members or CCVIPs/Officials seriously.
* Central Command should avoid responding to faxes not sent by Command or CCVIPs/Officials unless it is a proper form or grounded complaint.
* Central Command should not answer faxes that have not been signed or stamped by any individual on the station.
* Central Command should only approve requests or reply in ways that are likely to enhance a player's experiences. Some situations you could send them a live pipe bomb which would improve their game experience by being funny. There is quite a bit of leeway.
* Central Command should usually only provide reasonable items via bluespace to assist the crew. What is reasonable is your discretion but it should not alter round flow in large ways.

==== Emergency Response Team (ERT) ====
ERT is a tool used for story telling. Admins have discretion to use this in situations where it could improve the situation and make it more fun for all parties involved. If you do not want to use it, there is no need to spawn them.

''When thinking on sending ERT:''

* You should consider the situation from an in-character perspective as an official in Central Command. Use information you have received via the Red Phone and the faxes as well as the credibility of the source.
* Take into context the effort of the form filled out and if it shows that an intervention of Central Command is needed.
* You should also consider the situation from an OOC admin perspective. Would ERT improve the round for everyone or would it just cause stall? Would ERT significantly turn the tides on an antagonist who deserves to win? If in doubt, ask the antagonists if they would like the challenge.
* If OOC rules were broken by the antagonists, the leeway for sending ERT in response even if the antagonist deserves to win, is a lot higher. Do what feels right for the players as a whole.

In general, send a force that matches the situation. If ERT is being used for non-combat purposes, consider giving them tools to fit the situation instead of more weapons.

|
|}