Staff Guidelines - Revision history

Cyclops at 19:09, 25 September 2017

2017-09-25T19:09:49Z

← Older revision		Revision as of 19:09, 25 September 2017
Line 1:		Line 1:
	~~__NOAUTOLINK__~~		__NOAUTOLINKS__
	This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from the server.		This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from the server.

Line 28:		Line 28:
	\\acceptes @user		\\acceptes @user

	These commands manage roles for Blazing Umbra, [[Angelic Sins]], and Embers of Soteria respectively. They add the proper roles and remove unwanted roles for new players. They can be stacked, so when a character is approved for a new player in each setting, these commands can be used to give the correct roles.		These commands manage roles for Blazing Umbra, Angelic Sins, and Embers of Soteria respectively. They add the proper roles and remove unwanted roles for new players. They can be stacked, so when a character is approved for a new player in each setting, these commands can be used to give the correct roles.

	== Dealing with Offenders ==		== Dealing with Offenders ==

Cyclops at 18:30, 25 September 2017

2017-09-25T18:30:48Z

← Older revision		Revision as of 18:30, 25 September 2017
Line 1:		Line 1:
			__NOAUTOLINK__
	This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from the server.		This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from the server.

Line 29:		Line 30:
	These commands manage roles for Blazing Umbra, [[Angelic Sins]], and Embers of Soteria respectively. They add the proper roles and remove unwanted roles for new players. They can be stacked, so when a character is approved for a new player in each setting, these commands can be used to give the correct roles.		These commands manage roles for Blazing Umbra, [[Angelic Sins]], and Embers of Soteria respectively. They add the proper roles and remove unwanted roles for new players. They can be stacked, so when a character is approved for a new player in each setting, these commands can be used to give the correct roles.

	== First Offense ==		== Dealing with Offenders ==
			Offenders of the rules will try to make it seem like things are not their fault. Here are the most common methods that we need to watch out for and refuse to engage on the basis of:
			* They started it.
			* I was only joking!
			* That rule isn't fair!
			* You are too strict!
			* I see others doing it all the time!

			Any of these excuses, it is important to refuse to engage with. After the 2nd offense, when there is a time involved before the user is allowed to resume normal activity it is also helpful to remember the phrase, ''We will discuss this further when your \whatever\ is lifted.'' This allows everyone time to cool off. I suggest temporarily blocking people in DM if they become a problem, you're allowed to do that. None of this escalates to the level of some kind of emergency service that we must be contactable at all times.

			Put simply. Do not engage. Explain the rule violated, explain what violated the rule, and explain how to avoid further violations. Period.

			=== First Offense ===
	Warn the user that they have violated the rule, ask they not do it again (politely) and verify the user understands the rule and how they violated it. Also make it clear that if they personally disagree with the rule, that is a separate discussion but they must still follow the rule. ''Do not allow the user to get you sucked into a conversation about the validity of the rule or if it is fair, unfair, or anything else. It is the rule, period.'' Please make sure to use the ''\\warn'' command.		Warn the user that they have violated the rule, ask they not do it again (politely) and verify the user understands the rule and how they violated it. Also make it clear that if they personally disagree with the rule, that is a separate discussion but they must still follow the rule. ''Do not allow the user to get you sucked into a conversation about the validity of the rule or if it is fair, unfair, or anything else. It is the rule, period.'' Please make sure to use the ''\\warn'' command.

	== Second Offense ==		=== Second Offense ===
	If the user does not follow the prescribed advise, that is, continues to violate rules, a mute may be required. I prefer to mute between 30 minutes to 2 hours depending on severity and how persistent the user is. I tend not to go over 6-8 hours without a pretty good reason, but use your best judgement. Make sure to explain why in the ''#admin'' channel what happened so everyone is aware.		If the user does not follow the prescribed advise, that is, continues to violate rules, a mute may be required. I prefer to mute between 30 minutes to 2 hours depending on severity and how persistent the user is. I tend not to go over 6-8 hours without a pretty good reason, but use your best judgement. Make sure to explain why in the ''#admin'' channel what happened so everyone is aware.

	== Third Offense ==		=== Third Offense ===
	If after being muted, the user continues to violate the rules. It is time for a long-term mute. I'd say doing a mute for a minimum of 24 hours, but 48 or 72 work very nicely. This allows said user to cool off and consider things if they weren't able to do that the first time. Each 24 hour period is '''86400 minutes'''. So 1 day is that, 2 days is '''172800''' and 3 days is '''259200''' minutes each.		If after being muted, the user continues to violate the rules. It is time for a long-term mute. I'd say doing a mute for a minimum of 24 hours, but 48 or 72 work very nicely. This allows said user to cool off and consider things if they weren't able to do that the first time. Each 24 hour period is '''86400 minutes'''. So 1 day is that, 2 days is '''172800''' and 3 days is '''259200''' minutes each.

	=== DM Idiots ===		==== DM Idiots ====
	A lot of people will get angry at being muted and move to DM's. Feel free to escalate to the next level if they start to do this. If they are going to do that about access to speaking, warn them that any further discussion or trying to evade the mute will result in a ban.		A lot of people will get angry at being muted and move to DM's. Feel free to escalate to the next level if they start to do this. If they are going to do that about access to speaking, warn them that any further discussion or trying to evade the mute will result in a ban.

	== Fourth Offense ==		=== Fourth Offense ===
	Banning then becomes necessary. I would do a ban for 7 days off this. That is '''604800''' minutes. At this point, do not respond to the users in private or public spaces, it is done, the next time anyone will revisit the issue is in 7 days. If there is some kind of conflict on what's going on, I urge all staff members to default to the phrase - ''"We will next revisit the issue in 7 days time but not before."''		Banning then becomes necessary. I would do a ban for 7 days off this. That is '''604800''' minutes. At this point, do not respond to the users in private or public spaces, it is done, the next time anyone will revisit the issue is in 7 days. If there is some kind of conflict on what's going on, I urge all staff members to default to the phrase - ''"We will next revisit the issue in 7 days time but not before."''

	== Fifth and Final Offense ==		=== Fifth and Final Offense ===
	If after a 7 day ban they are still unable to control themselves. A permanent ban is in order, any staff member can issue such a ban. I again refer to the above statement about 7 days. Do not let this escalate to a permanent ban without doing a full 7 days of being banned first. This allows everyone to cool off!		If after a 7 day ban they are still unable to control themselves. A permanent ban is in order, any staff member can issue such a ban. I again refer to the above statement about 7 days. Do not let this escalate to a permanent ban without doing a full 7 days of being banned first. This allows everyone to cool off!

	[[Category:OOC]]		[[Category:OOC]]

Cyclops: /* Fourth Offense */

2017-09-25T17:58:39Z

Fourth Offense

← Older revision		Revision as of 17:58, 25 September 2017
Line 42:		Line 42:

	== Fourth Offense ==		== Fourth Offense ==
	Banning then becomes necessary. I would do a ban for 7 days off this. That is '''604800''' minutes. At this point, do not respond to the users in private or public spaces, it is done, the next time anyone will revisit the issue is in 7 days. If there is some kind of conflict on what's going on, I urge all staff members to default to the phrase - ''"We will next revisit the issue in 7 days time but not before."''.		Banning then becomes necessary. I would do a ban for 7 days off this. That is '''604800''' minutes. At this point, do not respond to the users in private or public spaces, it is done, the next time anyone will revisit the issue is in 7 days. If there is some kind of conflict on what's going on, I urge all staff members to default to the phrase - ''"We will next revisit the issue in 7 days time but not before."''

	== Fifth and Final Offense ==		== Fifth and Final Offense ==

Cyclops: Created page with "This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from..."

2017-09-25T17:58:19Z

Created page with "This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from..."

New page

This document is not meant to do anything except for guide staff in how they might want to deal with particular situations. We generally prefer not to kick or ban users from the server.

== Commands ==
Here are our most useful commands for Staff.

\\warn @user [reason]

This allows a staff member to issue a warning that other staff can read later. It is suggested to do this every time one has to actually warn a user about something.

\\warnings @user

Use this when a user has done something, if everyone uses the ''warn'' command properly, it should allow everyone to know what a given user has done in the past.

\\mute @user [time in minutes] [reason]

This is my preferred tool for dealing with unruly players. It is essentially telling the user to go to their room for a certain amount of time. It doesn't drop them off the server and it protects everyone else from their banter in the server.

\\ban @user [time in minutes] [reason]

Be careful with the ban option, use this sparingly. However, if a user repeatedly offends and becomes disrespectful, please do not hesitate to use it. I always prefer to do a ban for a certain amount of time. This allows someone to come back after a while and play on.

=== Other Useful Commands ===
Here are some other commands for staff members.

\\acceptbu @user
\\acceptas @user
\\acceptes @user

These commands manage roles for Blazing Umbra, [[Angelic Sins]], and Embers of Soteria respectively. They add the proper roles and remove unwanted roles for new players. They can be stacked, so when a character is approved for a new player in each setting, these commands can be used to give the correct roles.

== First Offense ==
Warn the user that they have violated the rule, ask they not do it again (politely) and verify the user understands the rule and how they violated it. Also make it clear that if they personally disagree with the rule, that is a separate discussion but they must still follow the rule. ''Do not allow the user to get you sucked into a conversation about the validity of the rule or if it is fair, unfair, or anything else. It is the rule, period.'' Please make sure to use the ''\\warn'' command.

== Second Offense ==
If the user does not follow the prescribed advise, that is, continues to violate rules, a mute may be required. I prefer to mute between 30 minutes to 2 hours depending on severity and how persistent the user is. I tend not to go over 6-8 hours without a pretty good reason, but use your best judgement. Make sure to explain why in the ''#admin'' channel what happened so everyone is aware.

== Third Offense ==
If after being muted, the user continues to violate the rules. It is time for a long-term mute. I'd say doing a mute for a minimum of 24 hours, but 48 or 72 work very nicely. This allows said user to cool off and consider things if they weren't able to do that the first time. Each 24 hour period is '''86400 minutes'''. So 1 day is that, 2 days is '''172800''' and 3 days is '''259200''' minutes each.

=== DM Idiots ===
A lot of people will get angry at being muted and move to DM's. Feel free to escalate to the next level if they start to do this. If they are going to do that about access to speaking, warn them that any further discussion or trying to evade the mute will result in a ban.

== Fourth Offense ==
Banning then becomes necessary. I would do a ban for 7 days off this. That is '''604800''' minutes. At this point, do not respond to the users in private or public spaces, it is done, the next time anyone will revisit the issue is in 7 days. If there is some kind of conflict on what's going on, I urge all staff members to default to the phrase - ''"We will next revisit the issue in 7 days time but not before."''.

== Fifth and Final Offense ==
If after a 7 day ban they are still unable to control themselves. A permanent ban is in order, any staff member can issue such a ban. I again refer to the above statement about 7 days. Do not let this escalate to a permanent ban without doing a full 7 days of being banned first. This allows everyone to cool off!

[[Category:OOC]]