Arsentic Guidelines And Documentation

This documentation is the official guidelines and documentation for Arsentic ® and is to be followed at all times. This document may be updated at any time without notice. Breaching any of the following will result in various consequences. If you have any questions or concerns, please address them to the management team. Last Updated 10/9/2020. Written by: Alexersion.

Terms Of Service

Any violations of terms of service may lead to serious consequences. Any dispute over the terms of service must have had an attempted arbitration paid by the Plaintiff. Any offenses to the terms of service will be capped at a fine of 1000 dollars USD. By joining this community, you will take full responsibility for any harm that may come your way; including but not limited to death, emotional pain, depression, and/or theft. Any violations against the terms of service may be adequately retracted by the ownership team. Please note that the terms of service may change at any point in time, and the selected user is given full responsibility to uphold these changes. As a staff member, one will be given access to certain information that should not leave the staff team and channels. Certain teams may require you to sign an NDA (Non-disclosure agreement) before joining. Breaching an NDA can result in us taking legal action. You are required to keep all information from the staff team to yourself, you cannot tell community members about anything that has not been made public. This applies even if you have not signed an NDA. Leaking information can result in a demotion and ban from the community. If any rules have been broken, the party responsible will most likely be issued a strike but punishments will vary depending on the staff member in charge and the severity of the rule broken. By joining Arsentic, you hereby agree to the following terms and conditions...

Section 1: Vulgar Language

There will be no vulgar language whatsoever tolerated within the discord, website, and Minecraft chat. One can only be exempt from this rule by the ownership team.

• Article 1.1: Vulgar language such as racial, sexual, gender, or general diction is unacceptable to use within this community and on all of its platforms.
• Article 1.2: Bringing up traumatic events such as shootings, bombings, family issues, or deaths as an insult or for malicious intentions is prohibited.
• Article 1.3: Any discussion revolved around politics or religion anywhere in the world is prohibited.
• Article 1.4: Any form of NSFW, sexual talk, sexual seduction, sexual jokes, messages, images, reactions, links, or memes are prohibited.
• Article 1.5: Talking about someone such as a player, partner, or staff member in a insultive, incriminating, or accusational way is prohibited. The solution around this problem is to report the user at fault in our discord or forums.
• Article 1.6: Inappropriate nicknames such as political, religious, or vulgar language is prohibited. There will be various punishments or changes that may be imperative for the user to accept. This rule will be enforced when necessary.
• Article 1.7: Although this rule is light, it is important to talk in English as much as remotely possible. We might have some non-english speakers, but keeping this rule as an idea is very much relevant.
• Article 1.8: Attempting to bypass the word-limit or the abuse of repeated characters is strictly prohibited. This can be considered spam and the party at fault may receive spam-like punishments for this offense.
• Article 1.9: Slur baiting and using strategies such as spoilers and or pictures with malicious intentions are prohibited in our community. If there is any suspicion of racial or political slurs then further investigation and punishments may occur.

Section 2: Mass Pinging

Mass pinging in the discord including roles, users, or bots is prohibited within the community discord.

• Article 2.1: Pinging roles, users, or bots in the form of repetition or spam is prohibited in the community discord.
• Article 2.2: Pinging roles, users, or bots for no urgent reason, or for reasons outside of the purposes of our community is prohibited.
• Article 2.3: Pinging staff or support team roles in tickets to grab attention or to speed up processes is prohibited.
• Article 2.4: Mass channel mentions are also prohibited for no apparent reasons or for spam and annoyance.
• Article 2.5: Spamming in any way and in any circumstance, is prohibited. Any violations against this rule can result in the suspension of a rank or a mute.

Section 3: Advertising

Advertising in any way, without administrative permissions is prohibited.

• Article 3.1: Under no circumstance is one allowed to advertise in discord channels or DM's without the role of Affiliate or Partner.
• Article 3.2: Affiliates and Partners agree to advertise only when allowed to, and if so, in a specified channel and time made clear by the current executives and management.
• Article 3.3: Advertisements such as videos, images, links, messages, or DM's are strictly prohibited. Any course of action can be taken if this rule is violated.
• Article 3.4: Advertisement in any way through DM's is prohibited in our community's platforms. This rule is taken very seriously as we value the safety of our users.

Section 4: Staff Respect

All users will have respect and follow the moderation of our staff team members. Staff team members are all required to listen to other staff members who are higher ranking unless it is contradicted by one of the owners.

• Article 4.1: Any and all staff disrespect is prohibited in any circumstance and may lead to major consequences regarding the party at fault. If one has a problem or issue with a staff member, the best solution is to report that staff member on our forums or discord.
• Article 4.2: Staff disrespect to administration, managers, or owners is prohibited in any circumstance. Any of these roles have full and final say to any situation. Violations against this rule may result in the removal of the party's staff rank.
• Article 4.3: If one disagrees with staff say or terms, contact the management team in DM's or create a ticket about your issue. If the given party talks about their issues in a public chat, most likely the issue at hand will be disregarded completely.
• Article 4.4: Above all roles and ranks in any of our platforms, the owners have final say no matter the circumstance. Any attempt to directly argue or defy an owner's terms will be followed with an unforgiving punishment.

Section 5: Leaking and Redistribution

Any leaking or redistribution of our products, software, or private information is prohibited under all circumstances. Devastating actions will have to be taken if this section is breached.

• Article 5.1: Under no circumstance is one to leak, redistribute, or claim our products as their own. A full copyright strike and other actions will be taken.
• Article 5.2: One may not leave reviews on our own or client's products for the purpose of harassment, manipulation, or blackmail. Blackmailing or harassing the seller to improve or alter his/her product in any way is harmful to our community.
• Article 5.3: If we decide to quit our service before the product is distributed or finalized for various reasons, this will be acceptable. Refunds and other policies will be discussed on a case to cases basis.
• Article 5.4: We do not accept charge-backs. Charge-backs in any way will result in a punishment from our community. We appreciate the hard work that goes into our staff member's time. Discussing charge-backs before commiting the action is acceptable.
• Article 5.5: Any release of private or personal information is not permitted under any circumstance. This includes addresses, legal information, locations, ages, or IP addresses. A complete wipe and banishment for any user that violates this rule is completely necessary. The safety of our members are a number one priority in our community.
• Article 5.6: Here at Arsentic we have a no-refund policy. We will not refund anything from any of our branches of the company under any circumstance. This is in place to help us protect the server against legality and chargebacks to prevent scamming. We may exchange items if the wrong item was bought and if the matter was brought out into our support system. There is no guarantee that this will occur. Payments and chargebacks will result in legal actions against the party at hand.

Section 6: Minecraft Server Rules

All of the following rules are under the category of our Minecraft server community. Any violations against these rules will have severe consequences.

• Article 6.1: Any form of hacking such as fly, kill aura, bee-hopping, tracers, and free-cam are strictly prohibited. Any form of hack clients or mods can lead to a series of drastic consequences.
• Article 6.2: Finding bugs and bug hunting is okay. However, exploiting bugs for personal gain, entertainment, or other purposes that don't help the progress of the server is strictly prohibited. If there's a bug, please report it to our staff team. Duping falls under this category.
• Article 6.3: No alternate accounts above the limit of 3 are allowed. Any alternate accounts that are used for the purposes of banishment evading, mute evading, or other evasions of our guideline punishment protocols are strictly prohibited. An internet protocol banishment will most likely result in this action.
• Article 6.4: Combat logging is not allowed on the server. Combat logging in any way, shape, or form such as /spawn commands, disconnecting, or abuse of warps is unexceptable. These things will be blocked on our server but abuse of possible bugs could result in certain measures.

Section 7: Staff Guidelines

All staff members under all circumstances must follow our guidelines and rules without exceptions. Any verbal or physical punishments used against community members will be considered abusive if it's not explicitly explained in the documentation.

• Article 7.1: If one does not know how to handle a situation or have the permissions to punish a certain community user accordingly, one must contact a higher staff member about the matter with any evidence if necessary.
• Article 7.2: The management team has the full power to demote or punish a staff member if necessary. There are no exceptions to immunity. The warning strike system will be used periodically.
• Article 7.3: There is zero tolerance for going against member guidelines, bullying, harassing, or using racial slurs against other staff members or players. Strikes or demotion will be used if necessary.
• Article 7.4: We take staff activity very seriously here at Arsentic. We know that you have a life outside of Discord and Minecraft and we respect that. However, we are an official company and we do expect some type of warning or heads up. We want you to be able to live your life and help us out on the server. One is allowed to take any breaks as long as the terms are followed. Any breaks shorter than three days are excusable as long as a valid explanation is in place afterwards. Any break which exceeds more than three days must be submitted via a LOA request on the forums. Proper formatting is required. Holidays are excusable under all circumstances. Failure to comply may result in a warning or a demotion.
• Article 7.5: One is not allowed to punish other staff members unless they have the permission(s) to do so.
• Article 7.6: Under no circumstance is one to use their staff permissions to intimidate or invalidate other users and staff members. We do not take staff abusing litely. This may be on any of our platforms. Staff members must be respectful of their peers and the community. Scams or harm to community members and staff peers are unexceptable.
• Article 7.7: Staff members are expected to hold some type of maturity among most and be role models for the community. They are not allowed to use unprofessionalism around the open community. Staff members must always express themselves in a professional and mature manner. Staff members are representative of the server and it's community so high expectations of maturity is expected. Repeated instances of immaturity and drama-causing may lead to a demotion or complete removal from the team. Keeping a professional demeanor at all times, even when dealing with difficult players is expected.
• Article 7.8: Staff members under all circumstances are not allowed to participate in contests, events, giveaways, or payouts for special community-based events. Depending on the level of your rank, you may not compete on our server for top payouts or invite rewards.
• Article 7.9: Staff members under all terms are not allowed to leak private information about the server without consent from the management team.
• Article 7.10: Under no circumstance is a staff member allowed to ask for IRL currency of actions or value in-game for staffing-related solutions.
• Article 7.11: All staff members must follow the staffing punishment guide to punish users. Punishing users with no evidence or with the lack of proper form is unexceptable.
• Article 7.12: All staff members must respect the community and answer any questions or support request no matter the circumstance. Completion of staffing tasks is required unless there is a certain obligation going against the capabilities of completing a certain task.

Section 8: Forums Rules

We take our rules very seriously. Many of the following may be repeated but it is important to understand our rules and guidelines for our forums pages. The forums bring together the community giving everyone a platform to share their experiences and suggestions. The following rules are of guidance to obtain a safe atmosphere on our forums platform.

• Article 8.1: Under no circumstance can one pretend to be a staff member on the forums. This may include similar names and/or in some circumstances profile pictures.
• Article 8.2: Necroposting, offtopic posting, advertising, spam, spam mentioning, spam dislikes, asking for likes, post or like farming, irrelevant bold colors or italics, and double posting may result in medium punishments depending on the offence. All of these things are super annoying and not allowed on our forums community.
• Article 8.3: Ban or punishment evading with alts or accounts of friends is unexceptable under any circumstance. This would result in an automatic ban on our forums.
• Article 8.4: Strong and inappropriate language as well as disrespect and rudeness is unacceptable on our forums. Those will lead to somewhat larger warnings and punishments on the forums.

Arsentic Rewards And Payouts

Here at our community, we host global giveaways, contests, and events for the community. These events may happen at random times or at periodic times like holidays. Ongoing rewards like invite rewards, trailer-reuploads, and boost rewards would be ongoing until otherwise said. Different types of rewards that may be given out include in-game perks, Buycraft currency, PayPal payouts, Discord perks, Forum perks, and more. These rewards were intended to boost player activity and help expand the community. If you have any inquiries whatsoever, don't hesitate to ask a staff member for help.

Rewards:

• Our said invite rewards are coming soon.
• Our said trailer re-upload rewards are coming soon.
• Our said Discord boost rewards are coming soon.
• Our said IS and F top payouts are coming soon.
• Weekly, monthly, and holiday-events are to be released and are coming soon.

Staff Screenshare Guide

Here, you'll find tips and tools that will help you during screen share sessions between yourselves and players you suspect cheating. Players may have access to this guide to familiarize themselves with the processes on our server. Do not ask or force players to download cracked screen sharing tools or tools that are not certified and proven to be safe. All screen share tools must be verified by a senior staff member from the management team. If there is a threat related to DDoS or Doxing, report the threat to a high ranking staff member immediately. Do not spam them unless it's an absolutely immediate threat. Gather as much evidence as possible.

Step 1. The Basics

Freeze the player in-game by typing "/freeze <player>" and give them around six to eight minutes to join a support channel. Make sure to move them to a private channel and notify other staff members that a screen share session is taking place. More staff members in the call will be good for better judgement. Make sure that only one staff member is directing the session. Record the session if necessary. Make sure to give the person a chance to admit to hacking / cheating for a shortened ban punishment. If they end up refusing to admit to hacking, call them on discord for a screen share session. Once you're in a call with the user, ask them to press their F3 key or left-shift key. These keys commonly enable a modular hacking GUI. Make sure to take any screenshots of their cheating. Look carefully for any hack client inferences on their screen. If you have caught them from any of the processes above, make sure to punish them accordingly. If you do not have permissions, make sure to contact another staff member who has permissions. Use the ban reference sheet for more help on ban and punishment times.

Step 2. X-Ray

If you are in suspicion of an X-Ray hacker by either seeing that they have a lot of rare ores or monitoring their anticheat alerts, you may want to use the following strategies to check up on them. Make sure to use the command "/invsee <player>" to first confirm your suspicions. The first thing that you can do is to make sure that they open their resource pack folder and settings. Look for an X-Ray resource pack. You may want to have them try out any and all resource packs in case one is renamed as something else. If they do not have an X-Ray resource pack, you may want to follow the steps in part one to check and see if they're using built-in X-Ray hacks inside of a hack client.

Step 3. Self Destructive Clients

Self destructive clients can and will be found inside of one's mods folder. Have them open up their Minecraft mods directory. If they are using forge, compare and contrast their mods folder with their mods in-game. If anything doesn't seem right, try having them open up the mod that doesn't work with a decompiler application such as winrar or unarchiver. If that mod doesn't work or pop up as damaged then it's considered a self-destructed client. Self destructive clients may be disguised inside of the directory "shaders/forge installers/bspkrs/<Anything>". Self destructive clients may also be in a %temp% folder. Search for "agent" and "BSP" in their temp folder. If they have anything like an agent or BSP, check the time to make sure that the user has recently used the files. If so, they have used a self destructive client.

Step 4. Injection Clients

Injection clients are one of the harder clients to find. Make sure to check their recently visited places. If they have anything related to a USB or weird folders, start checking those. Some of the folders may be at the bottom so make sure to check those as well. If the person's Minecraft crashes while changing a resource pack, it will most likely be because of a self-destructed client. Another trick that someone may have. They might hide their actual Minecraft directory inside of a resource pack folder or something such as that. Make sure to go through their resource pack folder. To check and see if the directory is true, have them delete a resource pack and check and see if the live edits appear onto their client. Check their client logs to make sure that everything looks okay. Ask for them to send you their logs folder zipped if necessary.

Step 5. Common Ghost Client Sizes

Some users rename their clients when downloading it to something like "Keystrokes Mod" to make you think that they're not cheating. If you believe that this is the case, tell them to right click on the file and then take a look at the properties of that said file. Once you've opened the properties of that said file, check for the following sizes. "Flux for 2.25 megabytes", "Vape Client Lite for ⅗ megabytes", and "Java Legacy Fixer for 5-7 kilobytes". If the Java Legacy Fixer file is more than 5-7 kilobytes, make sure to decompile that said file. For 1.17.10 clients, BSPKRS-Core-Universal-6.16 clients are commonly self-destructive clients that will be in a mods folder. When you open the file, it would come out as damaged. Those files are commonly 92 to 110 kilobytes. BSP is 194 kilobytes. Once you find a file that you want to decompile with Winrar, press "find" on the winrar tabs. Click on the "string to find" button and not the "file to find" button. Search for "trig/kb/aim/velocity". Sometimes, you will find strings there but don't ban them off of those unless it says "hacks", "triggerbot", "aim assist", or something along those lines.

Beta Program

Our Beta program is super relaxed and open for many to come and try out our beta servers, projects, bots, clients, and more ahead of time. Lots of rewarded perks are traded for your time and expertise to try out our server and services as much as possible. It is expected that there will be bugs. You are to report all and any bugs that you may find. To apply for beta testing, see your application section of this document or make a ticket on the Discord. You can also apply on our forums. Once and if you are accepted, you will be given special beta perks and a beta role on our Discord. That will entail access to our beta chat channel. You are expected to follow our beta terms and protocol.

Responsibilities:

• You may try to break and place blocks in any protected areas unless otherwise said not to. Regions are one of the last things that we do on the server so it would make sense if some areas would be breakable when they shouldn't be. Checking for errors in our builds is also a responsibility.
• Are may test any commands with any permissions. You will be temporarily given top rank and other ranks to test command, permission, and language message abilities.
• You are allowed to swear and attempt to bypass chat filters. Occasional hacking is allowed as well to check the anticheat. Unless otherwise specified, you are not allowed to do this.
• You may test any glitches or duplication glitches that you might think would work.
• You may test our voting system to make sure that links and rewards work correctly. Player linking and other things follow this rule.
• Adding to suggestions for things to add or change, or just anything of the sort.
• You may not leak any information, bugs, or new changes/updates that have not been made public at that given moment.
• You may not report false bugs or errors in our builds for trolling purposes or for your own personal gain.
• You may not force any refunds from the beta phrase if you have bought something on our server. We will usually provide BuyCraft credit for you to use in-game for beta testing anyways.
• You may not advertise any other platform or media to our community in such a situation. Even if it's just yourself, outside and competitor servers are not allowed.

Staff Responsibilities

Whether you're a staff member or not, understanding each role's responsibilities, expectations and tasks before applying or asking for help is important. One couldn't possibly apply for any role in our community without fully understanding the full tasks and responsibilities required of that said role. Therefore, make sure to read this section to the fullest and take any notes on this. Be sure to remember that tasks and abilities may vary and change or may change at any given moment. Individual tasks out of the exception of the role are not included within the bounds of this section.

Rank: Owner

• The role of the owner fluctuates the most. The owner has to be available to do anything and everything for the server.
• The owner must fund or provide some sort of economic value to the project.
• The owner must keep progress within the server steady.
• The owner has the final say and is incharge of high-tier tickets and staffing procedures.
• The owner must plan out the server direction and start sorting out tasks and responsibilities.
• The owner must set deadlines and a timeline for the server's progress and completion.

Rank: Manager

The role of manager is split into three somewhat blended sections. General management, community management and HR management.

• General manager: is the overseer of the other management teams. That job is required to have experience in all fields of management and will assist the other managers if needed. They are also responsible for helping the owner(s) and recruiting staff members.
• Community managers: are responsible for reaching out to the community via our different platforms. They inform the community on events, updates and anything else that has changed or needs to be said. They will also collaborate with the general manager(s) on creating and sending out server advertisements to help the server grow.
• Staff manager: are tasked with making sure that all the staff members are adequately trained and know how to respond. They will also work closely with ownership and the other managers to train the staff, create documents, run meetings, striking staff members, sending out messages to keep staff informed. They will also help staff resolve drama.

Rank: Administrator

• Administrators are responsible for helping lower staff achieve their tasks. They also will help management with tasks that they need help with.
• Administrators will mainly be working with the community manager and the Arsentic community.
• Majority of the time, administrators will be responding to tickets unless it's a simple thing that a moderator and trainee can handle.

Rank: Developer

The role of the developer is fairly broad. There are various types of developers, each with their own expertise and part of the server. However, the end goal of all of the developers is the same. Fix bugs and update the progress on the backend development itself.

• Website and system administrator developers are in charge of the custom web relations and making sure that everything systematically is secure and set up correctly with minimal bugs. Once the main gist of this required position is finished, the bugs and additions aspect may come into play furthermore.
• The plugin development aspect is fairly straightforward. Follow the manager's or owner's requests in what to specifically code and howso. This position is where custom plugins and features get created. Bug support is also expected of this position as well as occasional configuration bug support.
• Configuration development will be minimal as a selective owner does have exceptional expectations for this field. Configuring language files and following the instructor's per-said instructions is non-negotiable to maintain this position. Any and all configurations will be done on their own test of a private server. Configurations will be tested and double checked upon completion.

Rank: Moderator

The moderator position is somewhat similar to the trainee position. Minimal skill and expertise is required for this position. In order to reach this position, one must get screenshared verified. Moderators are expected to be active and complete any and all requests given by the administration and management team to the best of their ability. Teaching trainees and learning new things for the reasonable support of the server is expected. Required playtime on the server for trainee and moderator positions may be required if minimal work is put in. Other staffing procedures such as but not limited to the completion of the trainee staffing training guide must be earned and completed.

• Moderators will be able to answer basic questions in support tickets.
• Moderators will be able to hunt hackers and punish them accordingly. They will also respond to tickets that address hackers.

Rank: Builder

The builder role is among the most important of the server with much skill. High-levels of building experience and involvement are required for this rank. This rank will follow management-handed assignments to work on as well as improving on previous builds. World edit and design are expected to be known by at least one member of the build team. The build team is expected to work together to get assignments and maps done. This position will not see a definite end as the need for builds is great.

Rank: Trainee

As a trainee, your job is fairly simple. Moderate chat(s), look for bugs, moderate players, and add to the suggestion pool. This role is just a baseline for our server. We want trainees to be able to help with any and all small tasks given to them. No prior skill or expertise is required although we do inquire about some sort of professionalism.

Rank: Partner [Excluded from staff activities]

As a Partner, your role on the server is to help the community grow. By creating content, posting updates, or doing whatever was assigned, you're helping us grow our platform. Partners will have a larger community-based status and will have access to special perks for their followers. Following our community guidelines and advertisement rules are also apparent for this role.

Rank: Affiliate [Excluded from staff activities]

As an Affiliate, your role on the server is to help the community grow. By creating content, posting updates, or doing whatever was assigned, you're helping us grow our platform. Affiliates will have a smaller community-based status and will have access to special perks for their followers which would be limited by their audience size. Following our community guidelines and advertisement rules are also apparent for this role.

Rank: Beta [Excluded from staff activities]

The Beta role is of importance. One who has this role should not abuse their power by leaking server updates or features and exploiting bugs. The Beta role is in place to help us test for bugs, add suggestions, and help with any and all testing. Activity when necessary and some sort of professionalism is required. The Beta role will have access to limited-edition perks and server secrets on the server. Any revealing of these said sneak peaks are disallowed and is a bannable offence.

Staff Strike System

Please take the time reading the Arsentic Staff Strikes Guide as it will help you navigate our unique strikes system. If you have any questions please consider messaging a manager. Please note that we retain the right to remove you from the team without prior notice.

What is a strike?

A strike is a form of punishment designed to help members of the team learn from their mistakes. If you were given a strike you should learn to avoid that mistake and grow from it. Getting a strike isn't the end of the world.

How do I receive a strike?

A strike is given to a member of the staff team when they break one of the rules of the server or the staff rules agreed upon when joining the team. Other reasons may include lack of maturity, toxicity towards members of the team and general disrespect to higher-ups. To check the rules and staff rules, please locate them on this document and the Discord server respectively.

What are the repercussions for having too many strikes?

If you gain 3 strikes you will be demoted. Getting three strikes means that you obviously don't care about your position on the team. Strikes are issued when a member of the team breaks a rule. The only way for a strike to get removed is if you learn from your mistakes and have shown the administrators your sorrow. Another way is for you to do a good deed for the team and the community. This can be many things so we will keep our eyes out!

How will I know when a strike is issued to me?

Once you have gained a strike, an administrator or above will DM you explaining the rule you broke.

Punishment Guide

This guide will teach you how to punish a user based on what rule was broken. Please try your best to follow this guide but make sure that the punishment "fits the crime". Please make sure that you log the punishments accordingly. Punishments are listed in sections and are followed by the appropriate step. Please make sure that punishments are logged CORRECTLY and ACCURATELY so another staff member can properly punish someone. Punishments will be listed as such: Username, infraction broken with proof, and length of punishment.

Section 1: Vulgar language.

• Infraction 1.1: 24 hour mute.
• Infraction 1.2: 1 week mute.
• Infraction 1.3: 1 week ban from platform used. (Example: Discord server.)
• Infraction 1.4: 1 month ban from all platforms.
• Infraction 1.5: Permanent ban from all platforms.

Section 2: Mass mentioning in the Discord server.

• Infraction 2.1: One warning.
• Infraction 2.2: 24 hour mute.
• Infraction 2.3: 1 week mute.
• Infraction 2.4: 1 week ban from all platforms.
• Infraction 2.5: Permanent ban from all platforms.

Section 3: Advertising.

• Infraction 3.1: 1 week ban from all platforms.
• Infraction 3.2: Permanent ban from all platforms.

Section 4: Staff disrespect.

• Infraction 4.1: 1 week mute.
• Infraction 4.2: 1 week ban from all platforms.
• Infraction 4.3: Permanent ban from all platforms.

Section 5: Leaking and redistributing software and products.

• Infraction 5.1: Permanent ban from all platforms.

Section 6: Minecraft community rules.

• Infraction 6.1: 1 week ban from the Minecraft server.
• Infraction 6.2: 1 month ban from Minecraft server.
• Infraction 6.2: Permanent ban from all platforms.

Staff Training Guide

General Information:

Whenever a new staff member is hired, they will most likely be given the trainee role. This is a common practice with many servers to help buildup a sense of trust with the new staff member. Once that member has completed tasks on time and fulfilled their job in an efficient and professional manner, after some time they may be given a promotion. A promotion should not be automatically expected. Before, during, or after your first day or promotion, you may or may not receive training from a staff member with a higher rank. This training is to help you grow in your abilities as a staff member and to help you perform your job effectively. Each rank, will have a separate training course, each time run by someone higher than you. They are immediately, assigned as your mentor.

Responsibilities:

• If you are a moderator or higher rank, you may or may not be given the responsibility to train lower staff members. (Typically Senior Mod's+ will conduct the training as Mentors.)
• If you are assigned someone to train, it is your duty to make sure that person knows exactly how to do their job and knows how to react in certain situations or conflicts.
• Training should be done in a professional manner and the trainee should respond well to criticism.
• The mentor shouldn't expect too much from their trainee. If the speed or method of training seems overbearing to the trainee, please make some adjustments. Don't push them, afterall we want them all to succeed.
• The goal of training is to help staff members learn and excel at their job. A friendly and sympathetic attitude should be portrayed by the higher staff member during instruction.
• If there are any questions from the trainee or mentor, please don't hesitate to ask a member of the management team.
• Mentor's choose how to mentor their trainee's, as long as they excel in their job's and know their stuff.
• Staff/moderation command knowledge.
• Completed tasks on time and fulfilled their job in an efficient and professional manner, after some time they may be given a promotion.

Training Requirements:

Admin:

Admins should have a vast knowledge about management and their assigned team. Below is a list of requirements you must meet for the administrator position:

• 16+ years of age.
• Mediation skills.
• Very strong communication skills.
• A dedicated and hard-working personality.

Sr. Moderator:

Senior Moderators will have experience as a moderator on Arsentic and will follow the requirements. Below is a list of additional requirements that are needed to be eligible for Senior Moderation:

• Mediation skills.
• Strong communication skills.
• Experience as a moderator.
• 1 month or more of moderation experience.
• Able to defuse arguments within the team and community.

Moderator:

Moderators should have a general knowledge of basic staff commands and how to use them. Below is a list of requirements you must meet for the moderator position:

• Good conversational skills.
• Knowledge of proper punishment durations.
• Ticket handling skills.
• A desire to learn.
• Knowledge of actions to take in common scenarios.