Staffing Guidelines - Revision history

Toastewoofs: /* Staff Hierarchy */

2026-05-09T13:09:39Z

Staff Hierarchy

← Older revision		Revision as of 13:09, 9 May 2026
Line 207:		Line 207:
	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").

	====== 2.1.1 Major Events: ======		====== 2.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 223:		Line 223:
	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.

	====== 2.1.2 Faction Events: ======		====== 2.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 232:		Line 232:
	* 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.

	====== 2.1.3 In-Round Events: ======		====== 2.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.

Line 264:		Line 264:
	** Foreseeability applies.		** Foreseeability applies.
	** This does not apply to major events.		** This does not apply to major events.

			== Maintainer Team Standards ==
			TBD

			==== '''0. TBD''' ====

			===== 0.1 TBD =====

			==== '''1. TBD''' ====

			===== 1.1 TBD =====

			==== '''2. TBD''' ====

			===== 2.1 TBD =====

	= Staff Hierarchy =		= Staff Hierarchy =

Toastewoofs: /* 3.1 Self and Community Service */

2026-05-04T18:59:40Z

3.1 Self and Community Service

← Older revision		Revision as of 18:59, 4 May 2026
Line 200:		Line 200:
	===== 1.2 Participation in Policy Discussions =====		===== 1.2 Participation in Policy Discussions =====

	* Members of the event team are permitted to partake in policy discussions ~~that are relevant to their work~~, such as amendments to the core or event team staff standards, event guidelines, or in-game policy ~~likely to affect their work (excluding their personal affairs~~ in~~-game, such as~~ policy ~~that may disrupt their security playstyle)~~.		* Members of the event team are permitted to partake in all policy discussions, such as amendments to the core or event team staff standards, event guidelines, moderation policy, or in-game policy, but members of the moderation team take priority in policy discussions.
	** Members of the event team may make votes, vote on, and propose ~~these~~ matters of their own accord.		** Members of the event team may make votes, vote on, and propose matters of their own accord.
	* ~~Members~~ of the event team ~~are permitted to partake in policy discussions otherwise irrelevant to their work~~, ~~such~~ as policy ~~on silicon (AI, cyborg) validhunting, but may not make votes~~, ~~vote on~~, or ~~propose these matters in any capacity~~.		** If an administrator+ requests that a member of the event team, or the event team as a whole to withhold from a policy discussion, then said member, or the team as a whole are obliged to do so.

	==== '''2. Event Classifications & Guidelines''' ====		==== '''2. Event Classifications & Guidelines''' ====

Toastewoofs: /* 1.2 Participation in Policy Discussions */

2026-04-29T21:04:35Z

1.2 Participation in Policy Discussions

← Older revision		Revision as of 21:04, 29 April 2026
Line 202:		Line 202:
	* Members of the event team are permitted to partake in policy discussions that are relevant to their work, such as amendments to the core or event team staff standards, event guidelines, or in-game policy likely to affect their work (excluding their personal affairs in-game, such as policy that may disrupt their security playstyle).		* Members of the event team are permitted to partake in policy discussions that are relevant to their work, such as amendments to the core or event team staff standards, event guidelines, or in-game policy likely to affect their work (excluding their personal affairs in-game, such as policy that may disrupt their security playstyle).
	** Members of the event team may make votes, vote on, and propose these matters of their own accord.		** Members of the event team may make votes, vote on, and propose these matters of their own accord.
	* Members of the event team are ~~prohibited from partaking~~ in policy discussions otherwise irrelevant to their work, such as policy on silicon (AI, cyborg) validhunting.		* Members of the event team are permitted to partake in policy discussions otherwise irrelevant to their work, such as policy on silicon (AI, cyborg) validhunting, but may not make votes, vote on, or propose these matters in any capacity.
	** Members of the event team may not make votes, vote on, or propose these matters in any capacity.

	==== '''2. Event Classifications & Guidelines''' ====		==== '''2. Event Classifications & Guidelines''' ====

Toastewoofs: /* 1.2 Participation in Policy Discussions */

2026-04-29T21:03:14Z

1.2 Participation in Policy Discussions

← Older revision		Revision as of 21:03, 29 April 2026
Line 200:		Line 200:
	===== 1.2 Participation in Policy Discussions =====		===== 1.2 Participation in Policy Discussions =====

	* Members of the event team are permitted to partake in policy discussions that are relevant to their work, such as amendments to the core or event team staff standards, event guidelines, or in-game policy likely to affect their work (excluding their personal affairs in-game).		* Members of the event team are permitted to partake in policy discussions that are relevant to their work, such as amendments to the core or event team staff standards, event guidelines, or in-game policy likely to affect their work (excluding their personal affairs in-game, such as policy that may disrupt their security playstyle).
	** Members of the event team may make votes, vote on, and propose these matters of their own accord.		** Members of the event team may make votes, vote on, and propose these matters of their own accord.
	* Members of the event team are prohibited from partaking in policy discussions otherwise irrelevant to their work, such as policy on silicon (AI, cyborg) validhunting.		* Members of the event team are prohibited from partaking in policy discussions otherwise irrelevant to their work, such as policy on silicon (AI, cyborg) validhunting.

Toastewoofs: /* 1.4 Maintainer Team */

2026-04-29T20:58:39Z

1.4 Maintainer Team

← Older revision		Revision as of 20:58, 29 April 2026
Line 326:		Line 326:

	===== 1.3 Event Team =====		===== 1.3 Event Team =====
			These roles are responsible for hosting events on the SPLURT game server.
	* '''Head Eventmin:''' There is one Head Eventmin slot on SPLURT, but an administrator may take the role of Interim Head Eventmin in the absence of one. Their duties include:		* '''Head Eventmin:''' There is one Head Eventmin slot on SPLURT, but an administrator may take the role of Interim Head Eventmin in the absence of one. Their duties include:
	** The opening, screening, shortlisting, selecting, and closing of '''event''' staff applicants & applications;		** The opening, screening, shortlisting, selecting, and closing of '''event''' staff applicants & applications;
Line 348:		Line 348:

	===== 1.4 Maintainer Team =====		===== 1.4 Maintainer Team =====
			The maintainer team, and its members, is the only team not forming part of the SPLURT staff team. As such, they are only beholden to the maintainer guidelines.
	* '''Head Maintainer:''' There is one Head Maintainer slot on SPLURT. Their duties include:		* '''Head Maintainer:''' There is one Head Maintainer slot on SPLURT. Their duties include:
	** Fixing issues posted on the GitHub;		** Fixing issues posted on the GitHub;

Toastewoofs: /* 1.3 Event Roles */

2026-04-29T20:57:19Z

1.3 Event Roles

← Older revision		Revision as of 20:57, 29 April 2026
Line 276:		Line 276:
	The SPLURT staff team is not tall in nature, and instead relies on a liberal distribution of power with some hard limits. Generally, staff are encouraged to act as equals until rank becomes necessary or relevant, either through duty requirements (an administrator is above a moderator in an appeal, for example) or when it comes to making decisions.		The SPLURT staff team is not tall in nature, and instead relies on a liberal distribution of power with some hard limits. Generally, staff are encouraged to act as equals until rank becomes necessary or relevant, either through duty requirements (an administrator is above a moderator in an appeal, for example) or when it comes to making decisions.

	===== 1.1 Management ~~Roles~~ =====		===== 1.1 Management Team =====
	These roles are responsible for the overarching administration/management of either the server or a specific server function. While not listed for redundancy's sake, all staff are beholden to all rules in these guidelines.		These roles are responsible for the overarching administration/management of either the server or a specific server function. While not listed for redundancy's sake, all staff are beholden to all rules in these guidelines.

Line 294:		Line 294:
	** Ensuring that the rules are enforced by other members of staff;		** Ensuring that the rules are enforced by other members of staff;
	** and The delegation of power.		** and The delegation of power.
	* '''Head Eventmin:''' There is one Head Eventmin slot on SPLURT, but an administrator may take the role of Interim Head Eventmin in the absence of one. Their duties include:
	** The opening, screening, shortlisting, selecting, and closing of '''event''' staff applicants & applications;
	** Handling staff complaints on Eventmins and Trial Eventmins;
	** Promoting Trial Eventmins, or ruling that they have failed their trial period;
	** Approving major events (events impacting >50% of the current active station population);
	** Running their own events.
	* '''Head Maintainer:''' There is one Head Maintainer slot on SPLURT. Their duties include:
	** Fixing issues posted on the GitHub;
	** Handling balance concerns or complaints raised by members of SPLURT (staff or players);
	** Managing administration-related PRs;
	** Feature implementation, coding, and spriting.

	===== 1.2 Moderation ~~Roles~~ =====		===== 1.2 Moderation Team =====
	These roles are responsible for the general maintenance of the discord and game server, and moderate the general community.		These roles are responsible for the general maintenance of the discord and game server, and moderate the general community.

Line 336:		Line 325:
	** Sricter adherence to SPLURT staffing guidelines is expected for the duration of their trial period.		** Sricter adherence to SPLURT staffing guidelines is expected for the duration of their trial period.

	===== 1.3 Event ~~Roles~~ =====		===== 1.3 Event Team =====

			* '''Head Eventmin:''' There is one Head Eventmin slot on SPLURT, but an administrator may take the role of Interim Head Eventmin in the absence of one. Their duties include:
			** The opening, screening, shortlisting, selecting, and closing of '''event''' staff applicants & applications;
			** Handling staff complaints on Eventmins and Trial Eventmins;
			** Promoting Trial Eventmins, or ruling that they have failed their trial period;
			** Approving major events (events impacting >50% of the current active station population);
			** Running their own events.

	* '''Eventmins:''' Eventmins are our event staff. Admin abuse rules are enforced more liberally on Eventmins, as they are expected to mold the experience for other players through the use of their administrative tools. Their duties include:		* '''Eventmins:''' Eventmins are our event staff. Admin abuse rules are enforced more liberally on Eventmins, as they are expected to mold the experience for other players through the use of their administrative tools. Their duties include:
Line 351:		Line 347:
	** Stricter 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.

	===== 1.4 ~~Miscellaneous Roles~~ =====		===== 1.4 Maintainer Team =====

			* '''Head Maintainer:''' There is one Head Maintainer slot on SPLURT. Their duties include:
			** Fixing issues posted on the GitHub;
			** Handling balance concerns or complaints raised by members of SPLURT (staff or players);
			** Managing administration-related PRs;
			** Feature implementation, coding, and spriting.

	* '''Maintainers:''' Maintainers ensure the codebase remains up-to-date, without bugs/exploits, and also make feature/code/sprite contributions to the server. Their duties include:		* '''Maintainers:''' Maintainers ensure the codebase remains up-to-date, without bugs/exploits, and also make feature/code/sprite contributions to the server. Their duties include:
Line 357:		Line 359:
	** Ensuring PRs are balanced, with consultation to Administrators and Head Admins;		** Ensuring PRs are balanced, with consultation to Administrators and Head Admins;
	** Feature implementation, coding, and spriting.		** Feature implementation, coding, and spriting.
			*'''Server Spriters:''' Server spriters are volunteer individuals who are only expected to contribute solely to sprites. They may occasionally be compensated for their work. Their duties include:
			**Sprite implementation, coding, and spriting.

	= Staff Complaints & Appealing =		= Staff Complaints & Appealing =

Toastewoofs: /* 0. Hierarchy */

2026-04-29T20:55:04Z

0. Hierarchy

← Older revision		Revision as of 20:55, 29 April 2026
Line 271:		Line 271:
	The current staff hierarchy is as follows:		The current staff hierarchy is as follows:

	[[File:~~staff hierarchy~~.png]]		[[File:Staff structure.png]]

	==== '''1. Roles, Responsibilities, & Functions''' ====		==== '''1. Roles, Responsibilities, & Functions''' ====

Toastewoofs: /* Event Team Standards */

2026-04-29T20:49:55Z

Event Team Standards

← Older revision		Revision as of 20:49, 29 April 2026
Line 229:		Line 229:
	* If applicable, members of the event team must ensure any PR(s) on the GitHub pass all checks (excluding linters);		* If applicable, members of the event team must ensure any PR(s) on the GitHub pass all checks (excluding linters);
	* Members of the event team may run faction events without approval;		* Members of the event team may run faction events without approval;
	* Members of the event team hosting or co-hosting a faction event ~~'''~~must~~'''~~ be present for the duration of the event;		* Members of the event team hosting or co-hosting a faction event must be present for the duration of the event;
	* Members of the event team should respect the current chaos level, unless players pass a vote allowing the member of the event team to increase the chaos beyond expected levels;		* Members of the event team should respect the current chaos level, unless players pass a vote allowing the member of the event team to increase the chaos beyond expected levels;
	* 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.

	====== 2.1.3 In-Round Events: ======		====== 2.1.3 In-Round Events: ======

Toastewoofs: /* 2. Event Classifications & Guidelines */

2026-04-29T20:36:15Z

2. Event Classifications & Guidelines

← Older revision		Revision as of 20:36, 29 April 2026
Line 206:		Line 206:

	==== '''2. Event Classifications & Guidelines''' ====		==== '''2. Event Classifications & Guidelines''' ====
	There are three types of events that members of the event team are expected to run: Major Events, Faction Events, ~~and~~ 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").

	====== 2.1.1 Major Events: ======		====== 2.1.1 Major Events: ======
Line 241:		Line 241:
	* Members of the event team may not cause or summon any round-ending events, with respect to the likelihood that spawning said event may end the round (for example, kudzu is extremely unlikely to end a round);		* Members of the event team may not cause or summon any round-ending events, with respect to the likelihood that spawning said event may end the round (for example, kudzu is extremely unlikely to end a round);
	* Members of the event team must respect the current chaos level, and may not attempt to create or pass a vote allowing the member of the event team to increase the chaos beyond expected levels.		* Members of the event team must respect the current chaos level, and may not attempt to create or pass a vote allowing the member of the event team to increase the chaos beyond expected levels.
			Additionally, OPFORs are also included as a kind of In-Round event. OPFOR applications a member of the event team approves are their sole responsibility, and these are treated as an in-round event for the levels of expected impact. Any awry actions an OPFOR applicant takes that are '''reasonably''' foreseeable from the content of the OPFOR are at the fault of the event team member, and they are liable to be punished according to the staff punishment process.

	==== '''3. Event Guidelines''' ====		==== '''3. Event Guidelines''' ====
	Members of the event team are expected to make events for the community and its players, and when running any of the three above kinds of events, they must follow these guidelines.		Members of the event team are expected to make events for the community and its players, and when running any of the three above kinds of events, they must follow these guidelines. Violating any of the above guidelines, or these guidelines, is liable to punishment according to the staff punishment process.

	===== 3.1 Self and Community Service =====		===== 3.1 Self and Community Service =====
Line 391:		Line 392:
	# Reveal the outcome of the complaint and how this outcome was achieved to the complainant before closing the ticket.		# Reveal the outcome of the complaint and how this outcome was achieved to the complainant before closing the ticket.

	Appropriate outcomes to a staff complaint involve:		===== 2.1 Staff Punishments =====
			Appropriate outcomes to a staff complaint, or appropriate staff punishments involve:

	* No action. The staff member either hasn't done anything wrong or is receiving a verbal warning.		* No action. The staff member either hasn't done anything wrong or is receiving a verbal warning.

Toastewoofs: /* 2. Ban Guidelines */

2026-04-29T20:27:25Z

2. Ban Guidelines

← Older revision		Revision as of 20:27, 29 April 2026
Line 484:		Line 484:
	There are two types of bans, role and server. Server bans are reserved for rule violations not tied to a specific role. Bans can be loosely appropriated by their severity:		There are two types of bans, role and server. Server bans are reserved for rule violations not tied to a specific role. Bans can be loosely appropriated by their severity:

	* Minor Severity: A third ~~or fourth~~ offense of the same kind (escalating from a note) or an offense done with clear malicious intent but would otherwise be a minor note;		* Minor Severity: A second or third offense of the same kind (escalating from a note) or an offense done with clear malicious intent but would otherwise be a minor note;
	* Moderate Severity: An offense that has shown a disregard for, lack of understanding of, or unwillingness to understand the rules; or an offense done with clear malicious intent but would otherwise be a moderate note;		* Moderate Severity: An offense that has shown a disregard for, lack of understanding of, or unwillingness to understand the rules; or an offense done with clear malicious intent but would otherwise be a moderate note;
	* High Severity: An offense that has shown a disregard for, lack of understanding of, or unwillingness to understand the rules '''AND''' has impacted one or more players in a highly disruptive manner; or an offense done with clear malicious intent but would otherwise be a major-severity note;		* High Severity: An offense that has shown a disregard for, lack of understanding of, or unwillingness to understand the rules '''AND''' has impacted one or more players in a highly disruptive manner; or an offense done with clear malicious intent but would otherwise be a major-severity note;