Enforcer Manual 2014
Community Information Edition
The Enforcer Manual 2014 ‘Community Information’ Edition is a resource available for users of the MCME Network who are interested in reading an extract of the Operational Procedures that Enforcers adhere to and follow in the course of their duties on the MCME Network.
The purpose of this resource is to inform users with an idea of what an Enforcer is; their responsibilities, obligations and expectations at a management level.
Some aspects of the Enforcer Manual have not been disclosed such as the Infraction Tables used in handling rule offenses on the MCME Network.
Please be advised that this document may be edited at anytime.
The rank of Enforcer is an authoritative rank within the Minecraft Middle-Earth Administration. Enforcers perform with the duty to moderate the proceedings that take place within the Server Context as well as oversee operations in various other settings through the MCME Network (Teamspeak, Forums)
An Enforcer's primary role are rule enforcers. It is under a Enforcer’s repertoire to make sure that all players adhere to the MCME Terms of Service as well as the Community Rules. The Enforcer is responsible to relegate players who have committed an infraction and deal with the player with the appropriate documented processes, thus Enforcers have the power to issue sanctions such as bans and assigning Oathbreakers under this right.
They have access to an advanced logging tool (Prism), that allows them to discover what happened at any place at any given time. Enforcers process these logs and take evidence whenever someone is banned to justify the measure. They also are in charge of moderating the forums.
It is also within an Enforcer's commitment to ensure that the operations that are integral to the proceedings of the server are not interfered with and that there is no likelihood of deterrence. Enforcers must be proactive in collaborating with other portfolios to ensure that everything is running smoothly. Enforcers can agree to chaperone with Build Mods in order to regulate player activity and to make sure individuals do not act outside authoritative direction under the instruction of the Build Mod. They must never perform with the impression to lead Projects.
Enforcers must act to exemplary standard. They should be just, impartial, act with integrity, must be firm, professional and accountable when within the role.
Enforcers are rule-enforcers of MCME Network and as such, are responsible for overseeing activity of players/users, prevent them from breaking the rules aswell as enforcing the rules. Enforcers are not Build Moderators and must not ever lead a job or instruct a player to perform build related tasks as would normally be coordinated by a Build Moderator. Below is an agenda of what Enforcers ensued to perform specific to an area within the MCME Network:
First and foremost is to check for grief on the build server and to monitor current player activity. This can be done by performing a Prism Search and teleporting to players. Enforcers must use other mediums of monitoring activity such as utilising the Prism Browser. If a player has been found to have committed a rule infraction, than that player must be dealt with accordingly and within good judgment and discretion. If you are unsure of a circumstance than it recommended that you consult with another Enforcer or Administrator.
Enforcers must document all instances of a ban/Oathbreaker.
While it is an Enforcer’s primary responsibility to look for grief or police players, it is also their responsibility if another Staff Member has banned someone from Freebuild to log that ban in the Enforcer doc. It is their responsibility to document all bans from Freebuild since only Enforcers and Administrators can access this doc. Enforcers must acquire relevant screenshots, statements and other means of evidence of the situation and have it documented/recorded as soon as practicable.
An Enforcer's duty is to make sure players are following the rules pertaining to chat etiquette. Remember that this is an open community project where players of all ages are welcome to join. The use of inappropriate language, sexual, vulgar, or discriminatory in nature and political / religious discussions are strictly not tolerated. The moderation of players within a job should be closely monitored as Build Moderators may require assistance with the movement and coordination of players. Although the TheGaffer plugin restricts activity outside an area, that radius area can still be manipulated if a job is executed.
Players should maintain correct etiquette in chat & follow rules when communicating with other members of the community.
Responsibility on the Freebuild has extended to further Enforcer moderation as the Build Server is further secured. The Freebuild, however, is open to player activity thus requiring more surveillance.
While all Staff retain the right to execute Commands such as /ban and /kick, the Enforcer has the running duty and obligation to handle matters. It is the Enforcer’s responsibility to moderate infractions of chat etiquette the same as the build server. All documentation must be followed up accordingly.
Enforcers must document all bans in the MCME officer document with the exact reason you banned from TeamSpeak. Whilst TeamSpeak is distinguished as more informal and a viable setting than chat in-game, it is still within the Enforcer’s responsibility that players do not abuse their TeamSpeak privilege by harassing others, playing music/soundclips in the wrong channel and excessive poking. Players who use our TeamSpeak must display their in-game name or have a name that can be easily distinguished. Failure to adhere to this must be instructed to change their in-game to easily distinguish players.
It must be noted that the handing out of the current TeamSpeak password to players not formally part of this MCME Network (not registered) is prohibited and Enforcers must deal with those who act freely outside this.
The TeamSpeak also has a complaint system integrated into the server. This mechanism shows complaints of players who have reported a person by utilising the complaint function. They are able to state the person they had made a complaint against, the reason behind the complaint, their username as well as the date they had made the report. It is recommended that Enforcers check up on this regularly. Any complaint Enforcers find is up-to their discretion to follow it up.
The forum is a public medium where users are to open to start threads and posts in their sequential board. Enforcers have the responsibility to enforce and moderate the forum through the Terms of Service and Community rules. Enforcers have a few resources in which they are able to assist them with this such as the: Forum Moderation Guidelines and the Forum Infraction Table.
Users are expected to distinguish the rules on the forum medium where Enforcers are there to remind them of that.
When an Enforcer has issued a ban on the MCME Network, they are responsible to record the ban. This is done where the Enforcer is given the premise to record the ban in an Enforcer List Document. The Enforcer list contains various tabs where the setting/medium to which that Enforcer has issued a ban for a user/player, they must supply sufficient evidence and thorough detail of the circumstance of the ban. Enforcers are held accountable if they fail to supply all information in the allocated columns of the tabs. Information should be filled out in the Enforcer List as soon as practicable.
Enforcers are accountable for their issued bans. If a player creates a Ban Appeal (Oathbreaker appealing for Freebuild), then the Enforcer who had issued that ban, MUST address that ban in question and make the determination to judge those appeals accordingly. Players who have been issued 2nd degree Oathbreaker MUST be banned on the Freebuild and documented in the appropriate tabs.
Once the ban appeal has been appealed or denied, lock the thread then wait one week and move to the ban appeal archives.
All documentation of Player Banishments, Oathbreaker, Freebuild Bans are processed through the Google Document ‘MCME Officer Lists’. The document requires strict authorisation upon the request of the Document Creator.
At this point in time, there is no public platform to search player's information. However an enquiry by the player can request this information (why they're Oathbreaker/banned) in the Help Section or messaging an Administrator/Enforcer on the forums.
Enforcers are expected to upload ‘evidence’ to a central Google Drive folder. There is a set procedure Enforcers must follow in order document and record information appropriately. Enforcers would usually investigate an incident and choose what the most appropriate form of evidence would be. Evidence can take the form of recording information utilised through the Prism System. The Enforcer would normally take a screenshot of this and upload with a corresponding filename of the player, the punishment ensued and the date.
The reporting of suspicious activity by members of the community have assisted us in investigating instances where players may of done something that speculated attention. With regards to infractions involving the Terms of Service and Community Rules, an official platform set up by Staff for players to submit a Suspicious Activity report enables Enforcers to cross check and reference where they can extract information from the information provided a make thorough determination.
First Degree Oathbreaker
This system will serve as the same premise of issuing Warnings but will be distinguished as less severe punishment than Oathbreaker Second Degree. This method of punishment will impose to punish people on the basis of assigning them a location (a location less farther than the usual Oathbreaker and teleported to Spawn) and banning them from Freebuild until they reach their destination. Time is not a factor nor is date they have to wait until to be eligible to be promoted back to their former rank.
Second Degree Oathbreaker
This punishment is much more severe and is reserved to players who had done things more detrimental than First Degree Oathbreaker. Players who are restricted to this rank must meet the requirements to reach an assigned location (from Spawn), meet the duration and length of time of their OB rank as well being banned from the Freebuild Server. A player must be overseen of all stages of the process by an Enforcer or Administrator.
Users within the MCME Network who have registered on the forums are able to create threads, posts and discuss certain topics in various sections of the forums. The forums have various areas distinguishing their context and thus people are able to contribute to discussion through its agenda.
When a user has acted outside of the Community Rules and Discussion they are able to be dealt with through the Forum Moderations Guidelines which is only viewed in the Staff Forums.
Issuing a Forum Warning
A user can be issued a warning directly or based on a post they have made. Warnings are segregating in different categories which correspond with the Community Rules and Terms of Service. Each warning also has a varying infraction level with its own point system. There is a certain point threshold when past the Forum system may limit or fully restrict access to the Forums.
Take note that the list of commands below are only there to inform you of the commands that are permissible by Enforcers or Staff. You are not able to execute these commands if not given the perms or access to do so.Admin Chat
Enforcers are able to utilise admin chat which only Staff members can see ingame. To send an ingame admin chat message use /a ‘message’ to send a singular message. To toggle admin chat indefinitely during a session toggle between /a on to turn on admin chat and /a off to toggle off admin chat. Only players who staff are able to see admin chat.
Please note that this function is only accessible by Staff Members.
Prism is an advance logging tool that records all actions a player makes. The tool has the ability to record over 60+ possible events in the Minecraft World. This includes everything from block placing & breaking, chat commands, logins, player interactions with chest to terrain fading and entity actions.
MANY things will not go Unnoticed!
Prism features several different ways to access the information it has stored. Enforcers may search by type of action, area, time and player or any combination of those. You may also view the history for a specific block.
Prism commands begin with /pr or /prism.
Two ways are available to view Prism information, one is through the Prism inspection tool, which is a mechanism that you enable with a 'wand' in your hand (you can use to interact with the blocks around you to view the history of a single block of space). Left click solid blocks to view the history of that block space, right click on non-solid blocks (air, water, lava) to view the history of that particular block space or adjacent block space.
The other way to view information is through console commands. This is done by using the search command along with custom parameters to filter the information you want to see. Prism console command always start with /pr l or /pr lookup. Adding parameters help refine your search to a particular situation and more parameters can be added or reduced to assist this to gain a result.
Once you have executed a successful Prism Search, the server will provide you with a search result on your text screen in-game. Prism has the ability to group searches based on a primary dependent result. For example if a group of players had removed a substantial amount of stone, the result of that search (if the Enforcer had searched for stone block-breaks server-wide) would bring back the players who had broken stone not each individual stone block that was broken (as would of been the case with other event logging Tools).
The other main feature to Prism is the rollback feature which utilises the command /pr rollback. This allows you to undo changes made to the server or to bring the server back to it's original state prior to an event happening. This command uses parameters to control the selection of what you want to rollback similar to inspecting. This command can be thought of as an ‘undo’ command to correct Griefers’ actions. It is essential that Enforcers do a rollback preview (i.e /pr preview rollback) to see what would of been removed if they had executed the command. If an Enforcer is confident in their search they can do /pr preview apply. If they aren't, than they enter /pr preview cancel.
- a:[action] - Like "block-break" (See below for full list). No default.
- r:[radius] - How many blocks near you the action happened, i.e. r:20. Default radius set in config.
- r:global - Instructs Prism to not limit results to a location. Requires special configuration or permissions (Prism 1.6) to be used for lookups/rollbacks/restores.
- r:we - Uses a WorldEdit selection to limit all results - lookups/restores/rollbacks. Works for anything that supports ther parameter. Player must have WorldEdit selection permissions.
- rlayer:[radius] Base a radius off of another online player.
- r:x,y,z:[radius] - Allow a radius around coordinates x,y,z
- r:world - No radius, but limited to the current world or the world specificed by the w: parameter.
- r:c - Limits the radius to the current chunk (x/z of the current chunk, from bedrock to world height)
- b:[blockname/id] - Like b:grass or b:2 or b:2:0. No default.
- e:[entity] - Like eig. No default.
- t:[timesince] - Events after x long ago. Like 1s(seconds), 20m(minutes), 1h(hour), 7d(days), 2w(weeks). No default. Use time arguments together if you wish, like 1h20m.
- before:[time] - Events before x long ago.
- since:[time] - Events after x long ago. Same as t:
- p:[player] - Like p:viveleroi. No default.
- w:[world] - Like w:worldname. Defaults to your current world.
- k:[world] - Text-based keyword search (for commands/chat mainly)
- id:[world] - A single record id.
i.e /pr l <parameters> - (Example /pr l p:TheJessicaAlba a:block-break r:15 b:grass)
That search would show any grass blocks TheJessicaAlba broke in a 15 block radius around your current position.
/pr rollback <parameters> - (Example /pr rollback p:TheJessicaAlba a:block-break,block-place r:15)
This command would undo any blocks placed or broken by TheJessicaAlba in a 30 block diameter circle around your current location.
Important: As stated previously in the Rollback section of this Resource, It is imperative that you use another parameter in conjunction with the player’s name, such as a radius or time. Otherwise you can end up undoing the ENTIRETY of a players actions on the server, and if they have worked on jobs, can lead to quite a mess.
A safer, but more time intensive way of doing a rollback would be to do /pr preview rollback p:TheJessicaAlba a:block-break,block-place r:15
Prism will show you what the changes would be if you are in the area, and they are only visible to you. You can effectively issue the rollback now with /pr preview apply or you can cancel with /pr preview cancel
These are your three main Hawkeye functions. The tool, the search and the rollback. More commands are listed below, which are usually used to support your searches and rollbacks.
- /pr inspect (while holding a log, right click to check air, water, or lava, left click on solid placed blocks)
- /pr rollback <parameters>
- /pr l <parameters> (will execute a search based on your given parameters)
- /pr tp <id> (logged actions will have an ID, this command allows you to tp to that ID number)
- /pr page <number> (Most searches will result in multiple pages of history, use this command to view the pages)
- /ha near (A quick search command to show all changes around your current location within a standard 5 block radius)
The vanish plugin allows you to become invisible to all players without access to the same plugin. On MCME you would only be visible when vanished to other Enforcers and Administrators. This is useful when watching over other players or looking for suspicious behavior and actions.
The command toggles invisibility on/off, while you are invisible item pick up is also disabled as to help maintain your stealth. Use of the compass to travel through walls and avoid opening doors is useful as well.
- /vanish - to vanish or reappear
- /vanish list - to see who is vanished
It is simple to use with a promote player and demote player command being all you need to use. It will promote and demote in the order of rank one step at a time. So promoting an Adventurer will make them Guide and demoting an Adventurer will make them Oathbreaker.
- /pex promote <player> (Will promote player name one rank)
- /pex demote <player> (Will demote player name one rank)
As Enforcers you have the authority to kick and ban players. The player who has used the command must add the reason to the end of the ban/kick command stating the reason. You are also enabled to unban the player whom the ban has been issued too.Take note that the command is NOT case sensitive.
- /ban <player> <reason>
- /unban <player> (On build server)
- /kick <player> <reason>
- /isbanned <player> (will check if a player is banned or not, and gives the result)
- /pardon <player> (unbanning a player on the Freebuild Server)