Welcome to ArchaicRealms!
PLAY.ARCHAICREALMS.ORG
Join today!

Official Discipline Guide

Status
Not open for further replies.

Luke

Owner
Owner
Developer
Oct 17, 2019
19
0
20
Preface
On ArchaicRealms, we have a complex and delicate set of rules, so we need to be careful with how we enforce rules. Of course, staff discretion will always remain with the highest member of staff, and we realise the reality that mistakes might be made. However, to minimise this risk, and to offer a level of transparency with our userbase, we have carefully constructed a discipline guide. This guide is useful for staff and player reference.

Discipline
There are a number of different utilities available to staff, depending on the context and magnitude of offence. To keep context in regard, we have made certain offences a "minor" infraction, and some a "major" infraction. For minor infractions, such as being toxic in chat, a warning should be issued (using the plugin). See below for our warning system. For major infractions, a [temporary] ban may be issued, depending on the severity. For most bans, we offer the chance to appeal on the forums, but in rare situations, staff may deny the chance to appeal (such as a ddos attack).

Warning system
For all warnings, they are permanent, and may only be removed by a successful appeal. So, whilst 8 warnings may seem like a lot, for long-time players, they might stack up quickly. This means that staff are only to issue warnings when the situation is severe enough to warrant it instead of a verbal (i.e. chat) warning.
Code:
Warning 1: No punishment.
Warning 2: Kick from server.
Warning 3: Muted on server for 30 minutes.
Warning 4: Banned from server for 30 minutes.
Warning 5: Banned from server for 2 hours.
Warning 6: Banned from server for 24 hours.
Warning 7: Banned from server for 7 days.
Warning 8: Banned from server permanently.
Staff usage
In order to use the plugin properly and effective, it is important that you refer to the commands below when issuing punishment. As a rule of thumb, if it isn't worth your time to check the command syntax, then the player probably doesn't deserve punishment, or you don't deserve to be staff.
Code:
Where <FIELD> requires a variable to be provided, 
[FIELD] is an optional field but usually recommended, 
and (FIELD) is an optional field only to be used for certain scenarios.

"/kick <player> [reason]" - used to kick a player from the server.
"/ban <player> [reason]/(@PermNoAppeal)" - permanently bans <player> from server for [reason]. (@PermNoAppeal will mean that there is no chance of an appeal.)
"/tempban <player> <time>/(#Regular) [reason]" - temporarily bans <player> from server for <time>/(#Regular) because [reason].
"/unban <player>" - removes any existing ban from <player>.
"/ipban <player>/<ip> [reason]/(@PermNoAppeal)" - permanently bans <player> from server for [reason]. (@PermNoAppeal will mean that there is no chance of an appeal.)
"/iptempban <player>/<ip> <time>/(#Regular) [reason]" - temporarily bans <player>'s ip/<ip> from server for <time>/(#Regular) because [reason].
"/mute <player> [reason]" - permanently mutes <player> for [reason].
"/tempmute <player> <time> [reason]" - temporarily mutes <player> for <time> for [reason].
"/warn <player> [reason]" - warns <player> for [reason].
"/unwarn clear <player>" - removes all warnings from <player>.
"/unpunish <player>" - removes all punishments from <player>.
"/warns [player]" - checks warns of [player]. If no [player] is specified, then checks own warns.
 
Status
Not open for further replies.