Staffing Guidelines - Revision history

Toastewoofs: /* H1.2 Moderation Team */

2026-05-27T19:46:28Z

H1.2 Moderation Team

← Older revision		Revision as of 19:46, 27 May 2026
Line 461:		Line 461:
	* '''Trial Game Moderators:'''		* '''Trial Game Moderators:'''
	** All duties of Game Moderators (above), excluding age verifications;		** All duties of Game Moderators (above), excluding age verifications;
	** ~~Sricter~~ adherence to SPLURT staffing guidelines is expected for the duration of their trial period.		** Stricter adherence to SPLURT staffing guidelines is expected for the duration of their trial period.

	===== H1.3 Event Team =====		===== H1.3 Event Team =====

Toastewoofs: /* (H) Staff Hierarchy */

2026-05-19T20:37:58Z

(H) Staff Hierarchy

← Older revision		Revision as of 20:37, 19 May 2026
Line 196:		Line 196:
	Application of this page and the rules therein are to the spirit of the guidelines/rules, and not necessarily the semantic or written expression. Contact Toaste (@toastey on discord) for queries or concerns.		Application of this page and the rules therein are to the spirit of the guidelines/rules, and not necessarily the semantic or written expression. Contact Toaste (@toastey on discord) for queries or concerns.

	== (E) Event Team Standards ==		= (E) Event Team Standards =
	Members of the event team (trial eventmins, eventmins, and head eventmins) are event-only members of staff intermingled with other staff, responsible solely for running events on the SPLURT game server. The following guidelines '''only apply to members of the event team''', and should not be referred to by members of the moderation team. '''Event team members are still beholden to the core staff rules'''.		Members of the event team (trial eventmins, eventmins, and head eventmins) are event-only members of staff intermingled with other staff, responsible solely for running events on the SPLURT game server. The following guidelines '''only apply to members of the event team''', and should not be referred to by members of the moderation team. '''Event team members are still beholden to the core staff rules'''.

Line 279:		Line 279:
	** This does not apply to major events.		** This does not apply to major events.

	== (M) Maintainer Team & Code Standards ==		= (M) Maintainer Team & Code Standards =
	These standards apply to maintainers in full. PR standards apply to all contributors.		These standards apply to maintainers in full. PR standards apply to all contributors.

Toastewoofs: /* M3. Balance */

2026-05-19T20:25:44Z

M3. Balance

← Older revision		Revision as of 20:25, 19 May 2026
Line 378:		Line 378:

	==== '''M3. Balance''' ====		==== '''M3. Balance''' ====
	When all is said and done, maintainers and head maintainers are '''above''' every member of the event and moderation team ~~(including~~ Head Administrators) when it comes to balance~~. While a Head Administrator can injunct a balance decision, they may not make their own balance decisions separate from members of the maintainer team~~.		When all is said and done, maintainers and head maintainers are '''above''' every member of the event and moderation team excluding Administrators and Head Administrators when it comes to balance.

	===== M3.1 Power Balance =====		===== M3.1 Power Balance =====

Toastewoofs: /* M3. Balance */

2026-05-19T20:23:51Z

M3. Balance

Toastewoofs: /* M2.4 Feature Additions */

2026-05-16T18:45:06Z

M2.4 Feature Additions

← Older revision		Revision as of 18:45, 16 May 2026
Line 279:		Line 279:
	** This does not apply to major events.		** This does not apply to major events.

	== (M) Maintainer Team Standards ==		== (M) Maintainer Team & Code Standards ==
	These standards apply to maintainers in full. PR standards apply to all contributors.		These standards apply to maintainers in full. PR standards apply to all contributors.

Toastewoofs: /* M3.2 Injunctions */

2026-05-16T18:36:54Z

M3.2 Injunctions

← Older revision		Revision as of 18:36, 16 May 2026
Line 389:		Line 389:

	* Head Admins may injunct balance actions during discussion, or prior to merging or test-merging. Merged balance actions cannot be injunctioned.		* Head Admins may injunct balance actions during discussion, or prior to merging or test-merging. Merged balance actions cannot be injunctioned.
	* An injunction means that the balance decision in question is '''not''' to be implemented until both Head Admins, and every member of the maintainer team has reviewed the decision.		* An injunction means that the balance decision in question is '''not''' to be implemented (merged, test-merged; and must be un-test-merged if applicable) until both Head Admins, Mosley, and every member of the maintainer team has reviewed the decision.
	** If both Head Admins agree that the injunction is necessary, they invoke an administrative override of the decision, and the injuncted action is not to be acted out.		** If both Head Admins agree that the injunction is necessary, they invoke an administrative override of the decision, and the injuncted action is not to be acted out.
			*** Mosley reserves the right to override any and all decisions made on SPLURT.
	** If only one Head Admin agrees that the injunction is necessary, the maintainer team may override this Head Admin if they are able to reach a consensus via poll that the decision should go ahead.		** If only one Head Admin agrees that the injunction is necessary, the maintainer team may override this Head Admin if they are able to reach a consensus via poll that the decision should go ahead.
	** Both Head Admins and the maintainer team have the right to request Mosley as an arbitrator in the case of an injunction.		** Both Head Admins and the maintainer team have the right to request Mosley as an arbitrator in the case of an injunction.

Toastewoofs: /* M2.4 Feature Additions */

2026-05-16T18:32:12Z

M2.4 Feature Additions

Toastewoofs: /* C8. Player Governance */

2026-05-16T18:29:49Z

C8. Player Governance

Toastewoofs: /* H1.2 Moderation Team */

2026-05-16T18:26:21Z

H1.2 Moderation Team

← Older revision		Revision as of 18:26, 16 May 2026
Line 435:		Line 435:
	** Creating staff discussions, providing input on staff discussions, and deciding on staff discussions (where appropriate);		** Creating staff discussions, providing input on staff discussions, and deciding on staff discussions (where appropriate);
	** Participation in the Administrator Forum;		** Participation in the Administrator Forum;
	** Handling tickets that have been escalated from moderators either as part of an appeal or contest (~~see 3~~, ~~4 of the "Staff Complaints & Appealing" section~~);		** Handling tickets that have been escalated from moderators either as part of an appeal or contest (S3, S4);
	** Screening, discussing, and overseeing balance changes with or without the Head Maintainer, involving Head Administrators where necessary;		** Screening, discussing, and overseeing balance changes with or without the Head Maintainer, involving Head Administrators where necessary;
	** Corroborating with other Administrators to ensure all rules, regulations, and guidelines are clear, concise, and able to be understood by both players and staff, including making amendments where rules are unclear, unwritten, or poorly written in some way;		** Corroborating with other Administrators to ensure all rules, regulations, and guidelines are clear, concise, and able to be understood by both players and staff, including making amendments where rules are unclear, unwritten, or poorly written in some way;
	** General game server moderation, including handling tickets regarding rule-breaks, player complaints, and other miscellaneous tickets;		** General game server moderation, including handling tickets regarding rule-breaks, player complaints, and other miscellaneous tickets;
	** Ensuring that the rules are enforced by other members of staff;		** Ensuring that the rules are enforced by other members of staff;
	** Handling staff complaints against Game Moderators or Trial Game Moderators (see 1, ~~2 of the "Staff Complaints & Appealing" section~~);		** Handling staff complaints against Game Moderators or Trial Game Moderators (see S1, S2);
	** Ensuring server safety, community safety, and community engagement (ensuring players want to play);		** Ensuring server safety, community safety, and community engagement (ensuring players want to play);
	** Representing the player base on balance, rules, policies, or changes thereof, and acting as a voice for the player base and their opinions thereof;		** Representing the player base on balance, rules, policies, or changes thereof, and acting as a voice for the player base and their opinions thereof;

Toastewoofs: /* M2.4 Feature Additions */

2026-05-16T18:24:17Z

M2.4 Feature Additions

@@ Line 33: / Line 33: @@
 * How to conduct themselves on the discord, through following the discord rules and maintaining positive relationships with staff and community members.
 * It is also expected that Head Eventmin provide information regarding hierarchy, staff punishment, appeal times, ban types, holistic punishment, etc.
@@ Line 59: / Line 61: @@
 * You must ensure that you handle sensitive situations with care, and avoid causing unnecessary stress or harm to both staff and players
 * You must ensure that sensitive and private information remains confidential; this includes all staff conversations, and all messages or media posted in staff channels.
 ==== '''C2. Respect''' ====
@@ Line 273: / Line 284: @@
 ===== M0.1 Core Staff Rules =====
-* The following Core Staff Rules apply to members of the maintainer team: 1.1, 1.2, 2.1, 3.1, 4.2, 5.1. No other core staff rules apply to maintainer team members.
+* The following core staff rules apply to members of the maintainer team: C1.1, C1.2, C1.3, C2.1, C3.1, C4.2, C5.1. No other core staff rules apply to maintainer team members.
 * Maintainers who hold a different rank in a different team, such as "Game Moderator", are liable to lose maintainership as a result of infringements committed on behalf of their conduct as their alternate rank.
 ** At the discretion of Mosley with input from Head Admins
@@ Line 289: / Line 300: @@
 *Members of the maintainer team are subject to immediate demotion following any pull requests that provide a direct in-game benefit to any one specific person (or group of persons) not designed to be an overarching non-targeted buff.
 **This means that self-serving pull requests for oneself or one's friends are summarily disallowed under every circumstance.
 ==== '''M1. Merging and Test-merging''' ====
@@ Line 348: / Line 363: @@
 ===== M2.5 Feature Removals =====
 ==== '''M3. Balance''' ====
 = (H) Staff Hierarchy =

← Older revision		Revision as of 20:23, 19 May 2026
Line 359:		Line 359:
	* When discussing whether to add a new gameplay feature, such as a new antagonist, members of the event and moderation team must be involved.		* When discussing whether to add a new gameplay feature, such as a new antagonist, members of the event and moderation team must be involved.
	** This does not extend to balance discussions of the proposed addition.		** This does not extend to balance discussions of the proposed addition.
	* Where a feature addition can be considered major (a new antagonist, new job, new department, new map, or new weapons) ~~Mosley~~ (typically after counsel with other members of staff) must provide approval of the addition.		* Where a feature addition can be considered major (a new antagonist, new job, new department, new map, or new weapons) a Head Admin+ (typically after counsel with other members of staff) must provide approval of the addition.
	** Head Admins may also issue injunctions (see M3.1, M3.2) at their discretion, if necessary.		** Head Admins may also issue injunctions (see M3.1, M3.2) at their discretion, if necessary.
	* Where a feature addition can be considered minor (new items, new chemicals, updates to existing maps), a Maintainer+ must provide approval of the addition.		* Where a feature addition can be considered minor (new items, new chemicals, updates to existing maps), a Maintainer+ must provide approval of the addition.
Line 384:		Line 384:
	* Trial Game Moderators, Game Moderators, Trial Eventmins, Eventmins, Head Eventmins, and Server Spriters are all considered below maintainers on the topic of balance.		* Trial Game Moderators, Game Moderators, Trial Eventmins, Eventmins, Head Eventmins, and Server Spriters are all considered below maintainers on the topic of balance.
	* Administrators and Head Admins are the primary staff members who should provide advice or feedback on balance decisions.		* Administrators and Head Admins are the primary staff members who should provide advice or feedback on balance decisions.
	** ~~With the exception of injunctions, members of the maintainer team~~ are ~~not required~~ to ~~listen~~ to ~~the words of Administrators~~ and Head ~~Admins, but~~ are ~~advised to integrate earnest feedback~~.		** Administrators are considered equal in rank to maintainers when it comes to balance, and Head Administrators are considered above maintainers.

	===== M3.2 Injunctions =====		===== M3.2 Injunctions =====
Line 392:		Line 392:
	** If both Head Admins agree that the injunction is necessary, they invoke an administrative override of the decision, and the injuncted action is not to be acted out.		** If both Head Admins agree that the injunction is necessary, they invoke an administrative override of the decision, and the injuncted action is not to be acted out.
	*** Mosley reserves the right to override any and all decisions made on SPLURT.		*** Mosley reserves the right to override any and all decisions made on SPLURT.
	** If only one Head Admin agrees that the injunction is necessary, the maintainer team may override this Head Admin if they are able to reach a consensus via poll that the decision should go ahead.		** If only one Head Admin agrees that the injunction is necessary, the maintainer team may override this Head Admin if they are able to reach a consensus via poll that the decision should go ahead, as long as Mosley is aware of this.
	** Both Head Admins and the maintainer team have the right to request Mosley as an arbitrator in the case of an injunction.		** Both Head Admins and the maintainer team have the right to request Mosley as an arbitrator in the case of an injunction.
	* Injunctions should not be performed lightly, and should be considered a last resort to reassert control over server direction.		* Injunctions should not be performed lightly, and should be considered a last resort to reassert control over server direction.

← Older revision		Revision as of 18:32, 16 May 2026
Line 358:		Line 358:

	* When discussing whether to add a new gameplay feature, such as a new antagonist, members of the event and moderation team must be involved.		* When discussing whether to add a new gameplay feature, such as a new antagonist, members of the event and moderation team must be involved.
	** This does not ~~extent~~ to balance discussions of the proposed addition.		** This does not extend to balance discussions of the proposed addition.
	* Where a feature addition can be considered major (a new antagonist, new job, new department, new map, or new weapons) ~~a Head Admin~~ must provide approval of the addition.		* Where a feature addition can be considered major (a new antagonist, new job, new department, new map, or new weapons) Mosley (typically after counsel with other members of staff) must provide approval of the addition.
			** Head Admins may also issue injunctions (see M3.1, M3.2) at their discretion, if necessary.
	* Where a feature addition can be considered minor (new items, new chemicals, updates to existing maps), a Maintainer+ must provide approval of the addition.		* Where a feature addition can be considered minor (new items, new chemicals, updates to existing maps), a Maintainer+ must provide approval of the addition.
	* Where a feature is being added that necessitates balance of any kind, the individual making the addition is wholly responsible for ensuring that said addition is balanced for the SPLURT community.		* Where a feature is being added that necessitates balance of any kind, the individual making the addition is wholly responsible for ensuring that said addition is balanced for the SPLURT community.
Line 369:		Line 370:
	*When discussing whether to remove a gameplay feature, such as a new antagonist, members of the staff team should be informed, but need not necessarily be involved.		*When discussing whether to remove a gameplay feature, such as a new antagonist, members of the staff team should be informed, but need not necessarily be involved.
	**This does not extent to balance discussions of the proposed addition.		**This does not extent to balance discussions of the proposed addition.
	*Where a feature removal can be considered major (antagonist removal, job removal, department removal, map removal, or removal of weapons) a Head Admin must provide approval of the removal.		*Where a feature removal can be considered major (antagonist removal, job removal, department removal, map removal, or removal of weapons) a Head Admin+ must provide approval of the removal.
			**Head Admins may also issue injunctions (see M3.1, M3.2) at their discretion, if necessary.
	* Where a feature removal can be considered minor (items, chemicals), a Maintainer+ must provide approval of the removal.		* Where a feature removal can be considered minor (items, chemicals), a Maintainer+ must provide approval of the removal.
	* Where a feature is being removed that necessitates rebalance of any kind, the individual making the addition is wholly responsible for ensuring that said removal is balanced for the SPLURT community.		* Where a feature is being removed that necessitates rebalance of any kind, the individual making the addition is wholly responsible for ensuring that said removal is balanced for the SPLURT community.

← Older revision		Revision as of 18:29, 16 May 2026
Line 192:		Line 192:
	* Staff have discretion, despite this guideline, to ticket players who have not been complained about, but staff doing so '''accept all responsibility''' and '''understand that players have a strong basis of appeal''' through the grounds of this guideline.		* Staff have discretion, despite this guideline, to ticket players who have not been complained about, but staff doing so '''accept all responsibility''' and '''understand that players have a strong basis of appeal''' through the grounds of this guideline.
	* Server-safety rule violations are exempted from this rule, and should be actioned regardless of circumstances.		* Server-safety rule violations are exempted from this rule, and should be actioned regardless of circumstances.

			==== '''C9. Application''' ====
			Application of this page and the rules therein are to the spirit of the guidelines/rules, and not necessarily the semantic or written expression. Contact Toaste (@toastey on discord) for queries or concerns.

	== (E) Event Team Standards ==		== (E) Event Team Standards ==
Line 218:		Line 221:
	There are three types of events that members of the event team are expected to run: Major Events, Faction Events, In-round Events (also known as "buttonpushing").		There are three types of events that members of the event team are expected to run: Major Events, Faction Events, In-round Events (also known as "buttonpushing").

	====== E2.1 Major Events: ======		===== E2.1 Major Events: =====
	A major event is any event that is expected to satisfy any two of the following four criteria:		A major event is any event that is expected to satisfy any two of the following four criteria:

Line 234:		Line 237:
	Members of the event team are permitted to disrupt any round that would delay a major event by more than 30 minutes through calling the shuttle early, or if voted for by players, more "fun" means.		Members of the event team are permitted to disrupt any round that would delay a major event by more than 30 minutes through calling the shuttle early, or if voted for by players, more "fun" means.

	====== E2.2 Faction Events: ======		===== E2.2 Faction Events: =====
	A faction event is any event that does not satisfy the criteria for a major event, but is still likely to involve the general station, or is restricted to a specific ghost role or group of ghost roles. For example, spawning in a custom .dmi meteor outside the Persistence, or in Ordnance, that they (the persistence) or crewmembers will interact with.		A faction event is any event that does not satisfy the criteria for a major event, but is still likely to involve the general station, or is restricted to a specific ghost role or group of ghost roles. For example, spawning in a custom .dmi meteor outside the Persistence, or in Ordnance, that they (the persistence) or crewmembers will interact with.

Line 243:		Line 246:
	* Members of the event team hosting a faction event must credit any co-hosting volunteers or staff, and any volunteers.		* Members of the event team hosting a faction event must credit any co-hosting volunteers or staff, and any volunteers.

	====== E2.3 In-Round Events: ======		===== E2.3 In-Round Events: =====
	A station event is any event that does not satisfy the criteria for a major event, but is likely to impact (and is restricted to) the general station. For example, spawning in a custom .dmi meteor in ordnance that crewmembers will interact with.		A station event is any event that does not satisfy the criteria for a major event, but is likely to impact (and is restricted to) the general station. For example, spawning in a custom .dmi meteor in ordnance that crewmembers will interact with.