Adminning Policy - Revision history

Huhm: Updated HeadAdmin and Community Manager

2026-03-12T19:41:48Z

Updated HeadAdmin and Community Manager

← Older revision		Revision as of 19:41, 12 March 2026
Line 28:		Line 28:

	=== Head Admin ===		=== Head Admin ===
	On the same level as the Head Maintainer / Host, with a focus towards admin affairs. They are solely responsible for hiring new Admins and ~~Community Moderators, and with the support of the Senior Admins~~ they are responsible for handling demotion procedure. They are also expected to handle rule clarifications and mediation when an issue arises between staff.		On the same level as the Head Maintainer / Host, with a focus towards admin affairs. They are solely responsible for hiring new Admins and they are responsible for handling demotion procedure. They are also expected to handle rule clarifications and mediation when an issue arises between staff.
	*Duties:		*Duties:
	#Running once-a-month open applications for Admins		#Running once-a-month open applications for Admins
Line 39:		Line 39:

	=== Community Manager ===		=== Community Manager ===
	This role is directly under the Head Admin~~, same as the Senior Admins~~, and their primary duties lie in assisting the Head Admin with communication on behalf of the staff team to the rest of the community, as well as representing the Funky community to external communities. They also directly manage the Community Moderators.		This role is directly under the Head Admin, and their primary duties lie in assisting the Head Admin with communication on behalf of the staff team to the rest of the community, as well as representing the Funky community to external communities. They also directly manage the Community Moderators and hire new ones.
	*Duties:		*Duties:
	#Handling hiring / demotion of Community Moderators with the assistance of the Head Admin		#Handling hiring / demotion of Community Moderators with the assistance of the Head Admin
Line 65:		Line 65:
	==== Trial Admin ====		==== Trial Admin ====
	This is the very base orientation phase of an Admin, they do not have spawning or View Variable permissions and are just expected to get a handle on moderation duties, community duties, and general conduct. Trial Admins should get first dibs to handle any ahelps that arise in-game, and a more senior admin should only help with advice / step in if requested, or if the situation escalates.		This is the very base orientation phase of an Admin, they do not have spawning or View Variable permissions and are just expected to get a handle on moderation duties, community duties, and general conduct. Trial Admins should get first dibs to handle any ahelps that arise in-game, and a more senior admin should only help with advice / step in if requested, or if the situation escalates.
	The Head Admin ~~and Senior Admins~~ should keep a tab on the Trial Admin's progress, and after 2-4 weeks make the decision on whether or not to promote them.		The Head Admin should keep a tab on the Trial Admin's progress, and after 2-4 weeks make the decision on whether or not to promote them.
	*Duties:		*Duties:
	#Ingratiate yourself with the staff team!		#Ingratiate yourself with the staff team!
Line 124:		Line 124:
	#Don't interfere in another admin's planned event without communication.		#Don't interfere in another admin's planned event without communication.
	#Limit yourself. If you're doing an event every round / other round, you're doing it too frequently. Events should be well thought-out, and not everything needs to be a bit. This is waived for exceptions such as: teaching new players on Sundays, or adjusting gamerules / adding antags for round balance reasons.		#Limit yourself. If you're doing an event every round / other round, you're doing it too frequently. Events should be well thought-out, and not everything needs to be a bit. This is waived for exceptions such as: teaching new players on Sundays, or adjusting gamerules / adding antags for round balance reasons.
	#Trial & Junior Admins should not run events of any scale without ~~admin/senior~~ admin oversight. Exception is granted for minor things e.g. giving Cargo a mail teleporter, or CC fax responses that do not include anything of substance being sent/promised to the crew.		#Trial & Junior Admins should not run events of any scale without admin oversight. Exception is granted for minor things e.g. giving Cargo a mail teleporter, or CC fax responses that do not include anything of substance being sent/promised to the crew.
	#Always log events in the event logs channel, even small ones.		#Always log events in the event logs channel, even small ones.

	=== Scheduling ===		=== Scheduling ===
	#Scheduled events include any event that will substantially affect the game from the start of the round to the end, including any relying on manipulating mechanics or player behavior outside of roleplay.		#Scheduled events include any event that will substantially affect the game from the start of the round to the end, including any relying on manipulating mechanics or player behavior outside of roleplay.
	#A ~~Senior~~ Admin must greenlight the scheduled event (post it in the event ideas channel for this), and at least two full-admins must be available to oversee the entirety.		#A Head Admin must greenlight the scheduled event (post it in the event ideas channel for this), and at least two full-admins must be available to oversee the entirety.
	#Events requiring scheduling should be primarily planned to run on Fridays.		#Events requiring scheduling should be primarily planned to run on Fridays.
	#Event frequency on Fridays is more lax compared to other days, but is limited to one event every other round.		#Event frequency on Fridays is more lax compared to other days, but is limited to one event every other round.

Huhm: Seniormin gone2

2026-03-12T19:38:20Z

Seniormin gone2

← Older revision		Revision as of 19:38, 12 March 2026
Line 100:		Line 100:
	==== Against the Head Admin or Host ====		==== Against the Head Admin or Host ====
	#If the complaint is about the Host, then the Head Admin will review it. If the complaint is about the Head Admin, then the Host will review it.		#If the complaint is about the Host, then the Head Admin will review it. If the complaint is about the Head Admin, then the Host will review it.
	#If the complaint also requests that a regular admin review it, ~~then the Senior Admins will discuss~~ if it is worthy enough to review, then gather a team of 5, including themselves, to review the complaint.		#If the complaint also requests that a regular admin review it, if it is worthy enough to review, then gather a team of 5, including themselves, to review the complaint.
	#The review process is the same for both.		#The review process is the same for both.

Line 177:		Line 177:
	#Strikes will expire 2 months after they are applied.		#Strikes will expire 2 months after they are applied.
	#At two strikes, event privileges will be revoked.		#At two strikes, event privileges will be revoked.
	#At three strikes, demotion will be brought up to a randomly picked group of ~~five~~ Admins.		#At three strikes, demotion will be brought up to a randomly picked group of 5 Admins.

	=== Demotions ===		=== Demotions ===
	#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.		#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.
	#The demotion process may be started by the Head Admin or Host.		#The demotion process may be started by the Head Admin or Host.
	#To demote a member of staff under normal procedure, a randomly picked group of ~~five~~ Admins must pass it by 2/3 majority, including the Head Admins.		#To demote a member of staff under normal procedure, a randomly picked group of 5 Admins must pass it by 2/3 majority, including the Head Admins.

Huhm: Remove traces of Seniormin

2026-03-12T19:10:38Z

Remove traces of Seniormin

← Older revision		Revision as of 19:10, 12 March 2026
Line 173:		Line 173:
	=== Strikes ===		=== Strikes ===
	#Strikes are formal written warnings from the Head Admin to any member of staff.		#Strikes are formal written warnings from the Head Admin to any member of staff.
	~~#The Head Admin is required to notify the Senior Admin team of any strikes given.~~		#They are a last-resort tool to be used on the track to demotion or lesser punishments, where minor corrections will not suffice and major admin policy breaks have occurred.
	#They are a last-resort tool to be used on the track to demotion or lesser punishments, where minor corrections will not suffice and major admin policy breaks have ~~occured~~.
	#While strikes aren't necessary for demotions in extreme cases (e.g. leaking of PII or other explicitly illegal activity), they are recommended to be used in cases of an admin abusing their tools or position over the playerbase, including breaches of admin policy or ingame rules in an unprofessional and consistent manner.		#While strikes aren't necessary for demotions in extreme cases (e.g. leaking of PII or other explicitly illegal activity), they are recommended to be used in cases of an admin abusing their tools or position over the playerbase, including breaches of admin policy or ingame rules in an unprofessional and consistent manner.
	#Strikes will expire 2 months after they are applied.		#Strikes will expire 2 months after they are applied.
	#At two strikes, event privileges will be revoked.		#At two strikes, event privileges will be revoked.
	#At three strikes, demotion will be brought up to ~~the Senior~~ Admins.		#At three strikes, demotion will be brought up to a randomly picked group of five Admins.

	=== Demotions ===		=== Demotions ===
	#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.		#Demotions are to be used only in extreme scenarios where an admin has consistently or extremely broken admin policy, and no other correction is feasible.
	#The demotion process may be started by the Head Admin or Host.		#The demotion process may be started by the Head Admin or Host.
	#To demote a member of staff under normal procedure, ~~the Senior~~ Admins must pass it by 2/3 majority, including the Head ~~Admin~~.		#To demote a member of staff under normal procedure, a randomly picked group of five Admins must pass it by 2/3 majority, including the Head Admins.

JoulesBerg: /* Guidelines */ Clarification on CC events

2025-09-12T04:12:38Z

Guidelines: Clarification on CC events

← Older revision		Revision as of 04:12, 12 September 2025
Line 139:		Line 139:
	#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.		#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.
	#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.		#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.
	#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors		#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors. Antagonist ghost roles / combat focused non crew roles should be avoided.

	== Ahelps and Notes ==		== Ahelps and Notes ==

JoulesBerg: /* Guidelines */ Add clause about central command post round events

2025-09-11T16:54:38Z

Guidelines: Add clause about central command post round events

← Older revision		Revision as of 16:54, 11 September 2025
Line 139:		Line 139:
	#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.		#If you end up running an event that ruins the round (it happens, minor things can spiral very quickly), it is recommended to apologize and give antag tokens to affected antagonists.
	#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.		#Keep events player-friendly. Run them based on what's good for the round and players rather than what's funny to you at the moment. A good example is sending an ERT when half of the station is dead and 2 dragons are running free. A bad example is spawning yourself in as a deathsquad agent 15 minutes into the round.
			#Events and role play at Central Command (post round) are generally allowed as long as they do not dramatically interfere with post round role play or encourage no-roleplay and EORG adjacent behaviors

	== Ahelps and Notes ==		== Ahelps and Notes ==

JoulesBerg: /* Whitelists */ add recent policy to mark whitelists as pending when clarification needed

2025-09-11T16:51:42Z

Whitelists: add recent policy to mark whitelists as pending when clarification needed

← Older revision		Revision as of 16:51, 11 September 2025
Line 108:		Line 108:
	#If the name is odd or something about the individual's profile tips you off, check their username for any active ban appeals. If none are found, they should be good to whitelist with no questions.		#If the name is odd or something about the individual's profile tips you off, check their username for any active ban appeals. If none are found, they should be good to whitelist with no questions.
	#If an active ban or ban appeal is found, it is encouraged to ask why in a private thread. Current precedent is recent active bans on other servers may require a successful ban appeal before whitelisting.		#If an active ban or ban appeal is found, it is encouraged to ask why in a private thread. Current precedent is recent active bans on other servers may require a successful ban appeal before whitelisting.
			#If a whitelist fails to pass the standards, it should be set to pending until the issues are solved, or denied with a minimum 1-week time requirement to re-apply.

	==== Replay Reviews ====		==== Replay Reviews ====

JoulesBerg: /* Head Admin */ update policies with most recent additions

2025-09-11T16:49:55Z

Head Admin: update policies with most recent additions

← Older revision		Revision as of 16:49, 11 September 2025
Line 35:		Line 35:
	#Making sure ban appeals and admin complaints are handled in a timely manner		#Making sure ban appeals and admin complaints are handled in a timely manner
	#Mediating and resolving any conflicts that arise within the staff team		#Mediating and resolving any conflicts that arise within the staff team
			#Organizing a staff meeting once a month
			#Adjusting admin policies as they see fit

	=== Community Manager ===		=== Community Manager ===

JoulesBerg: /* Community Duties */ remove time transfers from the wiki, we no longer do them

2025-09-11T16:45:48Z

Community Duties: remove time transfers from the wiki, we no longer do them

← Older revision		Revision as of 16:45, 11 September 2025
Line 76:		Line 76:
	== Community Duties ==		== Community Duties ==
	All admins regardless of position are expected to do and check these regularly, as it is a large part of their out-of-game duties. If not claimed, the Head Admin may assign any of these to any admin as they deem fit.		All admins regardless of position are expected to do and check these regularly, as it is a large part of their out-of-game duties. If not claimed, the Head Admin may assign any of these to any admin as they deem fit.

	~~=== Time Transfers ===~~
	~~#Players can make tickets in the #create-a-ticket channel, following the format found within.~~
	~~#All role time is transferred with the exception of Overall, Security, and Command playtime~~
	~~#Apply times through the Time Transfer Panel (add time)~~
	~~#Leave a note on the player that time has been transferred so there are no duplicate time transfers made~~
	~~#If there is a duplicate time transfer, set all their times to 0. They brought it on themselves.~~

	=== Ban Appeals ===		=== Ban Appeals ===

JoulesBerg: /* Ranks / Structure */ Remove Senior Admins from the wiki as the role no longer exists

2025-09-11T16:43:51Z

Ranks / Structure: Remove Senior Admins from the wiki as the role no longer exists

← Older revision		Revision as of 16:43, 11 September 2025
Line 21:		Line 21:

	== Ranks / Structure ==		== Ranks / Structure ==
			[[File:Rank Structure.png\|thumb]]

	=== Head Maintainer / Host ===		=== Head Maintainer / Host ===
	On the same level as the Head Admin, with a focus towards development.		On the same level as the Head Admin, with a focus towards development.
Line 30:		Line 32:
	#Running once-a-month open applications for Admins		#Running once-a-month open applications for Admins
	#Promoting Admins		#Promoting Admins
	#Heading disciplinary action on Admins~~, and demoting with Senior Admin approval~~		#Heading disciplinary action on Admins following internal procedure
	#Making sure ban appeals and admin complaints are handled in a timely manner		#Making sure ban appeals and admin complaints are handled in a timely manner
	#Mediating and resolving any conflicts that arise within the staff team		#Mediating and resolving any conflicts that arise within the staff team
Line 42:		Line 44:

	=== Admin ===		=== Admin ===
	==== ~~Senior Admin ====~~		==== Full Admin ====
	This is a hand-picked 'council' of admins who have proven themselves to have an excellent fundamental grasp on everything from policy to training. Decisions made by the admin team and Head Admin will typically pass through this group for confidence, including Head Admin and Community Manager candidates.		This is a full admin, trusted with full access to PII (IPs, HWIDs, connection log) on the admin website, access to the full-admin chat, and access to other administrative tools.
	*Duties:
	~~#Assisting the Head Admin with orientating new Trial Admins~~
	~~#Being an active mentor for all other admins up to and including~~ Full ~~Admins~~
	~~#Acting in an advisory role to the Head Admin and Host for all important decisions~~
	~~#Assembling groups for admin complaints~~
	~~#Voting on matters regarding the demotion of a member of staff~~

	~~====~~ Admin ====
	This is a full admin, trusted with full access to PII (IPs, HWIDs, connection log) on the admin website, access to the full-admin chat, and access to ~~the Adminbus~~.
	*Duties:		*Duties:
	#Assist in acting as a mentor to Junior and Trial Admins		#Assist in acting as a mentor to Junior and Trial Admins
	#Be able to handle the server independently and clarify rules when needed		#Be able to handle the server independently and clarify rules when needed
	#Be able to handle and moderate large-scale events with the assistance of 1 other admin		#Be able to handle and moderate large-scale events with the assistance of 1 other admin
			#Participate in discussions related to policy, rules, enforcement, and other important server business
			#Participate in assembled groups for the handling of admin complaints

	==== Junior Admin ====		==== Junior Admin ====

Taydeo: /* Notes */

2025-06-13T18:29:36Z

Notes

← Older revision		Revision as of 18:29, 13 June 2025
Line 168:		Line 168:
	#Notes not ahelped over should be secreted, as are notes that are for a player 'toeing the line' rather than breaking a rule.		#Notes not ahelped over should be secreted, as are notes that are for a player 'toeing the line' rather than breaking a rule.
	#Notes that were a formal warning should be visible.		#Notes that were a formal warning should be visible.
			#Notes that are over 3 months old should be considered as expired.
			#Expired notes should not be considered when issuing punishment, unless permitted by the Head Admin.
			#Expiry of Ban Notes should start after the ban has either been appealed or expires.
			#Notes that fall under the Non-grouping and Language sections of the banning policy are exempt from expiry.

	=== Watchlists ===		=== Watchlists ===