Staff Guide

Welcome to the DemocracyCraft Staff Guide! This guide contains all staffing policies, tips, and tricks that is used in day-to-day operations. By making this guide public access, our playerbase is informed of the expectations and procedures our Staff are subjected to.

If you are a new hire, first off - congratulations! We’re excited to have you onboard with us. Seeing the table of contents/how long this document is may appear scary at first, but try to remember we don’t expect you to memorise everything. We give you this guide so you know where to refer to when you need help, in addition to your peers.

With enough time, you might end up contributing to this guide!

For Senior Administrators

Console

As a Senior Administrator, you are able to access both the server console and files. To be added to the panel, mention a Manager or Owner in your personal channel, to receive your invitation! You will mainly be using this to configure plugins, fix bugs, and add new features.

Note

There is no one set way of learning how to do these things.

Trial and error, along with general observation goes a long way in helping you form your own way of doing these things.

Tip
Be sure to log any player-facing changes in #changelog, and any internal changes in #internal-changelog. This way we have an accurate record of who’s done what!

For System Administrators

Resetting the Nether and End

In most instances, a Nether and End reset will occur once every 6 months, typically during our quiet hours. This time frame tends to be 10pm EST - 5am EST is the optimal time for this reset.

Steps

Try to make an announcement in #server-announcements one week away for the desired data.
- Make a follow up announcement at least 48 hours before the reset as well to give players a reminder that this is about to happen!

Turn on the whitelist via /whitelist on to ensure those pesky players stay out of our way.
Delete both Reveille_nether and Reveille_the_end using /mw delete <world>.
Recreate both Reveille_nether and Reveille_the_end using /mw create <world>.
Using /gamerule, set keepInventory to false, announceAchievement false, and showDeathMessage to false.
Merge inventories between the worlds by running /mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton.
Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.
Link nether portals correctly via /world netherportal destination Reveille_nether Wilderness and /world netherportal destination Wilderness Reveille_nether.
Run /mw gamemode survival Reveille_the_end and /mw gamemode survival Reveille_nether in Console (without the slash!).
Turn off the server.
Open Reveille_nether/paper_world.yml and add below _version the following from the "Nether Configuration" (Engine Mode 1)
Open Reveille_the_end/paper_world.yml and add below _version the following from the "End Configuration" (Engine Mode 1)
Start the server.
Open the server back up by removing the whitelist. (/whitelist off).
Announce the change in #server-announcements!

For Administrators

How to manage Billboards

We use a plugin called ImageMaps to allow us to implement images in-game via item frames. This plugin is currently how we’re able to make billboards!

Steps

Upload your image to an image hosting service such as Imgur or ImgBB
Download the image in-game by running /imagemap download <filename> <sourceURL>
- Replace <filename> with an easy to identify name, without any file extensions such as .png.
- Replace <sourceurl> with a link to the image, this should include the file extension such as .png.
Place the image in-game by running /imagemap place <filename> [frameInvisible] [frameFixed] [frameGlowing] [size]
- Replace <filename> with the file name you selected in Step 2. Please add the file extension featured in the <sourceurl> you used earlier.
- Replace [frameInvisible] with “true”, no quotation marks. This ensures that players do not see the default item frame texture in empty spaces of the image.
- Replace [frameFixed] with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.
- Replace [frameGlowing] with “false”, no quotation marks. This the frames are not glowing.
- Replace [size] the height (A) and width (A) in the following format: AxB
  - i.e. for a 2 by 2 image, it would be: 2x2
Admire your work!

How to conduct Rollbacks

We use the industry standard plugin CoreProtect to log all of our in-game interactions. This allows us to rollback, inspect, and review any player changes or interactions as they happen.

Commands

/co help - help command; displays all commands.
/co rb; /co rollback - rollback block data based on certain parameters.
- Usage: /co rb u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>
/co undo - revert a rollback.

You can see a list of parameters for these commands here.

Additional Information

Here is a video tutorial that goes other aspects of CoreProtect that are not covered within this guide.

How to manage VPN Bypasses

Players will commonly open tickets suffering connection issues. There are multiple ways we can attempt to solve this, but before anything else get them to turn their router off for at least a minute, and then turn it back on. This is often the simplest solution. See Screening Players For VPNs

VPN

If all fails, this could be a routing issue that cannot be solved through conventional means. Asking the player to use a free Virtual Private Network (VPN) such as Cloudflare Warp.

If you offer this option, please provide the player with the antivpn.bypass permission node in-game.

Administrative Commands

These are useful commands to know with your position.

LuckPerms

/lp; /luckperms; /perm; /perms: /permissions - Main alias. Put these before any LuckPerms command.
/lp editor [type] - Opens a website interface to edit permissions data. After changes are saved, a command will be given that you need to run for the changes to take effect.
- [type] - the types to include in the editor session. can be all, users or groups.

User Commands

/lp user <user> info
/lp user <user> permission
/lp user <user> parent
/lp user <user> meta
/lp user <user> editor
/lp user <user> promote <track> [context...]
/lp user <user> demote <track> [context...]
/lp user <user> showtracks
/lp user <user> clear [context...]
/lp user <user> clone <user>

Tip
Add in-game roles via /lp user <user> parent add <job>

Group Commands

/lp group <group> info
/lp group <group> permission
/lp group <group> parent
/lp group <group> meta
/lp group <group> editor
/lp group <group> listmembers [page]
/lp group <group> setweight <weight>
/lp group <group> setdisplayname <name>
/lp group <group> showtracks
/lp group <group> clear [context...]
/lp group <group> rename <new name>
/lp group <group> clone <name of clone>

General

/tps- check the ticks-per-second (tps). The go to command to check for server lag. /whois - useful for finding a players IP if you wish to ban their IP.
/socialspy - able to see players private messages.

Crates

You can replace players' crate keys by running /crate key give <user> <crate> .

For Moderators

Here is everything a Moderator needs to know!

Managing Players

Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour.

How to check for Alternative Accounts

Players are only allowed one account on our discord, forums, and in-game. This is for a few reasons; mainly for ease of identification and punishment as well as for economic reasons in game. Players who join and show as alternative accounts should be alternative accounts tested.

Information
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.

1. Assessing

When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with /alts <username>). This scans their account to see if there are any other accounts that are playing on the same IP as them. Once you do /alts, something like this will come up. If there are two or more green usernames (which means that they are both online at the same time), check #automod on the DemocracyCraft Discord server to see if someone has already done an alternative accounts test on them. If no one has, then you need to conduct one. See below in Testing.

If you run /alts on someone and they have one green username and one or more grey usernames, that means that an account with the same IP has logged on before. Check #notes to see if they have passed the alternative accounts test before. If they haven’t, make a note in #notes. You can also check both accounts’ command histories by running /co lookup on them. If one account has transferred all of its money to the other account, it is pretty safe to say that they are alternative accounts.

Testing

If both accounts are online you can first try conducting the movement test.

You can warp yourself and the other players to the testing area using /staff-alttest <player1> <player2>
Once both players are there, inform them that their accounts have been flagged as suspicious and that you need to conduct an alternative accounts test on them.
Ask one player to run on the pink line and the other on the blue line.
You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).

If they fail the test in one of these listed ways, you’re allowed to ban one of the accounts permanently for having alt accounts;

One of the players is not moving or moving every so often
Only one player moves at a time
One is uncooperative with the test (not responding to anything)
One or both accounts log off and do not return after a while.

However, if the players pass, you can run /staff-notanalt <username 1> <username 2> and it will remove the warning and add a message in the #automod channel of the main discord.

You can also return players back to spawn using /staff-sendtospawn <player>

Additionally, you could go into /spectator and /staff-tp <player> <reason> to them to further investigate/watch their movements to verify that they aren’t alts. Consult with fellow staff members if you're unsure.

Understanding Basics

WorldGuard

/rg define <name> - Creates a region.
/rg remove <region> - Removes the specified region.
/rg redefine <name> - Re-sets an existing region to your current selection.
/rg setparent <region> <parent> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.
- Ex.: /rg setparent ExampleRegion dc-001 - Sets dc-001 as the parent of region ExampleRegion

Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change.

NOTE: Only Admin+ are able to modify region flags but it's good to be aware of what flags exist.

Flags
Flag	Type	description
build	state	Everything: Whether blocks can be mined or placed Whether doors, levers, etc. (but not inventories) can be used Whether entities and blocks can be interacted with Whether player versus player combat is permitted Whether sleeping in a bed is permitted Whether inventories can be accessed Whether vehicles (boats, minecarts) can be placed etc.
interact	state	Everything that involves ‘using’ a block or entity: Whether doors, levers, etc. (but not inventories) can be used Whether vehicles (including animals) can be mounted etc.
block-break	state	Whether blocks can be broken
block-place	state	Whether blocks can be placed
use	state	Whether doors, levers, etc. (but not inventories) can be used
damage-animals	state	Whether players can harm friendly animals (cows, sheep, etc)
chest-access	state	Whether inventories can be accessed
ride	state	Whether vehicles (including animals) can be mounted
pvp	state	Whether player versus player combat is permitted
sleep	state	Whether sleeping in a bed is permitted
respawn-anchors	state	Whether respawn anchors can be activated
tnt	state	Whether TNT detonation or block damage is permitted
vehicle-place	state	Whether vehicles (boats, minecarts) can be placed
vehicle-destroy	state	Whether vehicles can be destroyed
lighter	state	Whether flint and steel or a fire charge can be used
block-trampling	state	Whether farmland and turtle or sniffer eggs can be trampled
frosted-ice-form	state	Whether players with frost walker boots will form ice
item-frame-rotation	state	Whether items can be rotated within item frames
firework-damage	state	Whether fireworks can deal damage to entities
use-anvil	state	Whether anvils can be used
use-dripleaf	state	Whether dripleaf can be used

For more information, please check out WorldGuard’s Documentation.

WorldEdit

We use WorldEdit as a tool for many staff duties and staff duties only. Seen staff members rolling around with a wooden axe? Yep, that’s a WorldEdit wand. We use WorldEdit to make selections for regioning, vaulting, and assisting players in most instances, Abuse of this plugin is strictly not tolerated. You can find a practical course on the Staff Training warp to help with this guide.

It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience.

Getting Started

Making a selection

A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid.

How do you choose the two points? You can…

Left and right click blocks while holding a wooden axe (use //wand to get a wooden axe)
Stand somewhere and enter //pos1 and //pos2
Look at a block and enter //hpos1 and //hpos2

Commands

//wand - gives you a World Edit tool. Left click a block while holding it to make your first selection, Right click a block while holding it to make your second selection
//wandoff - takes away a World Edit tool from your inventory.
//cut - copies and clears your current selection.
//paste - pastes your previous cut selection.
//expand <amount> [direction] - makes your current selection expand by the amount specified in the specified direction.
- Amount is either specified as a number or vert (infinitely vertical).
//calc - short for ‘calculate’. Allows you to do equations in-game. Example: //calc 100*7
//sel [poly/cuboid] - select the type of region.
- Cuboid is the default selection type; basic two point selection
- Left click a block to set first selection
- Right click a block to set a second selection.
- Poly is the advanced selection type.
- Left click a block to set first selection
- Right click a block to set a second, third, fourth, etc. selection
//sel - when used like this this command will clear your current selection.
//rotate <degrees> - rotates your current clipboard (cut/copy) the specified degrees.
- Degrees have to be in multiples of 90 or it won’t work.
- i.e. 90, 180, 270, 360, -90, -180, -270, -360.
//move <amount of blocks> [direction] - moves your current selection by the amount specified in the specified direction.
/expand <number> [direction] - modifies your selection in the direction specified by the amount of blocks specific.

Directions can be…

Relative to the world
- i.e. up, down, north, east, south, west.
Relative to the player
- i.e. forward, back, left, and right.

If a direction is omitted from the command, the region will expand in the direction the player is looking.

Examples:

//expand 6 - Expand 6 blocks in the direction you’re facing
//expand 10 up - Expand 10 blocks upwards
//expand vert - Expand the region selection from bedrock to the sky. Do not use when making rentable regions (i.e. apartment rooms)

You can learn more by reading the WorldEdit 7.2 documentation

AreaShop Basics

AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them.

These are only basic commands, further down are sections dedicated to regioning.

Commands

/as add <buy/sell> <region> - makes a region either a buyable or rentable region.
- Used when making wilderness or apartment/shop regions.

IMPORTANT
You must always specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.

/as del <region> - deletes the specified region from AreaShop.
/as setprice <price> --region <region> - used to set the selling/renting price of an AreaShop region.
/as setlandlord <name> --region <region> - used to set the landlord of an Areashop region.
- Wilderness regions will always have the landlord be “DCGovernment
- Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.
/as setowner <player> --region <region> - used for when transferring ownership of a region to another player.
/as addsign <region> - used to add an Areashop sign to the sign you’re looking at.
/as delsign - used to delete the Areashop sign you’re looking at.
/as tp <region> - Teleports you to the specified Area Shop region.
- Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.
- Don’t use this for personal transportation to your regions.
/as info player <player> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.
- An alias of this command is /as me <player>.
/as info region --region <region> - provides information about a region added to AreaShop, e.g. owner, landlord etc.
/staff-getsign - gives you a sign which you can use to make AreaShop signs.
- Can also be used to label chests/buildings when vaulting.
/staff-getwool - gives you wool which you can use for selection points.

Note: --region is just a part of the syntax of some areashop commands, this isn't variable :)

How-tos

Managing disputes

As a staff member you will sometimes be required to handle delicate situations. We run on a few principles to assist staff making decisions in these scenarios.

Solve problems as early as possible at the lowest level

Unfortunately arguments and disputes are not like wine and don’t get better over time. They get worse. It’s really important for all parties that we jump on any situation early and solve the problem pacifically.

Steer clear of drama

Some players have a tendency to incite drama and you will come to learn who they are quite quickly. Be compassionate but keep a mind on players’ motives. Usually, what happens out of the server and its’ server related channels isn’t for us to deal with unless it’s quite serious and relates to our platforms. i.e. bullying enabled by our Discord server.

Evidence

Sometimes players can get a little invested or tell white lies (i.e. not telling you the whole story where they may have also been at fault) when presenting to you with a report. Make sure you collect evidence to support claims, regardless of the amount of people wanting a player banned for example.

There are two sides to every story

There will always be a personal bias in every story. Person A’s story will always be slightly different from Person B’s story. It’s important that you assess both sides to come up with an educated guestimate of the truth which is usually somewhere between the two stories.

Searching for Items

We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions.

Commands

/co l; /co lookup - used to lookup specific block data.
/co l u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>

Using CoreProtect Parameters

These can be used in almost every CoreProtect command.

`u:<user>`

Specify a user to rollback. Example: u:Technofied

`t:<time>`

Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. Example: t:2w,5d,7h,2m,10s

You can pick and choose time amounts. Example: t:5d2h You can also use decimals Example: t:2.50h (2 and a half hours)

`r:<radius>`

Specify a radius. You can use this to only rollback blocks near you. You can specify a number (i.e. r:5), a world (i.e. r:#world_the_end), a global rollback (r:#global), or a WorldEdit selection (r:#worldedit or r:#we)

For example, the following would only rollback damage within 10 blocks of where you are standing: r:10

`a:<action>`

Restrict the rollback to a certain action. Example: If you wanted to only rollback blocks placed, you would use a:+block.

Here’s a list of all the actions:

a:block - blocks placed/broken
a:+block - blocks placed
a:-block - blocks broken
a:chat - messages sent in chat
a:click - player interactions
a:command - commands used
a:container - items taken from or put in chests
a:+container - items put in chests
a:-container - items taken from chests
a:inventory - items dropped or picked up by players
a:+inventory - items picked up by players
a:-inventory - items dropped by players
a:item - items dropped, picked up, taken from, or put in chests
a:+item - items picked up or put in chests
a:-item - items dropped or taken from chests
a:kill - mobs/animals killed
a:session - player logins/logouts
a:+session - player logins
a:-session - player logouts
a:sign - messages written on signs
a:username - username changes

`b:<blocks>`

Restrict the rollback to certain block types. For example, if you wanted to only rollback stone, you would use b:1 You can specify multiple items, such as b:1,5,7

`e:<exclude>`

Exclude certain block types from the rollback.

Example: If you don’t want TNT to come back during a rollback, you would type e:46

`#<hashtag>`

Add a hashtag to the end of your command to perform additional actions.

Example: To perform a rollback preview, you would use #preview

Here is a list of all available hashtags

#preview - preview a rollback/restore
#verbose - display additional information during a rollback/restore
#silent - display minimal information during a rollback/restore

Merging regions

Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.

IMPORTANT
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.

Merging

To merge a region is quite simple - all that is required is to redefine a region over the plot divider with /rg redefine <plot>. See below for an example.

What can be merged?

You can merge any commercial (inclusive of skyscraper plots) and industrial plots. Residential, CBD, and any other special plots (e.g farms, yacht, ranch) are NOT to be merged.

Urban Regioning

Urban regions are city/town plots and their child regions (apartments/shops). This guide will show you how to create child regions. For this, you will be using World Edit (selecting the region), World Guard (making the region), and Areashop (renting the region).Template:Danger

Step by Step Guide

1.1 Creating the WorldGuard region and fining the player.
- After selecting the points for the region you can define the region to create it.
- The owner of the building may choose the name of the region.
- Command: /rg define <regionName>.
  - i.e. /rg define EndStore1.
1.2 Make sure to fine the player for the creation of each region.
- Each individual region costs $25 to create excluding shulker regions, those are free. Don't forget the fee!
- Command: /fine <user> <amount> <reason>.
  - Select “Staff” as the account to send the fine to.
  - i.e. /fine xEndeavour 25 Staff rental creation.
2.0 Setting the region parent.
- Next we need to tell WorldGuard who the child region belongs to. In order to do this, we will parent the child region to the plot it’s on.
- The parent is the plot the room will inherit permissions from.
- Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.
- Command: /rg parent <regionName> <PlotRegion>.
  - i.e. /rg parent EndStore1 c001.
3.0 Adding the region to AreaShop
- After you have created the WorldGuard region and parented it, it’s now time to make it rentable. All you need to do is add the region to Areashop.
- Command: /as add rent <regionName>.
3.1 Set the landlord
- Command: /as setlandlord <landlord> --region <regionName>, this usually is the player who is creating the region, rental money will go to the landlord.
3.2 Set the price
- Command: /as setprice <price> --region <regionName>
3.3 Set the duration
- Command: /as setduration <duration> --region <region>
- This must be kept within a timeframe of 14d - 30d to maintain consistency. The only exception to this rule is the creation of shulker regions which typically hold a rental duration of 5 minutes.
4.0 Adding an AreaShop sign
- If the player is unable to provide a sign for you to place and create, you can obtain one by using /staff-getsign.
- After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.
- The player will usually show you where they want the signs.
- After the sign is placed look at it and use the command: /as addsign <regionName>, this will make the sign interactive and add the region’s information to it.
5.0 Quality Checks
- Check the priority of the region is 30 or above via /rg info <regionName> - if not click on the priority and type in 30. Note: Adding a region to areashop can mess with the priority, set this after adding it.
- While in the /rg info section of chat, select the coordinates next to "Bounds". This will show you the borders of the region to ensure it's regioned correctly, go into /spec and check everything is fine.
- Make sure to get rid of the wool that you placed, don’t leave anything behind.

Using the sign-based method

If you prefer doing region creation through signs, try this!

Wild Regioning:

Wilderness regions are private wild plots that any player can obtain. It costs $10/block to claim land in the wilderness. Wild regions used to be made manually by staff, now the server utilises a plugin which enables players themselves to create their own claims without the need for staff. Make sure to review Wilderness Claiming, essential information is documented there!

Some players still have an wild claim of the old system from where they were made using a WorldGuard region and added to AreaShop, you may be needed to transfer this claim to the new system when a player opens a ticket.

Instructions:

Do /rg i on the player's old claim or /rg info <claim name (will be the playername)>
Click on Bounds to select the player's old claim
Get some wool with /staff-getwool and mark the corners of the region, this will assist the player in claiming their region again later.
Run //count #yaxis to get the number of surface blocks
Run /staff-grant-claim-blocks <username> <amount of blocks>, replacing <amount of blocks> with the number from //count This will send a message in #staff-team if you need to refer back to it. Recall it will be 10 blocks extra as the first 10 claim blocks are free! If you make a mistake you can remove claim blocks by using a negative value for the amount of blocks!
Do /as setowner DCGovernment - this is very important :)
Run /rg-d <username> to kill the old region then /as del --region <username>. The player won’t be refunded anything as their claim is being transferred, not refunded - as you set DCgovernment as the owner the money from deletion will go to that account. NOTE: If the player doesn't wish to have their claim transferred and instead wants it removed you can delete it from WorldGuard and AreaShop with the commands above, make sure the owner is set to the player so they get refunded in that case!
The player now has the correct number of blocks to re-claim their new region, direct them to Wilderness Claiming for the how-to and assist them if needed.

Useful information:

Players are still only allowed ONE wild claim. Use /listclaims <username> to see information about a player, the command will show you something similar to this:

It may look like a bit of a mess but (-360) shows the claim block size (it’s a positive value mind you, not negative :<) while “X blocks left to spend” shows how many claim blocks a player currently has.

Other relevant commands:

/ignoreclaims Use this to bypass claim protections of the claim you're standing on.
/deleteclaim (Use this to delete the claim your standing on even if you're not the owner, region claim blocks will be returned to the owner of the claim. - be careful in using this command!)

If you're unsure with anything always consult with fellow staff members :)

For Everyone

Note taking

In order to keep comprehensive notes on our players that are easily accessible, we use the discord channel #notes. Search for the player’s full username, before creating a thread. (You can use in:#notes playername.) In these threads we record evidence and general notes about players behaviours and punishments.

How and when to action warrants

Warrants are a legal writ that allow for only enforcement agencies to break the law under certain circumstances. I.e. trespass, take items, gather evidence. This is a function that requires Staff Support.

Warning
If you are involved in a case/investigation or have a vested interested in the outcome of a case/investigation, please recuse yourself from getting the information for the warrant.

Eligibility

A warrant is only enforceable if it is has been approved by a Judge or Justice. Agencies seeking to exercise warrants will need to provide proof that the warrant was approved appropriately. Warrants generally need to be served within a 48 hour window before they expire. - Noting that Staff tickets take more than 48 hours to process these requests, as long as the warrant was posted in a staff ticket prior to the warrant expiring, we can still provide the information post-deadline.

We can search through logs, but excessive requests (i.e. searching multiple days will be denied). - No more than 48 hours and some topics/key words that we can search for within that timeframe is generally seen as acceptable. - Beyond this it is up to the staff member taking the ticket.

Protecting Staff Information

Staff do not have to comply with legal orders - there are no punishments for not providing the information. If something seems off about the request, please raise it with your colleagues or senior staff. It is best to take a more cautious approach rather than accidentally giving away information that shouldn’t be given away. Warrants need to dictate what information they are seeking. We will usually search for this information and give that information to them only.

Who can request what

Animal and Villager Death Logs do not require warrants provided they are being requested by a member of the Department of Justice that is a Sergeant or above. Everything else requires a warrant!

'''''

Staff
Leadership Guides	Server Panel Access
Administration Guides	Restoring Files Forums Admin Control Panel (ACP) Using LuckPerms Verbose Screening Players For VPNs Imagemap Naming Guide Getting CPI Data
Staff-wide Guides	Staff Guide Everything Senior Vice Presidents (SVPs) Quick Reference Staff Guide Staff Discord Tickets Guide Issuing Punishments Vaulting WorldEdit
Policy	Staff Intent Staff Vetos Staff Career Progression, Expectations, and Disciplinary Staff Conflict Of Interest Policy Client Modifications Replacement Policy
Resources	Bug Tracker Trial Moderator Checklist
Category