This defo needs updating
Team Roles
Admin
Top level of chain of command, Reports to Josh
Admin will perform Moderation duties if a less experienced mod is online, if a mod is online and has experience they will be expected to issue infractions and perform moderation duties
Write policy and interpret it for moderators to use
Moderator/MOD
Performs moderation duties when no admin is online, experienced mods will perform those duties whether an admin is online or not.
Moderators report to the Admin team
For now all mods report to Danny
Moderators while they may be used for input are not writers or policy makers for isoVerse
Builder
NOT STAFF
Build for iso only in mvtp build
Build at the warps admins create
Only have permissions in mvtp build
Report to granny
Developer
NOT STAFF
Do not have console access to iso right away, will be working on test server
Not added to git right away
No in-server permissions on iso
Report to Josh
Team Expectations
Staff members have an important job on the server. They are leaders of the community and role models, setting the attitude for everyone else in our community.
We want players to feel welcome, part of the community and above all - safe!
As a member of the isoVerse staff your main responsibility is to ensure the safety of our players and the community by maintaining the rules and being a good role model to other players by being helpful and welcoming.
We will have a zero tolerance to abusers and rule breakers. Please act swiftly when someone reports an issue or if you spot someone breaking a rule. Be proactive but not bullish. A player may not appreciate that their action is not acceptable so be tolerant but firm.
1 Respect everyone at all times
2 Keep the chat clean
3 No client modifications or exploits
4 No griefing, stealing, property damage, or trolling
5 No inappropriate buildings, skins, usernames
Refer to the Wiki for in-depth descriptions of the rules.
We have certain expectations for our staff.
Although we want you to enjoy your time PLAYING isoVerse you need to put staff duties first.
If all staff log on frequently then the task of being staff should be fun and not onerous.
Online Time
Minimum expectations for staff members.
Mod and Admin are expected to be on the server, not AFK, for 6 hours per week.
This is to help answer questions and respond to tickets. Having staff online, especially when new players join, is huge.
Builders are expected to spend at least 4 hours per week, not AFK, working on the build projects.
Media/Dev do not have the same requirements as they do more behind-the-scenes thing.
Media team is expected to make one post per day, run contests, host events, etc.
Absences
Any staff member who is absent from the server for more than 2 weeks will automatically lose their staff rank UNLESS they have notified the Admin Team in advance. We appreciate that holidays happen, school/work can become time consuming etc so please notify Admins if you feel that things will develop that will reduce your playing time. If you are coming up to an exam period we may put your staff role on hold BUT this will only be a temporary arrangement until the end of exams. Please do NOT assume we know you have heavy commitments outside of isoVerse. ALWAYS notify us in advance! Any further delays in your return to isoVerse will result in your position being removed.
Attitude
* As a staff member you are to demonstrate in your game-play the community spirit of isoVerse. It is more than not breaking rules, it is being an exemplary member of the community.
* Be welcoming to all newcomers
* Do not abuse your power
* Don’t voice any criticisms you may have, don’t get into discussions about the server with other players. If you have any issues with isoVerse, a player or staff member then please message the Admin/Owner team.
* Speak politely to all players
* Take an active part in all aspects of the server: even if you aren’t creative, take part in build contests; if you don’t like parkour, at least attempt the easiest run etc.
Helping Others
* When a player asks for staff help, be quick to follow it through. Always be courteous. If a player is constantly asking you for help and rarely does things without you, be gracious whilst reminding them that they should play their own game. Don’t feel obligated to give up your time and resources to help people build or clear land, but it’s always appreciated.
* Staff may have certain perms that players don’t have. DON’T allow a player to persuade you to do things their rank doesn’t allow them to do. Ie on Creative, you may have more WE commands than the player. DO NOT use your advanced commands for their benefit. The same applies to players. If you see player A helping player B by using commands that player B doesn’t have, then please remind them both that it is not allowed.
This is part of our policy on the Rules Wiki page.
Tickets
Remember to check /ticket list when you first log on. The more frequently this is done the shorter the list will be.
Ticket Categories
The main categories for tickets are
Bugs
Check if the player is using the command or feature wrong. Check the wiki to see if they’ve missed something. If not, close it and put it on GitHub issues.
Griefing
The player reporting the grief will need to stand by the grief when writing the ticket. If the grief isn’t visible, close the ticket with a reply saying that. Remember to follow the rules about rolling back (don’t roll back chests).
Do not roll back griefs you find. Only roll back griefs when they are reported by the victim who got griefed.
If you get griefed, as a Staff Member you should always make another member of staff roll it back for you. It can cause discrepancies if you roll it back yourself, so always ask another staff member to rollback your base if you get griefed.
Never roll back only chests. Sometimes people have others move the contents out of a chest and “claim it was stolen.” Therefore, asking if the person had access when rolling back builds is a very important step, as they could be exploiting the system. And typically, when someone griefs they’ll steal items and break the base, indicating a real grief.
When rolling back a grief, always be aware of what chests are in the area you are rolling back, and how big of a radius you put in for the radius. For example someone may have been mining, and put their diamonds away in a chest, realized they’ve been griefed, and then by rolling it back, you remove their diamonds.
Ideas
Bring to the staff discussion channel if reasonable and doable, otherwise close if it’s obviously not possible.
Other
These will require your own common sense. Some things you will be able to deal with, others may need to be escalated to Admin.
Question
Try to answer quickly. If you don’t know the answer, ask other staff members in Discord or staff chat. If you can’t get the answer, escalate it to Admin.
Don’t get into an argument with another player, state the facts and leave it at that.
Some players may question WHY can’t I have my old rank back? I’ve only been gone 4 months. Josh used to let me have it back blah blah… Remind them that isoVerse is a new server and that purchases help to pay for the running of the server. Leave it at that.
Checking and Taking Action
Check Outstanding Tickets
Use /ticket list
/queue
Lists in chat all pending nickname requests.
They are specifically for players to report info and questions.
- If question: answer it and leave it open for a few days, then close if no response
- If bug report: test the bug yourself, ask for more info if necessary, and if it's confirmed please close the ticket and add the issue to our GitHub Issues
- If feature request: Close the ticket saying it’s a great idea and they should post it at isoverse.net/suggestions
Staff, do not create your own tickets. If you see a bug, put it directly in GitHub Issues.
For a list of commands see github lists:
https://github.com/HoshiKurama/TicketManager/wiki/TicketManager-8-Commands
Back to top of page
GitHub
A video Tutorial on how to use the isoVerse GitHub
https://www.youtube.com/watch?v=TXTepRcnhHsal
Commands
These are commands that are available to staff during play. Please use them wisely but do NOT use them to improve your own gameplay - this will result in the removal of your staff status!
Do NOT abuse any of your powers for fun! ie do NOT delete homes/warps unless necessary.
/mod
This gives you /fly and /god mode: but must ONLY be used to assist a player who has called for help, etc. It is NOT a perk of staff rank! Misuse of this (and any other command) will see your rank being revoked! It is a toggled command. Remember to switch it off once you have completed your work! All time spent with this command on are logged for further review.
/gmsp
To go into spectator mode. This should be your default go-to for vanishing If you need to completely hide from the list and show offline.
/gmc
To go into creative mode
/gms
To go back to survival mode
/vanish
A toggle command used to allow you to follow players who are acting suspiciously. Once vanished you can /tpos to reach them quickly and without notification. Once you have completed your task return to normal mode using /vanish.
/stats
/lp user [username] <user> info</user>
Displays information about a user, including their username, primary group, parents, and current contexts.
/webinfo [name]
will only work for players who have linked to the website (and soon Discord) and it can help troubleshoot problems with their linking
Anticheat
/grim
This allows you to check for players who may be using hacks etc during gameplay. . It will reduce the need for staff to try to decide if a player is using a hack.
https://github.com/GrimAnticheat/Grim/wiki/Commands
Chat
/freezechat
This allows you to stop everyone using chat which is useful if someone is spamming. It is toggled on/off
/clearchat
This will clear all the chat so players won’t be able to scroll back over what has been said. Used for inappropriate content that got through the filter.
We are working on a chat channel for staff only
/chatsentry tvn
(toggle violation notification)
This command will show you if there are chat violations occurring that are being picked up by the server and auto-corrected. The command is toggled for on/off.
Climate
/climatechange
This will bring up a list of climate related commands which you can use throughout the server. These commands will be replaced in favor of WorldGuard flags in the future.
Spawner
/spawner [type]
To get any spawner. This is meant to help someone with a given rank get a spawner back if it did not drop as an item when broken with silk touch. Check that they have the required rank to receive it.
Contest
There are various additional commands which will be set by the staff member in charge of contests. These include
/contest open
/contest voting
/contest judging
/contest closed
/contest name [contest name]
Unless asked, please do NOT use these commands.
Player Info
/history (player)
This will bring up the player’s history and include any previous infractions. Use it before issuing a punishment.
/home (player)
This will bring up a list of all the player’s homes. You will be able to tp to them and delete them.
/tradelog
Staff can use /tradelog (player) to bring up a list of all a player's trades. This may be useful if there is suspicious activity in a player's game-play. (Survival/Skyblock)
/dupeip (player)
This will display a players IP address to verify if they are using 2 accounts at the same time.
Claims
/ignoreclaim
Used to interact with blocks on a claimed area while helping a player.
/abandonclaim
To remove a claim created by a player while standing in it. This is usually used in cases of griefing such as a player claiming an area/build that belongs to someone else, or too close to a claim/build without taking permission.
/is bypass
Allows you to build/mine/harvest etc on any island!
/rg bypass
Bypass the official spawn claim protection
Player Inventory and Chests
/open
Various similar commands that allow staff to investigate what a player is holding/storing in various places. If you suspect a player of stealing you can check if they are carrying the stolen items and you can remove them. You may also add to a player's inventory.
/openinventory (player)
allows you to look at a player's inventory. The top three lines are the inventory, 4th line is their hotbar and 5th is any armor they are wearing.
/openender (player)
/openchest (player)
/backpack (player)
/restart
This command is ONLY to be used if a server is struggling. It will kick ALL players from the server and either send to the hub or kick them from isoVerse if it is the hub being restarted. Please warn players that you are about to restart a server. The command is not immediate so do not repeat it whilst waiting. You can restart individual servers by putting their name after restart
/restart survival /restart creative /restart parkour /restart skyblock
/rules
This will bring up a list of the rules. Suggest a player use this command to remind them of our rules.
/speed
Staff may use this from 1 - 20. 20 is VERY fast! Players who have donated will have access to /speed 1-5 only.
Teleport :
/tp
/tp (player)
As staff you have extra tp commands at your disposal. The standard /tp (player)will send a request to the player. Please use this for most situations, including if a player has asked you to come and see a build they’re working on.
/tpo (player)
This allows you to instantly tp to a player without waiting for them to accept. It will be announced that you are there. Use this for staff duties like checking a grief or teleporting to a player needing staff help.
/tpo (x y z)
This will tp you to an exact co-ord…
/tpos (player)
This must only be used when you are vanished. It will not announce you and the player will be unaware of your presence. This command is useful if you suspect a player of using illegal mods and you want to track them. Most useful if you suspect a player of using x-ray as you can follow them, passing through blocks etc. Before making a decision about x-ray, ask another member of staff to come and check as well.
/send (player) (server)
This will send a player to the named server
MultiVerse
/mv List
Shows a list of all worlds on the server.
/mv tp (Name of World)
Teleports you to a specific world
/mv who
Shows which players are in each world on the server
/glist
opens a gui to veiw the players on each server
Warp:
/warp
The warp commands are greater for staff than players and allow you to delete warps etc. If a player reports a dangerous warp, you can delete it for the safety of other players. Use the Warp GUI for this.
/wb bypass
Allows all players to bypass the world border. Please do not use it as the worlds are pre-generated and going past the border will BREAK dynmap.
/wb bypass (player)
Allows you to toggle on/off the world border. Only use this for yourself if you are working on an area outside of the current world border on survival spawn in preparation for a future extension to the world.
/gwarp
Create global warps which are for builders and staff.
World Edit:
/wea
Allows you to use WE anywhere in Creative. Remember you should NOT abuse your powers to help other players build something that they don’t have the permissions for.
Player Shops
The plug-in that we are using is InsaneShops.
Graves
/cleargraves or /fixgraves :
This removes the hologram that lingers after the grave is recovered or expires.
Also may be used to remove the hologram left by as removed shop chest.
Back to top of page
Violation Actions (Warn/Kick, Mute, Ban)
On isoVerse we want all players to enjoy their experience and to feel safe. For this reason your primary role is to ensure players abide by the rules. If a player is beginning to show signs of breaking a rule - borderline chat violations, remind them to check the rules.
Players who are blatantly breaking rules should be banned. Players who may not realize they are breaking a rule should first be given a warning. A chat violation results in /mute.
Our new system is simpler than previously and has fewer steps!
Before issuing bans, check the Plan network site for the player history. If they have already been warned for the same offense then a ban is applicable. If they have already received a ban then a permanent ban will be more suitable. You can also check their /history (same as their infractions).
General Flow of Minor Chat Infractions (based on their previous /history). Minor chat infractions don’t usually need to result in a ban, since we can restrict their chat easily.
1. Verbal warning
2. /warn
3. /mute 1-3 days
4. /mute 3-7 days
5. /mute 30 days or permanent mute
General Flow of Major Chat Infractions (based on their previous /history)
1. /warn
2. /mute 1-3 days
3. /mute 3-7 days
4. Permanent mute, or ban if the chat offence was really bad
/warn- if they are online and not AFK, or offline
/kick - if they are online and AFK
If a player is breaking a lesser rule such as mini-modding, advertising etc then initially just a word in chat is sufficient. If they repeat the action then give a warning. You must give a reason so the player knows what they are being warned about.
Good example
/warn Joshwenke repeatedly advertising his new server
Bad example
/warn Joshwenke ads
/mute
This command requires a time specification (you can use s (seconds), minutes, hours etc.) otherwise the player will be permanently muted! (I know -tempting for some players!). Use mute for repeated chat violations of any nature but remember to be specific in the reason. Be sensible with the length of ban times, make them relevant to the crime! Do not mute a player for one offense, only if they repeat the offense after a verbal warning. A player who comes on and spams can be muted immediately as they are often only online to antagonize.
Good example
/mute 1d Joshwenke repeatedly swearing in global chat
Bad example
/mute 10d Joshwenke spam
Discord: !mute
/ban
This one command is very powerful. Without the time specification the player will receive a permanent ban although they will be able to appeal.
Good example
/ban Grannysue using x-ray despite warnings and previous 2d ban
Bad example
/ban Grannysue mini-modding
Use a time specific ban relevant to the crime!
Remember to use mute for chat violations and later /ban if they continue after the mute has ended.
Punishment reasons
Every time you "punish" a person (either by banning, warning, muting), use one of the following reasons for the punishment. Please be specific with your reason as it is what the player will see. Below is an example of reasons you may give.
1. "swearing": any form of swearing (signs, etc) or attempting to bypass the filter
2. "advertising": any form of sharing links or names to other servers
3. "spamming": repetitive repeating of phrases or words
4. "griefing": destruction of other people's stuff, includes stealing
5. "disrespect": any form of harassment or defiance to the staff or other players
6. "racism": specifically being racist
7. "nazi": building, using, or talking about nazi symbols, includes nazi skins
8. "nudity": wearing of a skin that displays nudity, or building nude structures
9. "exploits": any abuse of exploits, this can be small or large
10. "caps": talking with too many capital letters (do not use unless the filter is broken)
11. "minimod": trying to be a staff member and annoyingly telling users what to do and not to do
12. "hacking": using client mods (x-ray, etc) — proof required, do not use out of speculation
13. "English": speaking languages other than English
Griefing
Griefing is probably the trickiest thing to know what to do with. It’s applicable to all servers, and all block actions are tracked. If the owner of a house/base/area has reported a grief on their property, please follow this protocol:
1. Ask the griefed player to show you where the griefing happened, if the coordinates were not supplied.
2. Use /core inspect command to find what happened and get the griefer name, if any.
3. Once the griefing is confirmed and the griefer is known, if the griefer is still online, talk to them and explain/remind them that we do not accept griefing, and the consequences of it. You can refer to the rules.
4. Remove/reverse the griefing:
1. Ask the griefer to repair the damage and return items taken. Most players will promise not to grief again.
2. If they are not online or do not repair the damage and return the items taken: Roll it back
5. Check the griefer's /history, to see if they have any previous similar infractions.
6. In case of first infraction: issue /warn and that should be sufficient.
7. If you find previous infractions in their /history : then they must be banned.
8. clear their inventory. They may have gotten some items from the grief, so try to get rid of those if you can.
Chat issues
There are various chat offences that a player may be guilty of, our chat filter should be able to automatically block 99% of spamming, caps, advertising, flooding, etc. It is not necessary for staff to issue warnings or infractions for chat offenses since the filter will handle it (and you can watch the filter process in real-time in chat-filter on Discord). The only exception when staff need to get involved is when people are trying to bypass the filter, and of course when players are being hateful/rude/disrespectful. The main thing is to determine whether it is a blatant violation of the rules or a slip of the tongue or in some cases a matter of not understanding that a particular word/phrase is not acceptable. It is your role to determine which category the offence falls into and punish accordingly. If you are unsure of ANY punishment, always check with another member of staff. Use the staff channel on Discord as someone is nearly always available for help.
Disrespect
We take disrespect very seriously. If you see any form of disrespect, or if a person is disagreeing in a violent way with a staff member, please /mute.
Mini-Modding
Mini-modding can be very annoying. There's a difference between a friendly tip and a constant, obsessive, and telling players what they should and shouldn’t do. Obviously if no staff are online a friendly word from another player to remind someone of the rules is ok. If a player sees a build that breaks the rules, they are best to open a ticket and report it. Encourage the mini-modder rather than correct a player that a friendly tip is ok but if they see a player repeatedly breaking the rules and there are NO staff online then to take a screenshot and report it.
Racism/sexism etc
If you see people being racist, please /mute and /warn. If it is a repeated offence then ban!
Using Languages other than English
If a player speaks in a language other than English in global chat, first remind them we are an English speaking only server. Generally there is no need for further warnings etc but if they persist then use /mute for a short period of time. If on their return they continue then extend the time period.
Nazi Symbols
Any form of nazi symbols will result in a ban.
Nude Skins / Buildings
If you see people with nude skins, warn them and tell them they have a few minutes to go change their skin to something appropriate. If they don't comply, use /ban.
If you see nude buildings, remove them and /ban the player for a couple of days. If the player repeats the offense then do a permanent ban.
Check the user's /history, see if they have any infractions for similar reasons as this one
Process for Inspecting and Rolling back a grief
CoreInspect is the system that we use to check griefs, rollback griefs, track x-rayers, and a lot more. CoreInspect commands will only work if you run them correctly and include all the information.
YouTube video, about 20 minutes:
https://youtu.be/JwijCiueZ3Y
/co inspect or /co i.
Either right or left clicking a block will bring up the information about what happened at that location.
Before you roll back the grief, make sure the user who is responsible for breaking the blocks is not trusted by the owner of the land.
When you have the information you need and are sure the action was griefing rather than trusted work you will need to decide how far back to rollback the area.
/co rollback or /co rb
/co rb p:[playername] r:[radius] t:[time]
* Radius is the number of blocks affected from roughly the central point. Don’t go mad! Be realistic
* Time can be measured as “s” for seconds, “m” for minutes, “h” for hours, “d” for days, “w” for weeks, and “m” for months. Use the information gained from /co i to determine when the griefing took place.
EXAMPLE ROLLBACK: “/co rb p:Brraadd r:15 t:50.6h” This will roll back everything in a 15 block radius within 50.6 hours ago that Brraadd has broken.
After rolling back, check whether the griefer has a history and punish accordingly. For a persistent griefer, a permanent ban must be issued.
X-ray
If you have reasonable suspicion that someone has been using xray, but stop when a staff member comes online you can use a lookup function in CoreInspect.
/co lookup or /co l
/co l p:[playername] block:[block] t:[time].
EXAMPLE LOOKUP: “/co l p:Brraadd block:diamond_ore t:50h”.
This will show you every block of diamond ore Brraadd has mined in the last 50 hours, and will give you the exact coordinates that the blocks were mined. You can teleport to the coordinates and examine if the player was in fact using xray by checking if other blocks were mined in the area or whether a player has gone straight for hidden diamonds.
Things to remember:
1. If you are a new staff member, you are expected to know these guidelines as thoroughly as a long-term Admin would know them. Ignorance is not a valid excuse for making mistakes. If you are ever uncertain about whether to issue an infraction or not, or how to resolve a situation, always ask another staff member if there is no admin, to come on and help you. Two opinions are always better than one!
2. If you are a Moderator and there is an Admin online, have the Admin carry out any punishments (or at least check with them before issuing any infractions.) This should be followed for newer staff; more experienced staff will probably not have to do this.
3. Refer players to the Wiki for help with commands. If someone asks how to do something, refer them to the wiki so they also see all the other commands and will have to ask less questions in the future. Ie “how do I claim land? Answer “use /claim”
4. Please stay updated with other wiki pages as well. Know every page like the back of your hand so you can assist people on the spot. This includes knowing our policies so you can take advantage of your commands in an effective, but proper way.
