Guest User

Dp

a guest
Aug 15th, 2016
131
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.73 KB | None | 0 0
  1. Welcome to the DatPixel Staff Handbook for all Staff Members.
  2.  
  3. After you have read this book, you must sign at the bottom stating "I have read all the terms and guidelines from the DatPixel staff handbook."
  4.  
  5. ========================================
  6.  
  7. One of the most important things you have to understand about being a staff member on DatPixel is that you are a representative to our community. You help represent the staff and administration that is the DatPixel Network.
  8.  
  9. Please maintain a professional image on the Network.
  10.  
  11. ===========================================
  12.  
  13. This is a super important topic that I have had to talk about too many times with individuals. What is discussed in the skype chat or even in-game moderator chat needs to stay there. What happens in our staff chat is for our staff to know only unless an administrator says it is ok to talk about outside the moderator circle. This includes but is not limited to: ban reports, ban appeals, new servers being planned, information about player's personal information, opinions about other moderators, etc. Anything that is discussed between the moderator circle needs to stay there. We know you guys get excited about new features at times that we are planning, but for our security's sake THEY NEED TO STAY A SECRET. You are not allowed to discuss things with ex-staff members who have retired in the past or just recently retired also. If they are no longer active staff then they are not to be told anything about the staff affairs. This rule literally will get you fired if you violate it. Make sure you read this paragraph a second time, and if you are unsure about something ask an Senior or Manager.
  14.  
  15. ========================================
  16.  
  17. We understand if you guys get heated or salty at times. If you find yourself in this situation you need to be smart and walk away from your computer until you can be more level headed again. We will NOT tolerate cursing or abusing other members of our community in-game or on the forums because you have a grudge against someone or you are having a bad day. This will get you immediately demoted if you are caught abusing your moderator powers in any way shape or form.
  18.  
  19. If you have a report made against you for abuse please do not respond to it. Let a Manager handle it. Commenting on it only reflects bad on yourself.
  20.  
  21. ========================================
  22.  
  23. As a staff member you are not allowed to act biased. You are to act based on facts and evidence and prior evidence. You are not allowed to act on someone because you have a history with them on another server. An even better example, we don't care if someone on our server has been caught hacking on other servers. If they are hacking on our server too then we take action against them. We do not take action against individuals for their past on other servers, only our server. Also if you are friends, in the same team/faction, etc with someone, you are not allowed to act on their behalf at all and must request another mod to look over the situation. As moderators we must be 100% neutral and not show bias here.
  24.  
  25. ========================================
  26.  
  27. Introducing the staff ranks:
  28.  
  29. Staff Chain (Below)
  30.  
  31. Lowest to Highest
  32. - Trainee
  33. - Mod
  34. - Senior Mod
  35. - Admin
  36. - Manager
  37. - Owner
  38.  
  39. All buycraft issues go to Steven as he's the only one that has access to buycraft.
  40.  
  41. Staff Positions:
  42.  
  43. Senior Mod:
  44.  
  45. (Currently Rafi is a Senior Advisor (Meaning all SrStaff Fall under him) and his duties is the same but, he takes care of all Senior related issues along with DiamondCruster ect.)
  46.  
  47. You do not apply for SrMod.
  48.  
  49. Every 3 Weeks (subject to change) each Mentor makes a report for their assigned staff members to determine their performance on DatPixel. This will help the Managers to determine who is doing well with the network, who needs to improve, and lastly who should be removed. If there is someone you need to not piss off, it is your mentor. Your mentor will stick with you throughout your career at DatPixel unless 1. You become a mentor yourself or 2. There is a serious conflict of interest between your mentor and yourself, in which case an Manager will need to get involved.
  50.  
  51. - Incharge of Maintaining Staff in order with Guidelines
  52. - Incharge of replying to all Staff Abuse Report
  53. - Responsible for determining when a trial is ready to become a full staff.
  54. - Responsible for determining if a trial is not fit to become a Moderator.
  55.  
  56. Moderator:
  57.  
  58. As a moderator, you need to act mature. Being a moderator does not just mean you now have access to the fancy permissions and have exclusive perks over the other non-staff members. Being a moderator means you have a job to do, and we only look for those who can do that job thoroughly and efficiently. To be a good moderator, you must be:
  59.  
  60. Mature (Doesn’t mean you can’t have fun here and there. Just don’t be over the top and ignorant)
  61.  
  62. Active - We need players who will be online when they can, and not be off playing a different server. (This doesn’t mean you can’t go on other servers, but just don’t spend the majority of your time on there and not here where your job needs to be done)
  63.  
  64. Helpful - We need staff who will do their job and help EVERY player that asks for it or seems to need it; not just the players you have befriended or have gotten to know
  65.  
  66. Unbiased - We cannot have staff members that will be biased and/or show favoritism towards certain players. Unbiased staff are good, hardworking staff members which we could use and welcome on the staff team.
  67.  
  68. What is your job?
  69.  
  70. A moderator is supposed to be a helpful and productive staff member which players can turn to for help. As a moderator, you will have to answer players’ questions, deal with player reports on the forums, moderate the chat in-game to make sure players do not break the rules, and help watch for players who are hacking and/or using any sort of method (whether it is an exploit/bug, or a cheat) to gain an advantage over other players. Basically, you are the police who need to enforce the rules. If you are watching for a player that may be hacking, and you are not positive if they are or not, please have another staff member (Sr. Mod or higher) come online to help you watch them.
  71.  
  72. Trainee:
  73.  
  74. When you are hired as a trainee here at DatPixel you are assigned a mentor. This mentor will work with you during your initial time here at DatPixel to help teach you how to do your job.
  75.  
  76. A Mentor as read above is a Senior Moderator.
  77.  
  78. As a Trainee you will not be able to ban but, you have limited powers of position.
  79.  
  80. You may warn a player and may mute players appropriately.
  81.  
  82. To be promoted, you will need to record valid recording of a player cheating and posting it in your Mentor and Trainee chat.
  83.  
  84. If you think the evidence isn't sufficient enough, contact a Senior.
  85.  
  86. (Check below for more infomation)
  87.  
  88. Here to be promoted, you will have Trial Reports.
  89.  
  90.  
  91. Training.
  92.  
  93. Here at your course at DatPixel you will need to learn some things while being a staff members.
  94.  
  95. To start of with:
  96.  
  97. Core Protect
  98.  
  99. Core Protect is the plugin that allows us staff members to help fix griefs. The main commands you will be using as a staff member will be /co rollback and /co inspect. The two commands are described below:
  100.  
  101.  
  102. ----------------------------------------------------------------------------------------------------------------------------
  103.  
  104.  
  105. Core Rollback (Senior)
  106.  
  107.  
  108. /co rollback -- Used to rollback a specific area in which a grief has been committed.
  109.  
  110.  
  111. The parameters for /co rollback (rb for short) are as follows:
  112.  
  113.  
  114. /co rb u:<user> (or p:<player>) t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>
  115.  
  116.  
  117. You probably will never have to use a:, b:, or e: as a moderator. The main ones you will use are u:user/p:player, t:time, and r:radius.
  118.  
  119.  
  120. The letter followed by the colon (u:) must be included when the command is executed.
  121.  
  122. If a player named Notch griefed an area 21.87 hours ago with a radius of approximately 5 blocks (you can just estimate), the command will look like:
  123.  
  124.  
  125. /co rb u:Notch (or p:Notch) t:21.88h r:5
  126.  
  127.  
  128. This restores the area specified within the radius back to how it was the amount of time you input (21.88h) ago.
  129.  
  130. Core Inspect (Mods+ Only)
  131.  
  132.  
  133. Now, when you go to check a grief, one of the most important parts is to make sure you know who did it. To find this out, you would do /co i, which enables core protect inspection mode. While in this mode, you cannot place or destroy blocks. This mode allows you to find out block data (for example, who broke/placed a block and how long ago it was done).
  134.  
  135.  
  136. To find out who placed a block, you would left click on the desired location and you will see the information appear in chat. It will show you how long ago the block was placed and who placed the block.
  137.  
  138.  
  139. To find out who broke a block, you would right click the desired location and the same information appears in chat. This is important as it allows you to find out who griefed the area so you may punish the correct player. It also lets you know how long ago it was griefed, so you know how long to roll it back.
  140.  
  141.  
  142. Another aspect of inspection mode is you may see who put in/took items from chests. All you have to do is right click a chest, and it shows you how long ago the player took/put an item into the chest (and what item). This is important for players who are reporting other players stealing their items. Unfortunately, if you rollback the area, the items will reappear in the chest. But, those items will still be out there with the other player who stole them. So now you’d have twice as many of that item, which may lead to a problem with specific items. To avoid this, you do not rollback the chest until you acquire the other items first. You may then give those items back to the player who lost them. However, if the player only lost some really easy-to-obtain items, you can just rollback the area, as creating more of that item would not be much of an issue. However, be aware that players may attempt to use you to dupe items for them. That’s why it is always important to right click a chest to check if they took the items out instead of other players.
  143.  
  144.  
  145. Core Restore (Seniors Only)
  146.  
  147.  
  148. Now, those are the two commands you will use most often. However, if you mess up on a rollback you do, and you need to fix it, there is always this command. It is /co restore (or /co rs). The parameters of this command are the same as rollback: /co restore u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>. This command can be used to undo a rollback you or another player has done. Meaning, this will redo a grief (if necessary for some reason), and it will redo any actions that had been undone from the previous rollback. It is used the same way as rollback, except the time is reduced to the time you want it to restore to. For example, if you rolled back 8 hours and you rolled it back an hour too far, you can do /co rs t:7h r:<radius> to restore anything that was done within that hour. Any blocks that were placed and removed, or any items that were stored or taken will be redone.
  149.  
  150. Now with Litebans: (Mods+)
  151.  
  152. To ban a player, you use /ban and the numbers of days (let's say 2) and the amount of time (s = second m = minute h = hour d = day)
  153.  
  154. So to ban someone for a week would be:
  155.  
  156. /ban irLaz 7d reason
  157.  
  158. Same thing as mute.
  159.  
  160. This is all you quite need to know with our staff permissions.
  161.  
  162. You have Vanish and are able to TP to any player you want. (Abusing this will lead into a immediate demotion and no chance of receiving staff again)
  163.  
  164. If you have any questions, please PM any seniors and or staff in the group staff chat.
  165.  
  166. NEW: Retired Rank!
  167.  
  168. If you have been a [Mod] for 8+ Months, you are eligible to receive this rank.
  169.  
  170. If you have been a [SrMod] for 3+ Months, you are eligible to receive this rank.
  171.  
  172. Last edited on 8/15/16.
Advertisement
Add Comment
Please, Sign In to add comment