DemocracyCraft Wiki - User contributions [en-gb]

Networks

2026-03-21T01:58:01Z

Technofied: Fix (properly) ingredients

DemocracyCraft has one of the most expansive in-game player-to-player economies on Minecraft, this naturally means a lot of shops to buy from and sell to. However, with several thousand entities in-game, this becomes laggy for the players more than it does for the server. For that reason, we’ve implemented a networking system to sort and filter your chests '''without''' the use of hoppers!

== Create your components ==

In any network, you will need '''input, sorting and miscellaneous''' containers, and a '''network wand''' to configure them.


=== Network Wand ===
[[File:Network wand.png|thumb|Network wand recipe]]This wand will be used to configure the filters for your sorting containers, and view more information about your network components.

This is the tool for networks. It's '''important''' you make this tool.

* '''Right Click''' on any network container with the wand in your main hand to view details.
* '''Left Click''' to toggle the wand mode.

==== Wand modes ====

===== Filter mode =====
This wil be your main mode to set whitelist filters on the containers. This means that every item on the filter for that container could go to that container.
It is possible to add multiple filters to a containers and it is possible to add the same filter to multiple containers.
{{Note
| inline = 1
| type = warn
| text = This filter does not store metadata. It won't be filtered on metadata.
}}
'''Sneak + Right Click''' on any sorting container to add a filter.
* You must have the item you are filtering in your off-hand, and the wand in your main hand.
* The sorting container will “filter” the item you specified in your off-hand, by grabbing them from input containers that are part of the same network.
'''Sneak + Left Click''' on any sorting container to remove a filter.
* You must have the item you are removing the filtering in your off-hand, and the wand in your main hand.
Usage example: normal block filtering like cobblestone, stone, grass, wood

Example on how filter is shown on a container: [Cobblestone, ]

===== Priority mode =====
This mode is for setting priority of which containers are going to be filled first.
* '''Shift + Right Click''' with the wand to increase the priority of a container.
* '''Shift + Left Click''' with the wand to decrease the priority of a container.
* priority is from high to low, meaning that it prioritizes a container with priority 10 over priority 9.

===== Strict filter mode =====
This wil be a mode you rarely use. This mode is to filter on metadata, this means that every item with the same metadata on the '''strict filter''' for that container could go to that container.

'''Sneak + Left Click''' on any sorting container to add a filter.
* You must have the item you are filtering in your off-hand, and the wand in your main hand.
* The sorting container will “filter” the item you specified in your off-hand, by grabbing them from input containers that are part of the same network.
Usage example: potions, tools, armor, enchantment books, etc.

Example on how filter is shown on a container: [[Bow], ]



=== Containers ===

See below for a description per container type.

{{Tip| Containers are not just barrels| You can ''also'' use Hoppers, Dispensers, and Droppers, just swap out the '''Barrel''' in the recipes below.
Shulker boxes and furnaces can not be used as a container.}}

[[File:Updated Input Container .png|thumb|Input Container Recipe]]

==== Input Containers ====

These containers are the start of your network and require the least configuration. You put any items in here for them to be sorted into your sorting containers. The items only get sorted when the chest is closed. You can still remove items as long as you didn't closed the input container. Items that it is unable to sort are going to stay in the chest or end up in a mics chest.

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the input item frame crafted to turn a regular container '''into an input container.'''[[File:Updated Sorting Container.png|thumb|Sorting Container Recipe]]

==== Sorting Containers ====

These containers look at your input containers and take items from them according to their set filters. You can use the '''Network Wand''' to set these filters.

On their own, '''without filters''', sorting container will remain empty. You need to specify your filters!

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the sorting item frame crafted to turn a regular container '''into a sorting container.'''
[[File:Updated miscellaneous container.png|thumb|Miscellaneous Container Recipe]]

==== Miscellaneous Containers ====

These containers look for items that haven’t been assigned to sorting chests, and takes them. This is useful for when you want to put a bunch of random items in your input containers and filter out rubbish.

{{Note
| type = reminder
| text = If a filter container is '''full''' and the network doesn't have any '''other sorting''' containers to put the items in. Those items end up in a mics container.
}}

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the misc. item frame crafted to turn a regular container '''into a miscellaneous container.'''

=== Upgrades ===

You are able to upgrade the range of your containers using <code>Upgrade Antennas</code>! Craft them using the below recipes, then '''right click with then in your hand''' to the container you want upgraded, to extend their range.

{{Tip|You need to have '''atleast one upgrade''' on the input container to work.|You cannot apply the same Tier upgrade more than once. This is a good way to check what Tier a current container is on (until we make an easier method).|}}
[[File:Tier 1 antenna.png|thumb|Tier 1 Antenna Recipe]]
==== Tier 1 (50 blocks) ====

Items for crafting:

* 4x Redstone Dust
* 1x Lightning Rod

Requires no prior tiers.

'''Usage:''' Input container in your house where the other containers are located.[[File:Tier 2 Antenna Recipe.png|thumb|Tier 2 Antenna Recipe]]
==== Tier 2 (100 blocks) ====

Items for crafting:

* 4x Redstone Block
* 3x Lightning Rod
* 2x Gold Ingot

Requires Tier 1.

'''Usage:''' Input container in your house where the other containers are located.
[[File:Tier 3 Antenna Recipe.png|thumb|Tier 3 Antenna Recipe]]
==== Tier 3 (500 blocks) ====

Items for crafting:

* 3x Copper Block
* 2x Ender Pearl
* 2x Gold Block
* 2x Redstone Block

Requires Tier 2.

'''Usage:''' Input container in another part of the city[[File:Tier 4 Antenna Recipe.png|thumb|Tier 4 Antenna Recipe]]
==== Tier 4 (Multi-dimensional) ====
Items for crafting:

* 4x Skulk
* 2x Ender Pearl
* 2x Copper Block
* 1x Gold Block

Requires Tier 3.

'''Usage:''' when you need to transfer items between worlds or cities.

Example:
*Between Aventura and Oakridge
*Between Wilderness and Reveille
== How do I create my first network? ==

Run the command <code>/net create <network_name></code>, please use a descriptive name for your reference!

You can then place down the containers you crafted, and use your Network Wand on them.

{{Tip| Need to edit a network?|Do <code>/net select <network_name></code>, then place your containers and use your Network Wand to your heart’s desire!|}}

=== How do I setup my first network? ===
First follow '''"How do i create my first network?"'''

Below are the following steps

* Run the command <code>/net select <network_name></code>.
* Craft the wand. '''You need it.'''
* Craft the containers to use.
* Place the containers on chest, hoppers or barrels. Shulker boxes and furnaces can't be used.
** Use input containers for hoppers or anything that will "take" items
** Use sorting containers for anything that receives items from the inputs (e.g. hoppers) according to specific requirements (e.g. only cactus)
** Use miscellaneous containers to capture anything that sorting containers aren't set to, that way you aren't clogging up your input containers
* Check if the wand is in '''filter mode'''. The wands name should be '''"Network Wand"'''.
** If it is in a different mode: '''Left Click''' until you get the message '''"[Networks} Wand mode set to [Filter]"'''.
* Approach an '''input''' container
* Hold the item you want to '''filter''' (end up in that container) in your '''offhand'''.
* Hold the '''wand''' in your '''main hand''' and '''Sneak + Right click''' to add a filter. to remove a filter do the same as before but then '''Sneak + Left click'''

== All Available Commands ==
* <code>/net</code> - Gives the help menu and network version.
* <code>/net manual</code> - Gives the manual in book form.
* <code>/net create <name></code> - Create a storage network.
* <code>/net delete <name></code> - Delete a storage network.
* <code>/net rename <name> <newName></code> - Rename a network.
* <code>/net select <name></code> - Select a storage network.
* <code>/net list</code> - List all networks you have permissions for.
* <code>/net listall</code> - List all networks that '''everyone''' has.
* <code>/net list <player></code> - List all networks that player has permissions for.
* <code>/net info</code> - Show information about the selected network.
* <code>/net items</code> - List all your network’s items.
* <code>/net view</code> - See all your items in a visual UI.
* <code>/net user add <player></code> - Give a player access to your network.
* <code>/net user remove <player></code> - Revoke a player access to your network.
* <code>/net merge (net1) (net2)</code> - Merge net2 into net1.

=== Sources: ===
Networks Docs: https://networks.kwantux.de/
[[category:Features]]

File:Tier 2 antenna.png

2026-03-21T01:57:41Z

Technofied: Technofied uploaded a new version of File:Tier 2 antenna.png

File:Tier 3 antenna.png

2026-03-21T01:57:10Z

Technofied: Technofied uploaded a new version of File:Tier 3 antenna.png

File:Tier 4 antenna.png

2026-03-21T01:56:28Z

Technofied: Technofied uploaded a new version of File:Tier 4 antenna.png

File:Tier 4 Antenna Recipe.png

2026-03-21T01:48:07Z

Technofied: Technofied reverted File:Tier 4 Antenna Recipe.png to an old version

A Tier 4 Antenna crafting recipe for Networks

File:Tier 3 Antenna Recipe.png

2026-03-21T01:47:36Z

Technofied: Technofied reverted File:Tier 3 Antenna Recipe.png to an old version

A Tier 3 Antenna crafting recipe for Networks

File:Tier 2 Antenna Recipe.png

2026-03-21T01:47:16Z

Technofied: Technofied reverted File:Tier 2 Antenna Recipe.png to an old version

A Tier 2 Antenna crafting recipe for Networks

File:Tier 1 antenna.png

2026-03-21T01:46:27Z

Technofied: Technofied reverted File:Tier 1 antenna.png to an old version

Crate Packer

2026-02-25T07:30:09Z

Technofied: Initial Crate Packer guide

Sometimes you will want to condense your stock so you can better transport or store them.

In DemocracyCraft, we have '''three''' types of items you can craft to condense your stock.

* Crates
* Barrels
* Bags

All of these can be crafted via a '''Crate Packer.'''

== Crafting a Crate Packer ==
[[File:Crate Packer Recipe.png|thumb|You can view this recipe in '''/recipes''' under '''General Recipes.''']]
You need the following ingredients to craft a Crate Packer in a Crafting Table.

* '''4x''' Spruce Planks
* '''5x''' Spruce Slabs

Place the Spruce Planks on each corner of the crafting grid of a Crafting Table, then place your Spruce Slabs in all other slots, as pictured.

== Recipes ==
'''RIGHT CLICK''' your Crate Packer with '''9 (nine)''' of any of the listed foods below, to craft their crate, barrel, or bag equivalent.

* To deconstruct a crate, barrel, or bag, simply place it in the middle of the Crafting Table UI.
** e.g. Placing '''1 (one)''' Apple Crate in the middle of a Crafting Table UI will turn it back into '''9 (nine) apples.'''

{| class="wikitable"
|+Food
!Name
|-
|Apple

Banana

Beef

Beetroot

Carrot

Cherry

Chicken

Chorus Fruit

Cocoa Beans

Coconut

Cod

Corn

Cucumber

Egg

Fermented Spider Eye

Glow Berries

Grape

Lemon

Lettuce

Mutton

Olives

Onions

Orange

Pepper

Plum

Porkchop

Potato

Pufferfish

Rabbit

Raspberry

Rice

Rotten Flesh

Salmon

Spider Eye

Strawberry

Sweet Berries

Tea Leaves

Tomato

Tropical Fish

Vanilla
|}

File:Crate Packer Recipe.png

2026-02-25T07:17:33Z

Technofied:

Minecraft Crafting Table UI depicting the recipe for a Crate Packer

Miner

2026-02-18T08:47:27Z

Technofied: Update to include per resource pay, fix up block drops, fix gps dealership command

{{Jobs}}

=== What miners do ===
As a miner, your main role is to mine ores, such as Coal and Netherite, and sell them. You can [[business|create a business]] or supply ores to other players and shops. There is no mining town, instead, the Wilderness and Everwild have natural generation which is already suited for miners. You can access the Wilderness and Everwild with <code>/airport</code>

=== Special Perks ===
Miners gain significant advantages over other players when it comes to collecting ore. Items collected can be refined further with custom recipes unique to miners, accessible through using <code>/recipes</code>.

[[File:Cobble to gravel.png|thumb|right|Cobblestone being crafted into gravel.]]

==== Block Drops ====
Miners get bonus resources when mining certain blocks. These are typically blocks other players would avoid in order to conserve inventory space or durability, but they hold more value in a miner's eyes.

Every '''fifteen minutes''' you get paid these bonus resources.

The following have a '''10% chance''' of being obtained '''per block broken.'''

{| class="wikitable"
|-
! Block !! Special Product
!Chance
|-
|Diorite
|Quartz
|20%
|-
| Dirt || Clay Ball
|10%
|-
| Stone || Gunpowder
|10%
|-
| Diorite || Quartz
|10%
|-
| Deepslate || Gunpowder
|10%
|-
| Amethyst Block || Budding Amethyst
|10%
|-
| Netherrack || Glowstone Dust
|10%
|-
| End Stone || Phantom Membrane
|10%
|}

==== Bonus Payments ====
You also get paid per block for certain resources, every '''15 minutes.'''
{| class="wikitable"
|+Payments by Block
!Block
!Money Range
!XP Range
!Chance
|-
|Nether Gold Ore
|10.0–15.0
|1.0–3.0
|10.0
|-
|Coal Ore
|3.0–5.0
|0.50–0.01
|10.0
|-
|Deepslate Redstone Ore
|10.0–15.0
|1.0–3.0
|10.0
|-
|Deepslate Iron Ore
|3.0–5.0
|0.50–0.01
|10.0
|-
|Deepslate Diamond Ore
|20.0–30.0
|1.0–3.0
|10.0
|-
|Diamond Ore
|20.0–30.0
|1.0–3.0
|10.0
|-
|Redstone Ore
|10.0–15.0
|0.50–0.01
|10.0
|-
|Deepslate Lapis Ore
|10.0–15.0
|0.50–0.01
|10.0
|-
|Deepslate Coal Ore
|3.0–5.0
|1.0–3.0
|10.0
|-
|Lapis Ore
|10.0–15.0
|0.50–0.01
|10.0
|-
|Ancient Debris
|30.0–40.0
|1.0–3.0
|10.0
|-
|Deepslate Gold Ore
|10.0–15.0
|1.0–3.0
|10.0
|-
|Copper Ore
|3.0–5.0
|0.50–0.01
|10.0
|-
|Deepslate Emerald Ore
|20.0–30.0
|1.0–3.0
|10.0
|-
|Gold Ore
|10.0–15.0
|0.50–0.01
|10.0
|-
|Nether Quartz Ore
|10.0–15.0
|0.50–0.01
|10.0
|-
|Iron Ore
|3.0–5.0
|0.50–0.01
|10.0
|-
|Emerald Ore
|20.0–30.0
|1.0–3.0
|10.0
|-
|Mossy Stone Bricks
|3.0–5.0
|1.0–0.01
|1.0
|-
|Mossy Cobblestone
|1.0–2.0
|1.0–0.01
|1.0
|-
|Gray Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Green Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Purple Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Warped Nylium
|3.0–5.0
|1.0–0.01
|1.0
|-
|Stone Bricks
|3.0–5.0
|1.0–0.01
|1.0
|-
|Cracked Stone Bricks
|3.0–5.0
|1.0–0.01
|1.0
|-
|Light Gray Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Granite
|1.0–2.0
|1.0–0.01
|1.0
|-
|Cobblestone
|1.0–2.0
|1.0–0.01
|1.0
|-
|Tuff
|1.0–2.0
|1.0–0.01
|1.0
|-
|Diorite
|1.0–2.0
|1.0–0.01
|1.0
|-
|Stone
|1.0–2.0
|1.0–0.01
|1.0
|-
|Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Light Blue Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Crimson Nylium
|3.0–5.0
|1.0–0.01
|1.0
|-
|Red Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Blue Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Cyan Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Pink Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|White Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Orange Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Black Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Andesite
|1.0–2.0
|1.0–0.01
|1.0
|-
|Deepslate
|1.0–2.0
|1.0–0.01
|1.0
|-
|Magenta Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Yellow Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Chiseled Stone Bricks
|3.0–5.0
|1.0–0.01
|1.0
|-
|Brown Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|-
|Lime Terracotta
|3.0–5.0
|1.0–0.01
|1.0
|}

=== Mining made easier ===
You can speed up mining by purchasing a [[Drill|drilling vehicle]] from the [[Reveille Dealership]] (use <code>//gps start dealership</code>). This isn't the only place to acquire [[Drill|drills]], however, as you can also get them from the server's crates or by buying them from other players.

=== Passed the exam? What now? ===
In only a little bit of time, you'll be swimming in resources. You'll want to sell those at either your own store or to someone with an existing shop. You may wish to start a company to sell under, but you must gain an [[Entrepreneur's license|entrepreneur's license]] first.

* Consider buying a plot and setting up a store to sell your products. Find available plots for sale/lease in the #realty-adverts section on our Discord.
* You can also sell to businesses using <code>/find {item name}</code>.

=== Additional resources ===
* To find more ways to make money, read the [https://wiki.democracycraft.net/government/money/ Making Money Guide].
* You can explore job opportunities with DC #employment channel: [https://discord.gg/democracy DC Employment]

[[category:trades]]

Networks

2026-02-15T10:53:01Z

Technofied: Update guide to be reflective of current Networks

DemocracyCraft has one of the most expansive in-game player-to-player economies on Minecraft, this naturally means a lot of shops to buy from and sell to. However, with several thousand entities in-game, this becomes laggy for the players more than it does for the server. For that reason, we’ve implemented a networking system to sort and filter your chests '''without''' the use of hoppers!

== Create your components ==

In any network, you will need '''input, sorting and miscellaneous''' containers, and a '''network wand''' to configure them.


=== Network Wand ===
[[File:Network wand.png|thumb|Network wand recipe]]This wand will be used to configure the filters for your sorting containers, and view more information about your network components.

This is the tool for networks. It's '''important''' you make this tool.

* '''Right Click''' on any network container with the wand in your main hand to view details.
* '''Left Click''' to toggle the wand mode.

==== Wand modes ====

===== Filter mode =====
This wil be your main mode to set whitelist filters on the containers. This means that every item on the filter for that container could go to that container.
It is possible to add multiple filters to a containers and it is possible to add the same filter to multiple containers.
{{Note
| inline = 1
| type = warn
| text = This filter does not store metadata. It won't be filtered on metadata.
}}
'''Sneak + Right Click''' on any sorting container to add a filter.
* You must have the item you are filtering in your off-hand, and the wand in your main hand.
* The sorting container will “filter” the item you specified in your off-hand, by grabbing them from input containers that are part of the same network.
'''Sneak + Left Click''' on any sorting container to remove a filter.
* You must have the item you are removing the filtering in your off-hand, and the wand in your main hand.
Usage example: normal block filtering like cobblestone, stone, grass, wood

Example on how filter is shown on a container: [Cobblestone, ]

===== Priority mode =====
This mode is for setting priority of which containers are going to be filled first.
* '''Shift + Right Click''' with the wand to increase the priority of a container.
* '''Shift + Left Click''' with the wand to decrease the priority of a container.
* priority is from high to low, meaning that it prioritizes a container with priority 10 over priority 9.

===== Strict filter mode =====
This wil be a mode you rarely use. This mode is to filter on metadata, this means that every item with the same metadata on the '''strict filter''' for that container could go to that container.

'''Sneak + Left Click''' on any sorting container to add a filter.
* You must have the item you are filtering in your off-hand, and the wand in your main hand.
* The sorting container will “filter” the item you specified in your off-hand, by grabbing them from input containers that are part of the same network.
Usage example: potions, tools, armor, enchantment books, etc.

Example on how filter is shown on a container: [[Bow], ]



=== Containers ===

See below for a description per container type.

{{Tip| Containers are not just barrels| You can ''also'' use Hoppers, Dispensers, and Droppers, just swap out the '''Barrel''' in the recipes below.
Shulker boxes and furnaces can not be used as a container.}}

[[File:Updated Input Container .png|thumb|Input Container Recipe]]

==== Input Containers ====

These containers are the start of your network and require the least configuration. You put any items in here for them to be sorted into your sorting containers. The items only get sorted when the chest is closed. You can still remove items as long as you didn't closed the input container. Items that it is unable to sort are going to stay in the chest or end up in a mics chest.

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the input item frame crafted to turn a regular container '''into an input container.'''[[File:Updated Sorting Container.png|thumb|Sorting Container Recipe]]

==== Sorting Containers ====

These containers look at your input containers and take items from them according to their set filters. You can use the '''Network Wand''' to set these filters.

On their own, '''without filters''', sorting container will remain empty. You need to specify your filters!

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the sorting item frame crafted to turn a regular container '''into a sorting container.'''
[[File:Updated miscellaneous container.png|thumb|Miscellaneous Container Recipe]]

==== Miscellaneous Containers ====

These containers look for items that haven’t been assigned to sorting chests, and takes them. This is useful for when you want to put a bunch of random items in your input containers and filter out rubbish.

{{Note
| type = reminder
| text = If a filter container is '''full''' and the network doesn't have any '''other sorting''' containers to put the items in. Those items end up in a mics container.
}}

'''Note:''' You need to '''right-click''' on a '''container''' (barrel, chest, etc) with the misc. item frame crafted to turn a regular container '''into a miscellaneous container.'''

=== Upgrades ===

You are able to upgrade the range of your containers using <code>Upgrade Antennas</code>! Craft them using the below recipes, then '''right click with then in your hand''' to the container you want upgraded, to extend their range.

{{Tip|You need to have '''atleast one upgrade''' on the input container to work.|You cannot apply the same Tier upgrade more than once. This is a good way to check what Tier a current container is on (until we make an easier method).|}}
[[File:Tier 1 antenna.png|thumb|Tier 1 Antenna Recipe]]
==== Tier 1 (50 blocks) ====

Items for crafting:

* 4x Redstone Dust
* 1x Lightning Rod

Requires no prior tiers.

'''Usage:''' Input container in your house where the other containers are located.[[File:Tier 2 Antenna Recipe.png|thumb|Tier 2 Antenna Recipe]]
==== Tier 2 (100 blocks) ====

Items for crafting:

* 4x Redstone Block
* 2x Gold Ingot
* 3x Lightning Rod

Requires Tier 1.

'''Usage:''' Input container in your house where the other containers are located.
[[File:Tier 3 Antenna Recipe.png|thumb|Tier 3 Antenna Recipe]]
==== Tier 3 (500 blocks) ====

Items for crafting: 2x Redstone Dust, 2x Gold Block, 2x Ender Peurl, 3x Copper block.

Requires Tier 2.

'''Usage:''' Input container in another part of the city[[File:Tier 4 Antenna Recipe.png|thumb|Tier 4 Antenna Recipe]]
==== Tier 4 (Multi-dimensional) ====
Items for crafting:

* 4x Sculk
* 1x Gold Block
* 2x Ender Pearl
* 2x Copper Block

Requires Tier 3.

'''Usage:''' when you need to transfer items between worlds or cities.

Example:
*Between Aventura and Oakridge
*Between Wilderness and Reveille
== How do I create my first network? ==

Run the command <code>/net create <network_name></code>, please use a descriptive name for your reference!

You can then place down the containers you crafted, and use your Network Wand on them.

{{Tip| Need to edit a network?|Do <code>/net select <network_name></code>, then place your containers and use your Network Wand to your heart’s desire!|}}

=== How do I setup my first network? ===
First follow '''"How do i create my first network?"'''

Below are the following steps

* Run the command <code>/net select <network_name></code>.
* Craft the wand. '''You need it.'''
* Craft the containers to use.
* Place the containers on chest, hoppers or barrels. Shulker boxes and furnaces can't be used.
** Use input containers for hoppers or anything that will "take" items
** Use sorting containers for anything that receives items from the inputs (e.g. hoppers) according to specific requirements (e.g. only cactus)
** Use miscellaneous containers to capture anything that sorting containers aren't set to, that way you aren't clogging up your input containers
* Check if the wand is in '''filter mode'''. The wands name should be '''"Network Wand"'''.
** If it is in a different mode: '''Left Click''' until you get the message '''"[Networks} Wand mode set to [Filter]"'''.
* Approach an '''input''' container
* Hold the item you want to '''filter''' (end up in that container) in your '''offhand'''.
* Hold the '''wand''' in your '''main hand''' and '''Sneak + Right click''' to add a filter. to remove a filter do the same as before but then '''Sneak + Left click'''

== All Available Commands ==
* <code>/net</code> - Gives the help menu and network version.
* <code>/net manual</code> - Gives the manual in book form.
* <code>/net create <name></code> - Create a storage network.
* <code>/net delete <name></code> - Delete a storage network.
* <code>/net rename <name> <newName></code> - Rename a network.
* <code>/net select <name></code> - Select a storage network.
* <code>/net list</code> - List all networks you have permissions for.
* <code>/net listall</code> - List all networks that '''everyone''' has.
* <code>/net list <player></code> - List all networks that player has permissions for.
* <code>/net info</code> - Show information about the selected network.
* <code>/net items</code> - List all your network’s items.
* <code>/net view</code> - See all your items in a visual UI.
* <code>/net user add <player></code> - Give a player access to your network.
* <code>/net user remove <player></code> - Revoke a player access to your network.
* <code>/net merge (net1) (net2)</code> - Merge net2 into net1.

=== Sources: ===
Networks Docs: https://networks.kwantux.de/
[[category:Features]]

File:Tier 4 Antenna Recipe.png

2026-02-15T10:50:38Z

Technofied: Technofied uploaded a new version of File:Tier 4 Antenna Recipe.png

A Tier 4 Antenna crafting recipe for Networks

File:Tier 3 Antenna Recipe.png

2026-02-15T10:50:30Z

Technofied: Technofied uploaded a new version of File:Tier 3 Antenna Recipe.png

A Tier 3 Antenna crafting recipe for Networks

File:Tier 2 Antenna Recipe.png

2026-02-15T10:50:21Z

Technofied: Technofied uploaded a new version of File:Tier 2 Antenna Recipe.png

A Tier 2 Antenna crafting recipe for Networks

File:Tier 1 antenna.png

2026-02-15T10:49:43Z

Technofied: Technofied uploaded a new version of File:Tier 1 antenna.png

Imagemap Naming Guide

2026-01-20T05:06:36Z

Technofied: Redo naming convention with transition to YAMIPA

The imagemap database is a mess and if you don't know the name of the file, it can take you forever to find images. Moving forward Administrators and the Commerce Department are asked to follow the guide below when downloading new images.

==== '''Government Images''' ====

* Presidential_Portrait_XXXXXX.png
* Department_of_XXXXXX_Seal.png
* Town_of_XXXXXX_Seal.png

==== '''Museum Images''' ====

* Museum_XXXXXX.png
* Party_XXXXXX_Logo.png
* Party_XXXXXX_Banner.png
* Campaign_XXXXXX_Banner.png

==== Player Billboards ====

* SERNAME_Billboard_NUMBER.png

In conclusion, just make sure that you'd be able to tell what the picture was of just by looking at the name of your imagemap file. Thank you!

{{Staff}}
[[category:staff]]

Staff Responsibilities and Progression

2026-01-20T04:44:07Z

Technofied: Add to Staff Category

[[File:TM.png|center|thumb|1055x1055px]]

== Trial Moderator ==
New Staff member undergoing training and evaluation. Trial Moderators assist players, handle tickets, and learn discipline standards while under a mentor's supervision.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Handle in-game and Discord support tickets
|Complete the Trial Moderator Checklist
|No prior experience necessary
|-
|Enforce server rules at a basic level
|Complete the Learning Confirmation
|
|-
|Use moderation tools (punishments, log searches)
|Be recommended by their Mentor for consideration
|
|-
|Assist with land, region, and vault issues
|Be recognised by administrative staff as suitable for independent duties
|
|-
|Learn staff procedures, policies, and expectations
|Possess a willingness to learn, follow guidance, and accept feedback
|
|-
|Act professionally and represent staff values
|
|
|}
[[File:M.png|center|thumb|1056x1056px]]

== Moderator ==
Qualified Staff Member responsible for enforcing server rules, resolving player issues, and completing the day-to-day work to keep the server running.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Independently resolve tickets and player issues
|Show consistent high-quality moderation
|Successful completion of Moderator Trial
|-
|Enforce rules in-game and on Discord
|Demonstrate good judgement and discretion
|Proven understanding of rules and moderation tools
|-
|Conduct log reviews and evidence verification
|Be active and engaged with the community
|Demonstrated professionalism and reliability
|-
|Apply punishments appropriately and consistently
|Be recognised by senior staff as suitable for higher responsibility
|
|-
|Act professionally and represent staff values
|
|
|}

[[File:A.png|center|thumb|1055x1055px]]

== Administrator ==
A senior-moderation staff member with leadership and mentoring responsibilities. A position of trust, with additional responsibility over complex issues and other staff members.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Mentor and support Moderators and Trial Moderators
|Demonstrate long-term commitment and reliability
|Extended experience as a Moderator
|-
|Assist with complex tickets and disputes
|Show leadership in staff management and policy application
|Strong knowledge of server systems and policies
|-
|Ensure consistency in rule enforcement
|Show initiative in staffing, as well as suggesting and implementing new ideas
|Proven trustworthiness and leadership capability
|-
|Participate in network decision-making
|Be recognised by server leadership as suitable for higher responsibility
|
|-
|Uphold and reinforce staff standards
|
|
|}

[[File:SA.png|center|thumb|1054x1054px]]

== Senior Administrator ==
High-level staff members entrusted with responsibility over policy, high-risk and sensitive issues, and the strategic direction of the server.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Lead and coordinate Administrators and Moderators
|Advancement beyond this role is determined by Server Leadership
|Significant experience as an Administrator
|-
|Handle high-risk or sensitive cases
|
|Deep understanding of server operations and culture
|-
|Assist in policy development and enforcement standards
|
|Strong leadership, judgement, and communication skills
|-
|Participate in promotion and disciplinary decisions
|
|
|-
|Act as a key point of contact for server leadership
|
|
|}

[[File:MX.png|center|thumb|1055x1055px]]

== Manager ==
A member of server leadership, they are an ambassador and leader of a respective area of the network (StateCraft, DemocracyCraft, Network Systems).
{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Final authority on policies and major decisions
|Extensive experience and trust within the server
|Significant experience as a Senior Administrator
|-
|Oversee staff structure and long-term vision
|Demonstrated leadership at the highest level
|A holistic understanding/appreciation of staff and server operations
|-
|Resolve escalated disputes
|Strong leadership, judgement, and communication skills
|Exceptionally strong leadership, judgement, and communication skills
|-
|Maintain server direction and integrity
|
|
|}

[[File:Seal Staff 3 sml.png|center|thumb|119x119px]]

== Duties and Expectations ==
Our Staff have several day-to-day roles that are covered under specific titles. Below is a table that comprises of typical duties and who is responsible for each duty.

As you progress up the ranks, you are expected to maintain your prior level’s duties while taking on the added duties. A focus is given to being able to help the server with your extended privileges.

{| class="wikitable"
!
!Corporate Management
!Systems Management
!Mentor/Monitor Administrators
!Mentor/Monitor Moderators
!Staff Dispute Resolution
!
!Manage Forums
!Manage Server
!Staff Application Verdicts
!Manage Permissions
!Conduct Rollbacks
!Spawn Items
!Regioning
!Vaulting
!Discord Roles
!Player Dispute Resolution
!Player Support/Tickets
|-
|Server Leadership
|✅
|✅
|✅
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Senior Staff
|
|
|✅
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Administrators
|
|
|
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Moderators
|
|
|
|
|
|
|
|
|
|
|
|
|✅
|✅
|✅
|✅
|✅
|}

== Progression ==
Staff progression is based on merit, contribution, and alignment with our staff values. Promotion is determined by a combination of factors, including but not limited to:

* '''Activity''' – Regular and consistent participation.
* '''Character''' – Integrity, professionalism, and attitude.
* '''Competence''' – Skill in performing staff duties effectively.
* '''Suitability for Promotion''' – Readiness and organisational fit to take on higher responsibility.
* '''Engagement with the Server & Community''' – Active involvement and positive influence.
* '''Adherence to Staff Values and Expectations''' – Following policies and expectations.
* '''Communication''' – Ability to challenge ideas constructively and speak up when something is wrong.
* '''Initiative''' – Going above and beyond in problem-solving, leadership, and contributions. ''(This is a major factor in distinguishing top performers.)''

=== Progression is not determined by ===

* Political or business affiliations.
* Personal friendships with other staff members (rapport may be considered, but not decisive).
* Personal support or alignment with any player, political figure, or faction.

=== Who determines your progression to these ranks ===

* '''All''': Your mentor will advise in if and when you are promoted.
* '''Manager:''' Server Leadership
* '''Senior Administrator''': Server Leadership
* '''Administrator''': Senior Administration
* '''Moderator''': Administration Team and above
* '''Trial Moderator''': Administration and above

=== How does progression occur? ===

# '''Nomination''' – A senior staff member raises a nomination, alternatively you may express interest
# '''Discussion''' – The team evaluates the member’s suitability and relevant factors
# '''Vote''' – The nomination is put to a vote
# '''Outcome''' – A decision is reached over time, or after further discussion if needed

{{Staff}}
[[category:staff]]

Staff Responsibilities and Progression

2026-01-20T04:42:04Z

Technofied: Minor formatting tweaks, addition to experience for managers

Staff Responsibilities and Progression

2026-01-20T04:37:21Z

Technofied: Clean up

[[File:TM.png|center|thumb|1055x1055px]]

== Trial Moderator ==
New Staff member undergoing training and evaluation. Trial Moderators assist players, handle tickets, and learn discipline standards while under a mentor's supervision.

==== Experience Needed ====
• No prior experience necessary

{| class="wikitable"
!Responsibilities
!Progression Criteria
|-
|Handle in-game and Discord support tickets
|Complete the Trial Moderator Checklist
|-
|Enforce server rules at a basic level
|Complete the Learning Confirmation
|-
|Use moderation tools (punishments, log searches)
|Be recommended by their Mentor for consideration
|-
|Assist with land, region, and vault issues
|Be recognised by administrative staff as suitable for independent duties
|-
|Learn staff procedures, policies, and expectations
|Possess a willingness to learn, follow guidance, and accept feedback
|-
|Act professionally and represent staff values
|
|}
[[File:M.png|center|thumb|1056x1056px]]

== Moderator ==
Qualified Staff Member responsible for enforcing server rules, resolving player issues, and completing the day-to-day work to keep the server running.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Independently resolve tickets and player issues
|Show consistent high-quality moderation
|Successful completion of Moderator Trial
|-
|Enforce rules in-game and on Discord
|Demonstrate good judgement and discretion
|Proven understanding of rules and moderation tools
|-
|Conduct log reviews and evidence verification
|Be active and engaged with the community
|Demonstrated professionalism and reliability
|-
|Apply punishments appropriately and consistently
|Be recognised by senior staff as suitable for higher responsibility
|
|-
|Act professionally and represent staff values
|
|
|}

[[File:A.png|center|thumb|1055x1055px]]

== Administrator ==
A senior-moderation staff member with leadership and mentoring responsibilities. A position of trust, with additional responsibility over complex issues and other staff members.

{| class="wikitable"
!Responsibilities
!Progression Criteria
!Experience Needed
|-
|Mentor and support Moderators and Trial Moderators
|Demonstrate long-term commitment and reliability
|Extended experience as a Moderator
|-
|Assist with complex tickets and disputes
|Show leadership in staff management and policy application
|Strong knowledge of server systems and policies
|-
|Ensure consistency in rule enforcement
|Show initiative in staffing, as well as suggesting and implementing new ideas
|Proven trustworthiness and leadership capability
|-
|Participate in network decision-making
|Be recognised by server leadership as suitable for higher responsibility
|
|-
|Uphold and reinforce staff standards
|
|
|}

[[File:SA.png|center|thumb|1054x1054px]]

== Senior Administrator ==
High-level staff members entrusted with responsibility over policy, high-risk and sensitive issues, and the strategic direction of the server.

==== Progression ====
• Advancement beyond this role is determined by Server Leadership

{| class="wikitable"
!Responsibilities
!Progression Criteria
|-
|Lead and coordinate Administrators and Moderators
|Significant experience as an Administrator
|-
|Handle high-risk or sensitive cases
|Deep understanding of server operations and culture
|-
|Assist in policy development and enforcement standards
|Strong leadership, judgement, and communication skills
|-
|Participate in promotion and disciplinary decisions
|
|-
|Act as a key point of contact for server leadership
|
|}

[[File:MX.png|center|thumb|1055x1055px]]

== Manager ==
A member of server leadership, they are an ambassador and leader of a respective area of the network (StateCraft, DemocracyCraft, Network Systems).
{| class="wikitable"
!Responsibilities
!Progression Criteria
|-
|Final authority on policies and major decisions
|Extensive experience and trust within the server
|-
|Oversee staff structure and long-term vision
|Demonstrated leadership at the highest level
|-
|Resolve escalated disputes
|Strong leadership, judgement, and communication skills
|-
|Maintain server direction and integrity
|
|}

[[File:Seal Staff 3 sml.png|center|thumb|119x119px]]

== Duties and Expectations ==
Our Staff have several day-to-day roles that are covered under specific titles. Below is a table that comprises of typical duties and who is responsible for each duty.

As you progress up the ranks, you are expected to maintain your prior level’s duties while taking on the added duties. A focus is given to being able to help the server with your extended privileges.

{| class="wikitable"
!
!Corporate Management
!Systems Management
!Mentor/Monitor Administrators
!Mentor/Monitor Moderators
!Staff Dispute Resolution
!
!Manage Forums
!Manage Server
!Staff Application Verdicts
!Manage Permissions
!Conduct Rollbacks
!Spawn Items
!Regioning
!Vaulting
!Discord Roles
!Player Dispute Resolution
!Player Support/Tickets
|-
|Server Leadership
|✅
|✅
|✅
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Senior Staff
|
|
|✅
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Administrators
|
|
|
|✅
|✅
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Moderators
|
|
|
|
|
|
|
|
|
|
|
|
|✅
|✅
|✅
|✅
|✅
|}

== Progression ==
Staff progression is based on merit, contribution, and alignment with our staff values. Promotion is determined by a combination of factors, including but not limited to:

* '''Activity''' – Regular and consistent participation.
* '''Character''' – Integrity, professionalism, and attitude.
* '''Competence''' – Skill in performing staff duties effectively.
* '''Suitability for Promotion''' – Readiness and organisational fit to take on higher responsibility.
* '''Engagement with the Server & Community''' – Active involvement and positive influence.
* '''Adherence to Staff Values and Expectations''' – Following policies and expectations.
* '''Communication''' – Ability to challenge ideas constructively and speak up when something is wrong.
* '''Initiative''' – Going above and beyond in problem-solving, leadership, and contributions. ''(This is a major factor in distinguishing top performers.)''

=== Progression is not determined by ===

* Political or business affiliations.
* Personal friendships with other staff members (rapport may be considered, but not decisive).
* Personal support or alignment with any player, political figure, or faction.

=== Who determines your progression to these ranks ===

* '''All''': Your mentor will advise in if and when you are promoted.
* '''Manager:''' Server Leadership
* '''Senior Administrator''': Server Leadership
* '''Administrator''': Senior Administration
* '''Moderator''': Administration Team and above
* '''Trial Moderator''': Administration and above

=== How does progression occur? ===

# '''Nomination''' – A senior staff member raises a nomination, alternatively you may express interest
# '''Discussion''' – The team evaluates the member’s suitability and relevant factors
# '''Vote''' – The nomination is put to a vote
# '''Outcome''' – A decision is reached over time, or after further discussion if needed

Staff Guide

2026-01-18T12:33:59Z

Technofied: Remove legacy wilderness claiming information

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!

[[File:Staff.png|center|frameless|858x858px]]

== 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
| text = 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.
| type = info
}}{{Note|type=reminder|text=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 <code>/whitelist on</code> to ensure those pesky players stay out of our way.
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete <world></code>.
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create <world></code>.
# Using <code>/gamerule</code>, set <code>keepInventory</code> to <code>false</code>, <code>announceAchievement</code> <code>false</code>, and <code>showDeathMessage</code> to <code>false</code>.
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.
# 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 <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).
# Turn off the server.
# Open <code>Reveille_nether/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "Nether Configuration" (Engine Mode 1)
# Open <code>Reveille_the_end/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "End Configuration" (Engine Mode 1)
# Start the server.
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).
# 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!
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]

==== Steps ====

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

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

You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].

==== Additional Information ====
Here is a [https://www.youtube.com/watch?v=JwijCiueZ3Y 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 [https://cloudflarewarp.com/ Cloudflare Warp].

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

=== Administrative Commands ===
These are useful commands to know with your position.

==== LuckPerms ====

* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.
* <code>/lp editor [type]</code> - 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.
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.

===== User Commands =====

* <code>/lp user <user> info</code>
* <code>/lp user <user> permission</code>
* <code>/lp user <user> parent</code>
* <code>/lp user <user> meta</code>
* <code>/lp user <user> editor</code>
* <code>/lp user <user> promote <track> [context...]</code>
* <code>/lp user <user> demote <track> [context...]</code>
* <code>/lp user <user> showtracks</code>
* <code>/lp user <user> clear [context...]</code>
* <code>/lp user <user> clone <user></code>
{{Note|type=reminder|text=Tip 
Add in-game roles via <code>/lp user <user> parent add <job></code>}}

===== Group Commands =====

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

===== General =====

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

===== Crates =====

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

== 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.

See also: [[Issuing Punishments|Punishment Guide]]

==== 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.

{{Note|type=info|text=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 <code>/alts <username></code>). This scans their account to see if there are any other accounts that are playing on the same IP as them. Once you do <code>/alts</code>, 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 <code>#automod</code> 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 <code>/alts</code> 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 <code>#notes</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#notes</code>. You can also check both accounts’ command histories by running <code>/co lookup</code> 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.

[[File:Flagged_alt_account_examples.png|1291x1291px]]

===== 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 <code>/staff-alttest <player1> <player2></code>
# 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 <code>/staff-notanalt <username 1> <username 2></code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord.

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

Additionally, you could go into <code>/spectator</code> and <code>/staff-tp <player> <reason></code> 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 ====

* <code>/rg define <name></code> - Creates a region.
* <code>/rg remove <region></code> - Removes the specified region.
* <code>/rg redefine <name></code> - Re-sets an existing region to your current selection.
* <code>/rg setparent <region> <parent></code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - 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.
{| class="wikitable"
|+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 [https://worldguard.enginehub.org/en/latest/regions/flags/ 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 <code>//wand</code> to get a wooden axe)
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code>
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code>

===== Commands =====

* <code>//wand</code> - 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
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.
* <code>//cut</code> - copies and clears your current selection.
* <code>//paste</code> - pastes your previous cut selection.
* <code>//expand <amount> [direction]</code> - makes your current selection expand by the amount specified in the specified direction.
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code>
* <code>//sel [poly/cuboid]</code> - select the type of region.
** <code>Cuboid</code> 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
* <code>//sel</code> - when used like this this command will clear your current selection.
* <code>//rotate <degrees></code> - rotates your current clipboard (cut/copy) the specified degrees.
** Degrees have to be in multiples of 90 or it won’t work.
** i.e. <code>90</code>, <code>180</code>, <code>270</code>, <code>360</code>, <code>-90</code>, <code>-180</code>, <code>-270</code>, <code>-360</code>.
* <code>//move <amount of blocks> [direction]</code> - moves your current selection by the amount specified in the specified direction.
* <code>/expand <number> [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific.

====== Directions can be… ======

* '''Relative to the world'''
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.
* '''Relative to the player'''
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>.

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

'''Examples:'''

* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing
* <code>//expand 10 up</code> - Expand 10 blocks upwards
* <code>//expand vert</code> - 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 [https://worldedit.enginehub.org/en/latest/usage/ 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 =====

* <code>/as add <buy/sell> <region></code> - makes a region either a buyable or rentable region.
** Used when making wilderness or apartment/shop regions.
{{Note|text=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.}}
* <code>/as del <region></code> - deletes the specified region from AreaShop.
* <code>/as setprice <price> --region <region></code> - used to set the selling/renting price of an AreaShop region.
* <code>/as setlandlord <name> --region <region></code> - used to set the landlord of an Areashop region.
** Wilderness regions will always have the landlord be <code>“DCGovernment</code>
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.
* <code>/as setowner <player> --region <region></code> - used for when transferring ownership of a region to another player.
* <code>/as addsign <region></code> - used to add an Areashop sign to the sign you’re looking at.
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.
* <code>/as tp <region></code> - 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.
* <code>/as info player <player></code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.
** An alias of this command is <code>/as me <player></code>.
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.
** Can also be used to label chests/buildings when vaulting.
* <code>/staff-getwool</code> - gives you wool which you can use for selection points.
'''Note:''' <code>--region</code> 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 =====

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

==== Using CoreProtect Parameters ====
These can be used in almost every CoreProtect command.

==== <code>u:<user></code> ====

* Specify a user to rollback. Example: u:Technofied

==== <code>t:<time></code> ====
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)

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

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

==== <code>a:<action></code> ====
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>.

'''Here’s a list of all the actions:'''

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

==== <code>b:<blocks></code> ====
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

==== <code>e:<exclude></code> ====
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

==== <code>#<hashtag></code> ====
Add a hashtag to the end of your command to perform additional actions.

'''Example:''' To perform a rollback preview, you would use <code>#preview</code>

'''Here is a list of all available hashtags'''

* <code>#preview</code> - preview a rollback/restore
* <code>#verbose</code> - display additional information during a rollback/restore
* <code>#silent</code> - 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.

{{Note|type=error|text=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 <code>/rg redefine <plot></code>. See below for an example.<div class="figure">
[[File:Merge_regions_example.png|553x553px]]
</div>

===== 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).{{Danger||Child regions may only be created on Commercial and Industrial plots, not residential and are rent only. You '''cannot''' have rent regions within rent regions.|}}

===== 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:''' <code>/rg define <regionName></code>.
*** i.e. <code>/rg define EndStore1</code>.
* '''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:''' <code>/fine <user> <amount> <reason></code>.
*** Select “Staff” as the account to send the fine to.
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.
* '''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:''' <code>/rg parent <regionName> <PlotRegion></code>.
*** i.e. <code>/rg parent EndStore1 c001</code>.
* '''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:''' <code>/as add rent <regionName>.</code>
* '''3.1 Set the landlord'''
** '''Command:''' <code>/as setlandlord <landlord> --region <regionName></code>, this usually is the player who is creating the region, rental money will go to the landlord.
* '''3.2 Set the price'''
** '''Command:''' <code>/as setprice <price> --region <regionName></code>
* '''3.3 Set the duration'''
** '''Command:''' <code>/as setduration <duration> --region <region></code>
** 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 <code>/staff-getsign</code>.
** 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: <code>/as addsign <regionName></code>, 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 <code>/rg info <regionName></code> - 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 <code>/rg info</code> 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 <code>/spec</code> 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 [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]!

==== Wild Regioning: ====
DemocracyCraft utilises a plugin which enables players themselves to create their own Wilderness claims without the need for Staff. Make sure to review [[Wilderness Claiming]], essential information is documented there!

Players are still only allowed '''ONE''' wild claim. Use <code>/listclaims <username></code> to see information about a player.

'''Other relevant commands:'''

* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on.
* <code>/deleteclaim</code> (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 <code>#notes</code>. Search for the player’s full username, before creating a thread. (You can use <code>in:#notes playername</code>.) 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.

{{Note|type=warn|text=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}}
'''''[[Category:Staff]]'''''

Wilderness Claiming

2026-01-18T12:33:20Z

Technofied: No longer need to migrate old areashop claims, as they should not exist anymore!

DemocracyCraft utilises a simple '''self-service claiming system''' for claiming up to '''4,096 blocks''' in the Wilderness!

* Each block costs '''$10''', and can be bought as you acquire the funds
* You start out with '''10 free blocks''' (very generous we know)
* You can only '''claim in the Wilderness, not the Everwild!'''

[[File:Create a Claim in Claims Menu.png|thumb|496x496px|Click '''Create a Claim''' in order to create your claim!]]

== How to create a claim ==

# Travel to the Wilderness (<code>/airport</code>)
# Find a piece of land that you would like to claim
# Run <code>/claim</code> and select '''Create a Claim!'''

You can add people to your claims and more in the <code>/claim</code> menu!

* You can also '''buy more claim blocks in the same menu!'''

== How to expand a claim ==

# Grab a claim wand via <code>/claimwand</code>! '''NOTE:''' You can only claim one wand per day, so don't misplace this wand! '''Any golden shovel will act as a wand however.'''
# <code>'''RIGHT CLICK'''</code> with the claim wand '''anywhere inside''' your claim, you will then see '''a glowstone and gold block perimeter.'''[[File:Example selected Wilderness Claim.png|border|center|thumb|500x500px|You can now see your wilderness claim borders, the '''corners are represented by glowstone!''']]
# <code>'''RIGHT CLICK'''</code> with the claim wand '''any corner''' ('''NOT''' edge!) of your claim to select your corner.[[File:Example corner of a Wilderness region selected.png|border|center|thumb|500x500px|The glowstone has now '''disappeared since you selected it - this is normal!''']]
# <code>'''RIGHT CLICK'''</code> the new position for your corner. '''If you have enough claim blocks, your claim will automatically resize!'''

[[File:Example expanded Wilderness Region.png|border|center|thumb|500x500px|Right click at any '''new position''' to '''expand your Wilderness claim!''' The corner you previously selected has '''moved to the position you selected.''']]

* '''Don't have enough claim blocks?''' Buy more from '''<code>/claim</code>'''!

Rules

2026-01-16T07:44:45Z

Technofied: Theft is no longer a rule as per the Theft Criminalization Act

[[File:Rules_and_Laws_Enforcement.png|thumb|500px|Rules and Laws - Who enforces what?]]
Moderation is an important aspect of keeping our network a welcome and inclusive environment for everyone to enjoy. Below, we’ve included some guidelines that apply on all Minecraft Cities Network platforms.

Staff maintain full discretion in their enforcement of rules and general moderation.

Feel free to ask questions on {{DCDiscord|our Discord server}}<nowiki /> if you have any questions or concerns.

{{Note|type=info|text=Respect the spirit of the rules. These rules are here to protect you - not for us to come after you! You will never be punished for raising a concern regarding rules, regardless of whether it is about yourself or others. 
Something may not be explicitly defined here, that doesn’t necessary make it okay. If you have to consider whether it is allowed, ask!}}
=== 1. Respect ===

* Any form of harassment or discrimination, including (but not limited to): racism, homophobia, transphobia, sexism, antisemitism, stalking, and bigotry are not acceptable ever.
** Our Staff members are players who, in their own time, volunteer to help. Politicizing staff actions, for the sake of roleplay or otherwise, is strictly prohibited. There must be an undeniable separation between staffing and state and this is heavily policed.
** Examples of harassment include (but is not limited to):
*** Targeting a player or group of players through means of stalking, destruction of property or killings.
*** Repeatedly attempting to communicate with a player or groups of after they have explicitly expressed they do not wish to communicate with you.
*** Any other acts which in either frequency or act causes loss of enjoyment of the network on the basis of being an individual, or group, beyond conventional gameplay mechanics (i.e. politicking and running campaign ads against parties etc is still acceptable behaviour.)
* Discussions about controversial topics such as real world politics and world religion are not permitted in public channels.
* You are not allowed to impersonate, mimic, or make malicious doctored images of other players/staff members.
* Tickets must be used for assistance purposes only.
** Be truthful always. We rely on your honest recount alongside our evidence to keep our community safe.
** Trying to lie or misrepresent facts '''intentionally''' may result in additional disciplinary actions.
* All content on this network must be appropriate for minors. This includes all skins, language, and actions on all our platforms.

=== 2. Chat ===

* Please do not excessively repeat phrases, use profanity, and/or capital letters in your messages.
* Profanity or strong language is permitted when used to express emotion or opinion about a situation, but not when directed at or used to insult another person.
* You are not permitted to communicate in '''any''' other languages than English in public channels.
* If your speech is altered by in-game drinks, you are not permitted to speak in public channels.
* You may only use '''/ask''' to ask or answer questions in good faith.
* You '''must''' use the #➕ | Create VC channel on our [//discord.gg/democracy Discord] when you are streaming or recording.
** Inform people who join your voice channel that you are recording.
* Platforms, such as Discord servers, are split into different categories for the purpose of moderation
{| class="wikitable"
|+Categories of platforms
!'''Type'''
!'''Managed by'''
!'''Moderated by'''
!'''Registration required?'''
!'''Responsibilities'''
!'''Limitations'''
!'''Notes'''
|-
|'''Official'''
|Network (staff). If a Government platform → managed by Government but still reported to staff
|Staff or Government
|No
|Must comply with network rules
|Fully integrated with network
|Can be Government-managed but still Staff-moderated
|-
|'''Affiliate'''
|Private players. Associated with Network (e.g. businesses, political parties)
|Staff
|No
|Must comply with network rules. Owners must remove banned players. Must align with network values/responsibilities
|Can advertise on official and other affiliate platforms
|Considered part of Network ecosystem
|-
|'''Non-affiliated'''
|Private players. Not associated with Network
|Individuals (Staff only moderate if blatantly necessary)
|No
|None
|'''Cannot''' '''be advertised''' to network players or share on affiliate/official platforms
|Fully separate from Network
|-
|'''Private conversations'''
|Individuals
|Individuals (Staff only moderate if blatantly necessary)
|No
|None
|Not generally moderated
|Government '''cannot penalise''' players for refusing to provide private messages
|}


=== 3. Advertising ===

* Advertising must be kept to <code>/ad</code> in-game or appropriate advertisement channels on our main Discord platforms
** You must not advertise player-run gambling using <code>/ad</code>
* You must not advertise non-affiliated platforms to network players for any reason
* You must not actively encourage other players onto other major games where it would decrease their engagement in the network (excluding minor team/individual games like Discord games, Among Us, Jackbox)
* Non-affiliated platforms and Minecraft networks that are not allowed to be advertised anywhere
=== 4. Property ===

* Lava casting and flooding is not permitted '''anywhere.'''
* You may not use lockable items (e.g., doors, buttons, etc.) to protect '''whole or partial structures'''
** It is acceptable to lock barrels, doors, etc for normal gameplay purposes
* You may not destroy, obstruct, or otherwise disturb property that you do not own, '''unless it is in the Wilderness''''''/End/Nether'''

=== 5. Lag Prevention ===

* Redstone clocks are not permitted in any builds. There must be a player interaction to activate the redstone circuit on each occurrence.
* All farms must either be manual or '''semi'''-automatic and are required to have player interactions.
* You must avoid using excessive tile entities (chests, hoppers, item frames) or regular entities (mobs) in builds and designated spaces.
** Item frames must only be used to display '''non-vanilla''' items. This applies especially for ChestShops
=== 6. Fair Play ===

* Permissions must be used strictly for the reasons you told you can have them for
** Many Government jobs contain additional features or access. It is your responsibility to use them responsibly and only for appropriate reasons
** Chatter directly inside government announcement channels are strictly prohibited
* You are allowed to use client modifications from our [[Client Modifications]] '''only'''
** Any proceeds from x-ray texture packs will be confiscated
* Any methods to avoid being kicked for being away-from-keyboard that is not genuine gameplay is not allowed
* Any form of exploitation is not permitted for any reason
** This includes abusing bugs in network features
** This includes any form of attempting to breach, exploit, scan, or otherwise gain access to systems, bots, accounts, or data without permission
* You can only play on this network with one Minecraft account across all network platforms
** Any activities that occur on this account are your responsibility
* Business entities cannot transact in '''real-world currency'''
* If your account is compromised, report it! We will try to help you out, and keep the account banned until you regain access to it
[[File:Bystanders.png|Rules and Laws - Let’s avoid Bystanders]]

=== Issuing Punishments ===
Punishments are not linear, and depend heavily on the circumstances of each contravention of the rules.

This means the following factors typically get considered prior to issuing a punishment:

* '''Severity''' of the contravention - how serious the behaviour was and its impact
* '''Intent -''' whether the action was deliberate, negligent, or accidental
* '''Context''' - what was happening at the time, including any provocation or misunderstandings
* '''Player history -''' any previous warnings, notes, or prior contraventions
* '''Attitude and cooperation''' - whether the player was honest, respectful, or attempted to evade responsibility
* '''Impact''' - whether other players or backend systems were affected, and to what extent
* '''Mitigating or aggravating factors''' - anything that reasonably reduces or increases culpability
** e.g., attempts to fix the issue vs. attempts to conceal it
* '''Behavioural patterns''' - whether there is recurring misconduct, ongoing negativity, or persistent disruptive behaviour
** This is not to be confused with player standing, only the player’s conduct and documented history may be considered

Where it is possible and reasonable to do so, we try to enforce '''punishment parity.'''

* e.g. if you are warned on our network's Discord platforms, you may be warned in-game as well

=== Types of Punishments ===

==== Permanent ====
* Banned from all network and affiliated platforms
* Cannot participate in network courts, events, or have assets distributed per their wishes
* Ban is indefinite; appeals via formal process only
* Must be removed from all official/affiliated platforms

==== Temporary ====
* Restricted from in-game servers and official Discords only
* Not required to leave affiliate or unofficial platforms
* Assets remain unless otherwise specified
* Can participate in network courts (forums only)
* Considered politically incapacitated for the period of their punishment

At the end of the day, our rules are here to foster safe and inclusive gameplay, accordingly Staff have discretion on how to enforce rules as they see fit.

CraftingStore

2026-01-10T08:13:59Z

Technofied: Create CraftingStore guide

== Parameters ==
These can be used in almost every CoreProtect command.

=== <code>u:<user></code> ===

* Specify a user to rollback. Example: u:Technofied

=== <code>t:<time></code> ===
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)

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

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

=== <code>a:<action></code> ===
Restrict the rollback to a certain action.

'''Here’s a list of all the actions:'''

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

'''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>.

=== <code>b:<blocks></code> ===
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

=== <code>e:<exclude></code> ===
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

=== <code>#<hashtag></code> ===
Add a hashtag to the end of your command to perform additional actions.

'''Example:''' To perform a rollback preview, you would use <code>#preview</code>

'''Here is a list of all available hashtags'''

* <code>#preview</code> - preview a rollback/restore
* <code>#verbose</code> - display additional information during a rollback/restore
* <code>#silent</code> - display minimal information during a rollback/restore

Template:Staff

2026-01-09T16:39:10Z

Technofied: Add SVPs Guide

<includeonly>{{Navbox
| name =
| title = [[Staff]]
| listclass = hlist

| image = [[File:stafficon.png|50px]]

| group1 = Leadership Guides
| list1 =
* [[Server Panel Access]]

| group2 = Administration Guides
| list2 =
* [[Restoring Files]]
* [[Forums Admin Control Panel (ACP)]]
* [[Using LuckPerms Verbose]]
* [[Screening Players For VPNs]]
* [[Imagemap Naming Guide]]
* [[Getting CPI Data]]

| group3 = Staff-wide Guides
| list3 =
* [[Staff Guide]]
* [[Everything Senior Vice Presidents (SVPs)]]
* [[Quick Reference Staff Guide]]
* [[Staff Discord Tickets Guide]]
* [[Issuing Punishments]]
* [[Vaulting]]
* [[WorldEdit]]

| group4 = Policy
| list4 =
* [[Staff Intent]]
* [[Staff Vetos]]
* [[Staff Career Progression, Expectations, and Disciplinary]]
* [[Staff Conflict Of Interest Policy]]
* [[Client Modifications]]
* [[Replacement Policy]]

| group5 = Resources
| list5 =
* [[Bug Tracker]]
* [[Trial Moderator Checklist]]

| below = [[:Category:Staff|Category]]
}}
</includeonly><noinclude>
{{Staff}}
[[Category:Staff]]

</noinclude>

Everything Senior Vice Presidents (SVPs)

2026-01-09T16:38:19Z

Technofied: Add footer

Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

== Elections ==
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

=== SVP Election Months ===

* January
* March
* June
* September
* November

== SVP Morale ==
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

=== Responsibilities ===

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

== SVP Talent (Administrators+) ==
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

=== Responsibilities ===

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

== SVP Justice (Administrators+) ==
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

=== Responsibilities ===

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

== SVP Retention (Administrators+) ==
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

=== Responsibilities ===

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

== SVP History ==
As SVP History, you are the owner/curator of the Staff/Server museum. Go to /gps staff-museum to have a look!

=== Responsibilities ===

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date

{{Staff}}
[[Category:Staff]]

Staff Guide

2026-01-09T16:37:58Z

Technofied: Split out SVPs from 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!

[[File:Staff.png|center|frameless|858x858px]]

== 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
| text = 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.
| type = info
}}{{Note|type=reminder|text=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 <code>/whitelist on</code> to ensure those pesky players stay out of our way.
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete <world></code>.
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create <world></code>.
# Using <code>/gamerule</code>, set <code>keepInventory</code> to <code>false</code>, <code>announceAchievement</code> <code>false</code>, and <code>showDeathMessage</code> to <code>false</code>.
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.
# 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 <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).
# Turn off the server.
# Open <code>Reveille_nether/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "Nether Configuration" (Engine Mode 1)
# Open <code>Reveille_the_end/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "End Configuration" (Engine Mode 1)
# Start the server.
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).
# 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!
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]

==== Steps ====

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

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

You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].

==== Additional Information ====
Here is a [https://www.youtube.com/watch?v=JwijCiueZ3Y 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 [https://cloudflarewarp.com/ Cloudflare Warp].

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

=== Administrative Commands ===
These are useful commands to know with your position.

==== LuckPerms ====

* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.
* <code>/lp editor [type]</code> - 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.
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.

===== User Commands =====

* <code>/lp user <user> info</code>
* <code>/lp user <user> permission</code>
* <code>/lp user <user> parent</code>
* <code>/lp user <user> meta</code>
* <code>/lp user <user> editor</code>
* <code>/lp user <user> promote <track> [context...]</code>
* <code>/lp user <user> demote <track> [context...]</code>
* <code>/lp user <user> showtracks</code>
* <code>/lp user <user> clear [context...]</code>
* <code>/lp user <user> clone <user></code>
{{Note|type=reminder|text=Tip 
Add in-game roles via <code>/lp user <user> parent add <job></code>}}

===== Group Commands =====

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

===== General =====

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

===== Crates =====

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

== 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.

See also: [[Issuing Punishments|Punishment Guide]]

==== 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.

{{Note|type=info|text=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 <code>/alts <username></code>). This scans their account to see if there are any other accounts that are playing on the same IP as them. Once you do <code>/alts</code>, 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 <code>#automod</code> 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 <code>/alts</code> 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 <code>#notes</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#notes</code>. You can also check both accounts’ command histories by running <code>/co lookup</code> 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.

[[File:Flagged_alt_account_examples.png|1291x1291px]]

===== 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 <code>/staff-alttest <player1> <player2></code>
# 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 <code>/staff-notanalt <username 1> <username 2></code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord.

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

Additionally, you could go into <code>/spectator</code> and <code>/staff-tp <player> <reason></code> 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 ====

* <code>/rg define <name></code> - Creates a region.
* <code>/rg remove <region></code> - Removes the specified region.
* <code>/rg redefine <name></code> - Re-sets an existing region to your current selection.
* <code>/rg setparent <region> <parent></code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - 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.
{| class="wikitable"
|+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 [https://worldguard.enginehub.org/en/latest/regions/flags/ 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 <code>//wand</code> to get a wooden axe)
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code>
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code>

===== Commands =====

* <code>//wand</code> - 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
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.
* <code>//cut</code> - copies and clears your current selection.
* <code>//paste</code> - pastes your previous cut selection.
* <code>//expand <amount> [direction]</code> - makes your current selection expand by the amount specified in the specified direction.
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code>
* <code>//sel [poly/cuboid]</code> - select the type of region.
** <code>Cuboid</code> 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
* <code>//sel</code> - when used like this this command will clear your current selection.
* <code>//rotate <degrees></code> - rotates your current clipboard (cut/copy) the specified degrees.
** Degrees have to be in multiples of 90 or it won’t work.
** i.e. <code>90</code>, <code>180</code>, <code>270</code>, <code>360</code>, <code>-90</code>, <code>-180</code>, <code>-270</code>, <code>-360</code>.
* <code>//move <amount of blocks> [direction]</code> - moves your current selection by the amount specified in the specified direction.
* <code>/expand <number> [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific.

====== Directions can be… ======

* '''Relative to the world'''
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.
* '''Relative to the player'''
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>.

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

'''Examples:'''

* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing
* <code>//expand 10 up</code> - Expand 10 blocks upwards
* <code>//expand vert</code> - 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 [https://worldedit.enginehub.org/en/latest/usage/ 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 =====

* <code>/as add <buy/sell> <region></code> - makes a region either a buyable or rentable region.
** Used when making wilderness or apartment/shop regions.
{{Note|text=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.}}
* <code>/as del <region></code> - deletes the specified region from AreaShop.
* <code>/as setprice <price> --region <region></code> - used to set the selling/renting price of an AreaShop region.
* <code>/as setlandlord <name> --region <region></code> - used to set the landlord of an Areashop region.
** Wilderness regions will always have the landlord be <code>“DCGovernment</code>
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.
* <code>/as setowner <player> --region <region></code> - used for when transferring ownership of a region to another player.
* <code>/as addsign <region></code> - used to add an Areashop sign to the sign you’re looking at.
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.
* <code>/as tp <region></code> - 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.
* <code>/as info player <player></code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.
** An alias of this command is <code>/as me <player></code>.
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.
** Can also be used to label chests/buildings when vaulting.
* <code>/staff-getwool</code> - gives you wool which you can use for selection points.
'''Note:''' <code>--region</code> 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 =====

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

==== Using CoreProtect Parameters ====
These can be used in almost every CoreProtect command.

==== <code>u:<user></code> ====

* Specify a user to rollback. Example: u:Technofied

==== <code>t:<time></code> ====
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)

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

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

==== <code>a:<action></code> ====
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>.

'''Here’s a list of all the actions:'''

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

==== <code>b:<blocks></code> ====
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

==== <code>e:<exclude></code> ====
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

==== <code>#<hashtag></code> ====
Add a hashtag to the end of your command to perform additional actions.

'''Example:''' To perform a rollback preview, you would use <code>#preview</code>

'''Here is a list of all available hashtags'''

* <code>#preview</code> - preview a rollback/restore
* <code>#verbose</code> - display additional information during a rollback/restore
* <code>#silent</code> - 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.

{{Note|type=error|text=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 <code>/rg redefine <plot></code>. See below for an example.<div class="figure">
[[File:Merge_regions_example.png|553x553px]]
</div>

===== 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).{{Danger||Child regions may only be created on Commercial and Industrial plots, not residential and are rent only. You '''cannot''' have rent regions within rent regions.|}}

===== 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:''' <code>/rg define <regionName></code>.
*** i.e. <code>/rg define EndStore1</code>.
* '''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:''' <code>/fine <user> <amount> <reason></code>.
*** Select “Staff” as the account to send the fine to.
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.
* '''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:''' <code>/rg parent <regionName> <PlotRegion></code>.
*** i.e. <code>/rg parent EndStore1 c001</code>.
* '''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:''' <code>/as add rent <regionName>.</code>
* '''3.1 Set the landlord'''
** '''Command:''' <code>/as setlandlord <landlord> --region <regionName></code>, this usually is the player who is creating the region, rental money will go to the landlord.
* '''3.2 Set the price'''
** '''Command:''' <code>/as setprice <price> --region <regionName></code>
* '''3.3 Set the duration'''
** '''Command:''' <code>/as setduration <duration> --region <region></code>
** 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 <code>/staff-getsign</code>.
** 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: <code>/as addsign <regionName></code>, 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 <code>/rg info <regionName></code> - 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 <code>/rg info</code> 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 <code>/spec</code> 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 [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region 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 <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code>
# Click on Bounds to select the player's old claim
# Get some wool with <code>/staff-getwool</code> and mark the corners of the region, this will assist the player in claiming their region again later.
# Run <code>//count #yaxis</code> to get the number of surface blocks
# Run <code>/staff-grant-claim-blocks <username> <amount of blocks></code>, replacing <code><amount of blocks></code> with the number from <code>//count</code> This will send a message in <code>#staff-team</code> 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 <code>/as setowner DCGovernment</code> - this is very important :)
# Run <code>/rg-d <username></code> to kill the old region then <code>/as del --region <username></code>. 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 <code>/listclaims <username></code> to see information about a player, the command will show you something similar to this:
[[File:Listclaim.png|thumb|453x453px]]

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:'''

* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on.
* <code>/deleteclaim</code> (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 <code>#notes</code>. Search for the player’s full username, before creating a thread. (You can use <code>in:#notes playername</code>.) 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.

{{Note|type=warn|text=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}}
'''''[[Category:Staff]]'''''

Everything Senior Vice Presidents (SVPs)

2026-01-09T16:35:45Z

Technofied: Technofied moved page Senior Vice Presidents to Everything Senior Vice Presidents (SVPs) without leaving a redirect: Match title from old migrated guide

Template:Staff

2026-01-09T16:31:15Z

Technofied: Add new guides

<includeonly>{{Navbox
| name =
| title = [[Staff]]
| listclass = hlist

| image = [[File:stafficon.png|50px]]

| group1 = Leadership Guides
| list1 =
* [[Server Panel Access]]

| group2 = Administration Guides
| list2 =
* [[Restoring Files]]
* [[Forums Admin Control Panel (ACP)]]
* [[Using LuckPerms Verbose]]
* [[Screening Players For VPNs]]
* [[Imagemap Naming Guide]]
* [[Getting CPI Data]]

| group3 = Staff-wide Guides
| list3 =
* [[Staff Guide]]
* [[Quick Reference Staff Guide]]
* [[Staff Discord Tickets Guide]]
* [[Issuing Punishments]]
* [[Vaulting]]
* [[WorldEdit]]

| group4 = Policy
| list4 =
* [[Staff Intent]]
* [[Staff Vetos]]
* [[Staff Career Progression, Expectations, and Disciplinary]]
* [[Staff Conflict Of Interest Policy]]
* [[Client Modifications]]
* [[Replacement Policy]]

| group5 = Resources
| list5 =
* [[Bug Tracker]]
* [[Trial Moderator Checklist]]

| below = [[:Category:Staff|Category]]
}}
</includeonly><noinclude>
{{Staff}}
[[Category:Staff]]

</noinclude>

Staff Guide

2026-01-09T16:30:27Z

Technofied: Split out many guides and delete old information

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!

[[File:Staff.png|center|frameless|858x858px]]

== 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
| text = 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.
| type = info
}}{{Note|type=reminder|text=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 <code>/whitelist on</code> to ensure those pesky players stay out of our way.
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete <world></code>.
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create <world></code>.
# Using <code>/gamerule</code>, set <code>keepInventory</code> to <code>false</code>, <code>announceAchievement</code> <code>false</code>, and <code>showDeathMessage</code> to <code>false</code>.
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.
# 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 <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).
# Turn off the server.
# Open <code>Reveille_nether/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "Nether Configuration" (Engine Mode 1)
# Open <code>Reveille_the_end/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "End Configuration" (Engine Mode 1)
# Start the server.
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).
# 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!
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]

==== Steps ====

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

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

You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].

==== Additional Information ====
Here is a [https://www.youtube.com/watch?v=JwijCiueZ3Y 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 [https://cloudflarewarp.com/ Cloudflare Warp].

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

=== Administrative Commands ===
These are useful commands to know with your position.

==== LuckPerms ====

* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.
* <code>/lp editor [type]</code> - 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.
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.

===== User Commands =====

* <code>/lp user <user> info</code>
* <code>/lp user <user> permission</code>
* <code>/lp user <user> parent</code>
* <code>/lp user <user> meta</code>
* <code>/lp user <user> editor</code>
* <code>/lp user <user> promote <track> [context...]</code>
* <code>/lp user <user> demote <track> [context...]</code>
* <code>/lp user <user> showtracks</code>
* <code>/lp user <user> clear [context...]</code>
* <code>/lp user <user> clone <user></code>
{{Note|type=reminder|text=Tip 
Add in-game roles via <code>/lp user <user> parent add <job></code>}}

===== Group Commands =====

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

===== General =====

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

===== Crates =====

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

== 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.

See also: [[Issuing Punishments|Punishment Guide]]

==== 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.

{{Note|type=info|text=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 <code>/alts <username></code>). This scans their account to see if there are any other accounts that are playing on the same IP as them. Once you do <code>/alts</code>, 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 <code>#automod</code> 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 <code>/alts</code> 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 <code>#notes</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#notes</code>. You can also check both accounts’ command histories by running <code>/co lookup</code> 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.

[[File:Flagged_alt_account_examples.png|1291x1291px]]

===== 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 <code>/staff-alttest <player1> <player2></code>
# 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 <code>/staff-notanalt <username 1> <username 2></code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord.

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

Additionally, you could go into <code>/spectator</code> and <code>/staff-tp <player> <reason></code> 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 ====

* <code>/rg define <name></code> - Creates a region.
* <code>/rg remove <region></code> - Removes the specified region.
* <code>/rg redefine <name></code> - Re-sets an existing region to your current selection.
* <code>/rg setparent <region> <parent></code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - 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.
{| class="wikitable"
|+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 [https://worldguard.enginehub.org/en/latest/regions/flags/ 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 <code>//wand</code> to get a wooden axe)
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code>
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code>

===== Commands =====

* <code>//wand</code> - 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
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.
* <code>//cut</code> - copies and clears your current selection.
* <code>//paste</code> - pastes your previous cut selection.
* <code>//expand <amount> [direction]</code> - makes your current selection expand by the amount specified in the specified direction.
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code>
* <code>//sel [poly/cuboid]</code> - select the type of region.
** <code>Cuboid</code> 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
* <code>//sel</code> - when used like this this command will clear your current selection.
* <code>//rotate <degrees></code> - rotates your current clipboard (cut/copy) the specified degrees.
** Degrees have to be in multiples of 90 or it won’t work.
** i.e. <code>90</code>, <code>180</code>, <code>270</code>, <code>360</code>, <code>-90</code>, <code>-180</code>, <code>-270</code>, <code>-360</code>.
* <code>//move <amount of blocks> [direction]</code> - moves your current selection by the amount specified in the specified direction.
* <code>/expand <number> [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific.

====== Directions can be… ======

* '''Relative to the world'''
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.
* '''Relative to the player'''
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>.

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

'''Examples:'''

* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing
* <code>//expand 10 up</code> - Expand 10 blocks upwards
* <code>//expand vert</code> - 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 [https://worldedit.enginehub.org/en/latest/usage/ 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 =====

* <code>/as add <buy/sell> <region></code> - makes a region either a buyable or rentable region.
** Used when making wilderness or apartment/shop regions.
{{Note|text=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.}}
* <code>/as del <region></code> - deletes the specified region from AreaShop.
* <code>/as setprice <price> --region <region></code> - used to set the selling/renting price of an AreaShop region.
* <code>/as setlandlord <name> --region <region></code> - used to set the landlord of an Areashop region.
** Wilderness regions will always have the landlord be <code>“DCGovernment</code>
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.
* <code>/as setowner <player> --region <region></code> - used for when transferring ownership of a region to another player.
* <code>/as addsign <region></code> - used to add an Areashop sign to the sign you’re looking at.
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.
* <code>/as tp <region></code> - 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.
* <code>/as info player <player></code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.
** An alias of this command is <code>/as me <player></code>.
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.
** Can also be used to label chests/buildings when vaulting.
* <code>/staff-getwool</code> - gives you wool which you can use for selection points.
'''Note:''' <code>--region</code> 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 =====

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

==== Using CoreProtect Parameters ====
These can be used in almost every CoreProtect command.

==== <code>u:<user></code> ====

* Specify a user to rollback. Example: u:Technofied

==== <code>t:<time></code> ====
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)

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

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

==== <code>a:<action></code> ====
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>.

'''Here’s a list of all the actions:'''

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

==== <code>b:<blocks></code> ====
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

==== <code>e:<exclude></code> ====
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

==== <code>#<hashtag></code> ====
Add a hashtag to the end of your command to perform additional actions.

'''Example:''' To perform a rollback preview, you would use <code>#preview</code>

'''Here is a list of all available hashtags'''

* <code>#preview</code> - preview a rollback/restore
* <code>#verbose</code> - display additional information during a rollback/restore
* <code>#silent</code> - 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.

{{Note|type=error|text=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 <code>/rg redefine <plot></code>. See below for an example.<div class="figure">
[[File:Merge_regions_example.png|553x553px]]
</div>

===== 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).{{Danger||Child regions may only be created on Commercial and Industrial plots, not residential and are rent only. You '''cannot''' have rent regions within rent regions.|}}

===== 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:''' <code>/rg define <regionName></code>.
*** i.e. <code>/rg define EndStore1</code>.
* '''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:''' <code>/fine <user> <amount> <reason></code>.
*** Select “Staff” as the account to send the fine to.
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.
* '''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:''' <code>/rg parent <regionName> <PlotRegion></code>.
*** i.e. <code>/rg parent EndStore1 c001</code>.
* '''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:''' <code>/as add rent <regionName>.</code>
* '''3.1 Set the landlord'''
** '''Command:''' <code>/as setlandlord <landlord> --region <regionName></code>, this usually is the player who is creating the region, rental money will go to the landlord.
* '''3.2 Set the price'''
** '''Command:''' <code>/as setprice <price> --region <regionName></code>
* '''3.3 Set the duration'''
** '''Command:''' <code>/as setduration <duration> --region <region></code>
** 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 <code>/staff-getsign</code>.
** 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: <code>/as addsign <regionName></code>, 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 <code>/rg info <regionName></code> - 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 <code>/rg info</code> 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 <code>/spec</code> 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 [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region 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 <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code>
# Click on Bounds to select the player's old claim
# Get some wool with <code>/staff-getwool</code> and mark the corners of the region, this will assist the player in claiming their region again later.
# Run <code>//count #yaxis</code> to get the number of surface blocks
# Run <code>/staff-grant-claim-blocks <username> <amount of blocks></code>, replacing <code><amount of blocks></code> with the number from <code>//count</code> This will send a message in <code>#staff-team</code> 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 <code>/as setowner DCGovernment</code> - this is very important :)
# Run <code>/rg-d <username></code> to kill the old region then <code>/as del --region <username></code>. 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 <code>/listclaims <username></code> to see information about a player, the command will show you something similar to this:
[[File:Listclaim.png|thumb|453x453px]]

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:'''

* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on.
* <code>/deleteclaim</code> (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 <code>#notes</code>. Search for the player’s full username, before creating a thread. (You can use <code>in:#notes playername</code>.) 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.

{{Note|type=warn|text=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!

=== Everything Senior Vice Presidents (SVPs) ===
Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

==== Elections ====
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

===== SVP Election Months =====

* January
* March
* June
* September
* November

==== SVP Morale ====
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

===== Responsibilities =====

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

==== SVP Talent (Administrators+) ====
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

===== Responsibilities =====

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

==== SVP Justice (Administrators+) ====
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

===== Responsibilities: =====

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

==== SVP Retention (Administrators+) ====
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

===== Responsibilities =====

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

==== SVP History ====
As SVP History, you are the owner/curator of the Staff/Server museum.

===== Responsibilities =====

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date 
{{Staff}}
'''''[[Category:Staff]]'''''

WorldEdit

2026-01-09T16:30:07Z

Technofied: Start migrating from old mega Staff guide

This guide will provide a concise overview on the basic features of WorldEdit. This guide follows the Staff training warp, made available for our newly minted Staff members, however this guide may prove useful to players too who wish to use WorldEdit (i.e. in their player build world plots).

== Commands ==
{| class="wikitable"
|+Most commonly used commands
!Command
!Description
!
!
|-
|//wand
|Gives you a WorldEdit 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
|
|
|
|}
To finish being migrated.

== Getting Started ==
[[File:Player running --wand.png|thumb|468x468px|Once you run //wand, you will be given a '''WorldEdit wand''' and instructions on how to use it in chat.]]
For most WorldEdit operations, you will need the WorldEdit '''wand.'''

* '''Command:''' <code>//wand</code>

A wooden axe will be deposited into your inventory, this is your '''WorldEdit wand.'''
{{Note
| type = info
| text = '''Fun Fact''' 
Any wooden axe can technically serve as a WorldEdit wand!
}}

== Selections ==
Using your WorldEdit wand, you are able to '''select blocks to be transformed.''' We use two types of selection:

* Cuboid '''(default)'''
* Polyhedron
Alternatively, you could

* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code>
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code>

==== Cuboid ====
This type of selection is the most common, and is the default option you are given when you obtain a WorldEdit wand.

* '''Command:''' <code>//sel cuboid</code>
** You only need to run this command when you have '''changed your selection type''' '''to polyhedron and need to go back to cuboid!'''

===== Usage =====
[[File:WorldEdit Cuboid Selection.gif|thumb|529x529px|'''Click the GIF above to play.''' After left and right clicking to form your selection, you will additionally '''see fire particles confirming your selection.''']]

# '''LEFT CLICK''' the block to select your '''first position''' with your wand.
# '''RIGHT CLICK''' the block to select your '''second position''' with your wand.

==== Polyhedron ====
This type of selection is the most common when you are dealing with unique shapes, such as apartments or other rental regions.

* '''Command:''' <code>//sel poly</code>
[[File:Polysel.gif|thumb|Click the GIF above to play. Select your starting position with a right click, then left click in a clockwise or counterclockwise direction for the remaining points.]]

===== Usage =====

# '''LEFT CLICK''' the block to select your '''starting position''' with your wand.
# '''RIGHT CLICK''' the block to select your '''nth position''' with your wand.
#* You can keep right clicking until '''you have selected all the points to close your shape.'''
#* Select your points in a clockwise/counterclockwise direction.
{{Note
| type = warn
| text = '''Make sure to right click your first position to close the shape'''
You must right click your first position at the ''very end'' of your selection to ensure it is a closed shape.
}}

== Moving selections ==

To be finished.{{Staff}}
[[Category:Staff]]

Server Panel Access

2026-01-09T16:22:16Z

Technofied: Add Staff tags

Managers are responsible for adding '''Senior Administrators''' and '''Administrators''' to our server control panel. To add a user, follow the steps below.

# Open the <code>DemocracyCraft</code> server
# Navigate to <code>Users</code> and click <code>New User</code>
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission node
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team
# Paste it in the input box, and click <code>Import</code>
# Repeat Steps 2-6 after opening the <code>MinecraftCitiesNetwork Playground</code> server and <code>StateCraft</code> server.
# Great work! All done. :)

{{Note
| type = reminder
| text = Tip 
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!
}}

==== Ranks and Privileges ====

===== Senior Administrators =====
<pre>["control.read-console","control.console","control.start","control.restart","file.create","file.read","file.read-content","file.update","file.delete","file.archive","file.sftp","recycle.read","recycle.restore","backup.create","backup.read","database.create","database.read","database.update","database.view_password","database.import","schedule.create","schedule.read","schedule.update","activity.read","websocket.connect","control.stop","allocation.read","startup.read","backup.restore"]</pre>

===== Administrators =====
<pre>["control.read-console","control.console","control.start","control.restart","file.create","file.read","file.read-content","file.update","file.archive","recycle.read","recycle.restore","backup.create","backup.read","database.read","schedule.read","activity.read","websocket.connect","control.stop","allocation.read","startup.read"]</pre>

{{Staff}}
[[category:staff]]

Server Panel Access

2026-01-09T16:21:54Z

Technofied: Migrate from mega Staff Guide

Forums Admin Control Panel (ACP)

2026-01-09T16:17:13Z

Technofied: Add Staff tags

As an Administrator you have access to our forums control panel. Here you can update user roles and profiles, as well as manage various forum functionality.

You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]

== User Confidentiality ==
You will have access to more information than a regular player. This information is in confidence and as always, we have a zero tolerance approach to any breaches of privacy.

== User Role Management ==
{{Note
| type = error
| text = Attention 
Never update a user’s primary group. It should always be <code>Registered</code>.
}}

[[File:Registered_group.png|902x902px]]

When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''

Staff changes require two separate roles and one option: <code>Show as Staff</code>, <code>Staff</code>, and <code>Moderator/Administrator/Senior Administrator</code>. Below is an example of what Technofied's Secondary Groups looks like.

[[File:Secondary_group.png|898x898px]]

==== Broken Role Syncing ====
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.

{{Note
| type = reminder
| text = Reminder 
Make sure the player has linked their in-game account to their Forums account first! They can do /register any time to confirm this.
}}

===== Steps =====

# Remove all their Secondary Group Roles ('''excluding''' Staff roles!)
# Ask them to log in, wait 5 minutes, then log out
# Ask them to log back in after 2-3 seconds

{{Staff}}
[[category:staff]]

Forums Admin Control Panel (ACP)

2026-01-09T16:17:00Z

Technofied: Migrate from mega Staff Guide

Staff Career Progression and Disciplinary

2026-01-09T16:13:40Z

Technofied: Technofied moved page Staff Career Progression and Disciplinary to Staff Career Progression, Expectations, and Disciplinary: Clearer title

#REDIRECT [[Staff Career Progression, Expectations, and Disciplinary]]

Staff Expectations and Disciplinary

2026-01-09T16:13:39Z

Technofied: Technofied moved page Staff Career Progression and Disciplinary to Staff Career Progression, Expectations, and Disciplinary: Clearer title

The purpose of this guide is to provide information on how staff are selected and how staff members progress in their careers. This guide also provides guidance on staff-specific disciplinary actions.

== Values ==
The Staff team operates on four core values

# '''Service''' - The selflessness of character to place the interests of our server and its players ahead of your own. Often measured in '''activity, ticket taken''' etc.
# '''Integrity -''' The consistency of character to align your thoughts, words, and actions to do what is right. This refers to your '''honesty and moral strength'''.
# '''Respect -''' The humanity of character to value others and treat them with dignity, with relation to how you engage with your peers and the wider community.
# '''Excellence''' - The willingness of character to strive each day to be the best you can be, both in a staff context and personally. This is also known as '''<nowiki/>'going above and beyond!''''

== Progression ==
Staff progression is determined by a series of factors such as, but not limited to:

# Activity
# Character
# Competence
# Suitability for promotion
# Engagement with the Server and it’s community
# Adherence to Staff Values and Expectations
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).
# Initiative (this is massive! What elevates you above your peers?)

=== What staff progression is '''not''' determined by ===

* Your political or business affiliations, spicy or not.
* Your friendship with other staff members. Your rapport, however, will be considered.
* Whether you simp for, or are politically aligned to, End or Tech.

=== Who determines your progression to these ranks ===

* '''All''': Your mentor will advise in if and when you are promoted.
* '''Senior Administrator''': Server Leadership
* '''Administrator''': Senior Staff
* '''Moderator''': Administration Team+
* '''Trial Moderator''': Administration Team+

=== How does it work? ===

# A member of the team, generally a senior staff member, will raise a nomination for discussion. (you can flag interest, generally about 4-6 months in your role).
# A discussion is had about the member’s suitability and other defining factors.
# The nomination is put to vote. Generally no comments are provided by the poster of the vote in the vote channel itself in order to maintain neutrality.
# An outcome is reached over time or after further discussion.

== Staff Disciplinary System ==
If a staff member has been punished under the staff disciplinary system (SDS), they will not be punished under the server rules for the same breach. The staff disciplinary system takes precedence.

=== 1. Coaching ===
Coaching is an informal process which is not recorded. Coaching is provided to staff members who make minor mistakes by their staff mentor or other more senior staff members. The aim of coaching is to prevent the behaviour from happening again by discussing what went wrong and how it could be dealt with differently next time.

=== 2. Warning ===
Warnings are a formal process which is recorded in the Staff member’s channel. Warnings are provided to staff members who continue to repeat behaviours after coaching or who have made errors in judgement. All warnings are tied to a Staff Value(s).

=== 3. Notice to Show Cause (NTSC) ===
A NTSC is a formal process which is recorded in the Staff member’s channel. A NTSC is provided to staff members who have received an unreasonable amount of warnings, or for continued warnings based on the same behaviours. A NTSC may also be issued to staff who have made significant errors in judgement.

== Duties and Expectations ==
Our Staff have several day-to-day roles that are covered under specific titles. Below is a table that comprises of typical duties and who is responsible for each duty.

As you progress up the ranks, you are expected to maintain your prior level’s duties while taking on the added duties. A focus is given to being able to help the server with your extended privilages.
{| class="wikitable"
!
!Corporate Management
!Systems Management
!Mentor/Monitor Administrators
!Mentor/Monitor Moderators
!Staff Dispute Resolution
!Player Dispute Resolution
!Manage Forums
!Manage Server
!Staff Application Verdicts
!Manage Permissions
!Conduct Rollbacks
!Discord Roles
!Spawn Items
!Regioning
!Vaulting
!Player Support/Tickets
|-
|Server Leadership
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Senior Staff
|
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Administrators
|
|
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Moderators
|
|
|
|
|
|✅
|
|
|
|
|
|✅
|
|✅
|✅
|✅
|}

=== Expectations ===

* As a staff member you have access to certain staff-related information. This should not be shared with anyone outside of the staff team.
* Respect player confidentiality.
* Be integral. Don’t steal. Don’t lie.
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!
* If you aren’t sure, ask your fellow staff members!
* Approach tickets in a timely, friendly, and helpful manner.
* Respect and value the advice of staff that are senior to you.
* Staff permissions are used for tickets while assisting other players only.
* Be positive! - Smile :)

{{Staff}}
[[category:staff]]

Staff Expectations and Disciplinary

2026-01-09T16:11:24Z

Technofied: Migrate rest of the guide

Staff Expectations and Disciplinary

2026-01-09T16:09:19Z

Technofied: Fix Staff tags

Staff Guide

2026-01-09T16:08:07Z

Technofied: Remove Staff Career Progression and Disciplinary

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!

[[File:Staff.png|center|frameless|858x858px]]

== Staff-wide Policies ==
These are policies every Staff member should be familiar with!

=== Staff Disciplinary System ===
If a staff member has been punished under the staff disciplinary system (SDS), they will not be punished under the server rules for the same breach. The staff disciplinary system takes precedence.

==== 1. Coaching ====
Coaching is an informal process which is not recorded. Coaching is provided to staff members who make minor mistakes by their staff mentor or other more senior staff members. The aim of coaching is to prevent the behaviour from happening again by discussing what went wrong and how it could be dealt with differently next time.

==== 2. Warning ====
Warnings are a formal process which is recorded in the Staff member’s channel. Warnings are provided to staff members who continue to repeat behaviours after coaching or who have made errors in judgement. All warnings are tied to a Staff Value(s).

==== 3. Notice to Show Cause (NTSC) ====
A NTSC is a formal process which is recorded in the Staff member’s channel. A NTSC is provided to staff members who have received an unreasonable amount of warnings, or for continued warnings based on the same behaviours. A NTSC may also be issued to staff who have made significant errors in judgement.

=== Duties and Expectations ===
Our Staff have several day-to-day roles that are covered under specific titles. Below is a table that comprises of typical duties and who is responsible for each duty.

As you progress up the ranks, you are expected to maintain your prior level’s duties while taking on the added duties. A focus is given to being able to help the server with your extended privilages.
{| class="wikitable"
!
!Corporate Management
!Systems Management
!Mentor/Monitor Administrators
!Mentor/Monitor Moderators
!Staff Dispute Resolution
!Player Dispute Resolution
!Manage Forums
!Manage Server
!Staff Application Verdicts
!Manage Permissions
!Conduct Rollbacks
!Discord Roles
!Spawn Items
!Regioning
!Vaulting
!Player Support/Tickets
|-
|Server Leadership
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Senior Staff
|
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Administrators
|
|
|
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|✅
|-
|Moderators
|
|
|
|
|
|✅
|
|
|
|
|
|✅
|
|✅
|✅
|✅
|}

==== Expectations ====

* As a staff member you have access to certain staff-related information. This should not be shared with anyone outside of the staff team. Respect player confidentiality.
* Be integral. Don’t steal. Don’t lie.
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!
* If you aren’t sure, ask your fellow staff members!
* Approach tickets in a timely, friendly, and helpful manner.
* Respect and value the advice of staff that are senior to you.
* Staff permissions are used for tickets while assisting other players only.
* Be positive! - Smile :)

== For Managers ==
=== Panel Access ===
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.

# Open the <code>DemocracyCraft</code> server.
# Navigate to <code>Users</code> and click <code>New User</code>.
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.
# Paste it in the input box, and click <code>Import</code>.
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.
# Great work! All done. :)
{{Note|type=reminder|text=Tip 
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}

==== Ranks and Privileges ====
===== Senior Administrators =====
<pre>["control.read-console","control.console","control.start","control.restart","file.create","file.read","file.read-content","file.update","file.delete","file.archive","file.sftp","recycle.read","recycle.restore","backup.create","backup.read","database.create","database.read","database.update","database.view_password","database.import","schedule.create","schedule.read","schedule.update","activity.read","websocket.connect","control.stop","allocation.read","startup.read","backup.restore"]</pre>

===== Administrators =====
<pre>["control.read-console","control.console","control.start","control.restart","file.create","file.read","file.read-content","file.update","file.archive","recycle.read","recycle.restore","backup.create","backup.read","database.read","schedule.read","activity.read","websocket.connect","control.stop","allocation.read","startup.read"]</pre>

== 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|text=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.|type=info}}{{Note|type=reminder|text=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 <code>/whitelist on</code> to ensure those pesky players stay out of our way.
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete <world></code>.
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create <world></code>.
# Using <code>/gamerule</code>, set <code>keepInventory</code> to <code>false</code>, <code>announceAchievement</code> <code>false</code>, and <code>showDeathMessage</code> to <code>false</code>.
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.
# 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 <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).
# Turn off the server.
# Open <code>Reveille_nether/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "Nether Configuration" (Engine Mode 1)
# Open <code>Reveille_the_end/paper_world.yml</code> and add below <code>_version</code> the [https://docs.papermc.io/paper/anti-xray#engine-mode-1 following] from the "End Configuration" (Engine Mode 1)
# Start the server.
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).
# Announce the change in #server-announcements!

=== Red v. Blue Event Guide for Staff ===

==== 1. Purge old teams ====

# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.
## <code>lp bulkupdate all delete "permission == group.blue"</code>
## <code>lp bulkupdate all delete "permission == group.red"</code>

==== 2. Setting up Team Selection ====

# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.
# Run <code>/mycmd-blockset create</code> while looking at the target block.
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.

==== 3. Team Verification / Checks ====

# You should be able to see the teams displayed on TAB
# Make sure that it is assisnging the teams at random through the GUI.
# Announce the change in #changelog!

==== 4. Post Event Checks ====

# Create and provide rewards to the DPA.
# Purge teams again, by following Step 1.

== 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!
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]

==== Steps ====

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

=== Understanding your Forums Privilages ===
As an administrator you have access to our forums control panel. Here you can update user roles and profiles, as well as manage various forum functionality.

You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]

==== User Confidentiality ====
You will have access to more information than a regular player. This information is in confidence and as always, we have a zero tolerance approach to privacy breaches.

==== User Role Management ====
{{Note|type=error|text=Attention 
Never update a user’s primary group. It should always be <code>Registered</code>.}}
[[File:Registered_group.png|902x902px]]

When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''

Staff changes require two separate roles and one option: <code>Show as Staff</code>, <code>Staff</code>, and <code>Moderator/Administrator/Senior Administrator</code>. Below is an example of what Technofied's Secondary Groups looks like.

[[File:Secondary_group.png|898x898px]]

==== Broken Role Syncing ====
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.
{{Note|type=reminder|text=Reminder 
Make sure the player has linked their in-game account to their Forums account first! They can do /register any time to confirm this.}}

===== Steps =====

# Remove all their Secondary Group Roles (excluding Staff roles!)
# Ask them to log in, wait 5 minutes, then log out.
# Ask them to log back in after 2-3 seconds

=== 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 ====

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

You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].

==== Additional Information ====
Here is a [https://www.youtube.com/watch?v=JwijCiueZ3Y 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 [https://cloudflarewarp.com/ Cloudflare Warp].

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

=== Administrative Commands ===
These are useful commands to know with your position.

==== LuckPerms ====

* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.
* <code>/lp editor [type]</code> - 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.
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.

===== User Commands =====

* <code>/lp user <user> info</code>
* <code>/lp user <user> permission</code>
* <code>/lp user <user> parent</code>
* <code>/lp user <user> meta</code>
* <code>/lp user <user> editor</code>
* <code>/lp user <user> promote <track> [context...]</code>
* <code>/lp user <user> demote <track> [context...]</code>
* <code>/lp user <user> showtracks</code>
* <code>/lp user <user> clear [context...]</code>
* <code>/lp user <user> clone <user></code>
{{Note|type=reminder|text=Tip 
Add in-game roles via <code>/lp user <user> parent add <job></code>}}

===== Group Commands =====

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

===== General =====

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

===== Crates =====

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

== 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.

See also: [[Issuing Punishments|Punishment Guide]]

==== 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.

{{Note|type=info|text=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 <code>/alts <username></code>). This scans their account to see if there are any other accounts that are playing on the same IP as them. Once you do <code>/alts</code>, 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 <code>#automod</code> 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 <code>/alts</code> 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 <code>#notes</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#notes</code>. You can also check both accounts’ command histories by running <code>/co lookup</code> 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.

[[File:Flagged_alt_account_examples.png|1291x1291px]]

===== 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 <code>/staff-alttest <player1> <player2></code>
# 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 <code>/staff-notanalt <username 1> <username 2></code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord.

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

Additionally, you could go into <code>/spectator</code> and <code>/staff-tp <player> <reason></code> 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 ====

* <code>/rg define <name></code> - Creates a region.
* <code>/rg remove <region></code> - Removes the specified region.
* <code>/rg redefine <name></code> - Re-sets an existing region to your current selection.
* <code>/rg setparent <region> <parent></code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - 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.
{| class="wikitable"
|+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 [https://worldguard.enginehub.org/en/latest/regions/flags/ 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 <code>//wand</code> to get a wooden axe)
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code>
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code>

===== Commands =====

* <code>//wand</code> - 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
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.
* <code>//cut</code> - copies and clears your current selection.
* <code>//paste</code> - pastes your previous cut selection.
* <code>//expand <amount> [direction]</code> - makes your current selection expand by the amount specified in the specified direction.
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code>
* <code>//sel [poly/cuboid]</code> - select the type of region.
** <code>Cuboid</code> 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
* <code>//sel</code> - when used like this this command will clear your current selection.
* <code>//rotate <degrees></code> - rotates your current clipboard (cut/copy) the specified degrees.
** Degrees have to be in multiples of 90 or it won’t work.
** i.e. <code>90</code>, <code>180</code>, <code>270</code>, <code>360</code>, <code>-90</code>, <code>-180</code>, <code>-270</code>, <code>-360</code>.
* <code>//move <amount of blocks> [direction]</code> - moves your current selection by the amount specified in the specified direction.
* <code>/expand <number> [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific.

====== Directions can be… ======

* '''Relative to the world'''
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.
* '''Relative to the player'''
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>.

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

'''Examples:'''

* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing
* <code>//expand 10 up</code> - Expand 10 blocks upwards
* <code>//expand vert</code> - 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 [https://worldedit.enginehub.org/en/latest/usage/ 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 =====

* <code>/as add <buy/sell> <region></code> - makes a region either a buyable or rentable region.
** Used when making wilderness or apartment/shop regions.
{{Note|text=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.}}
* <code>/as del <region></code> - deletes the specified region from AreaShop.
* <code>/as setprice <price> --region <region></code> - used to set the selling/renting price of an AreaShop region.
* <code>/as setlandlord <name> --region <region></code> - used to set the landlord of an Areashop region.
** Wilderness regions will always have the landlord be <code>“DCGovernment</code>
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.
* <code>/as setowner <player> --region <region></code> - used for when transferring ownership of a region to another player.
* <code>/as addsign <region></code> - used to add an Areashop sign to the sign you’re looking at.
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.
* <code>/as tp <region></code> - 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.
* <code>/as info player <player></code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.
** An alias of this command is <code>/as me <player></code>.
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.
** Can also be used to label chests/buildings when vaulting.
* <code>/staff-getwool</code> - gives you wool which you can use for selection points.
'''Note:''' <code>--region</code> 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 =====

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

==== Using CoreProtect Parameters ====
These can be used in almost every CoreProtect command.

==== <code>u:<user></code> ====

* Specify a user to rollback. Example: u:Technofied

==== <code>t:<time></code> ====
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)

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

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

==== <code>a:<action></code> ====
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>.

'''Here’s a list of all the actions:'''

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

==== <code>b:<blocks></code> ====
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

==== <code>e:<exclude></code> ====
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

==== <code>#<hashtag></code> ====
Add a hashtag to the end of your command to perform additional actions.

'''Example:''' To perform a rollback preview, you would use <code>#preview</code>

'''Here is a list of all available hashtags'''

* <code>#preview</code> - preview a rollback/restore
* <code>#verbose</code> - display additional information during a rollback/restore
* <code>#silent</code> - 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.

{{Note|type=error|text=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 <code>/rg redefine <plot></code>. See below for an example.<div class="figure">
[[File:Merge_regions_example.png|553x553px]]
</div>

===== 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).{{Danger||Child regions may only be created on Commercial and Industrial plots, not residential and are rent only. You '''cannot''' have rent regions within rent regions.|}}

===== 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:''' <code>/rg define <regionName></code>.
*** i.e. <code>/rg define EndStore1</code>.
* '''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:''' <code>/fine <user> <amount> <reason></code>.
*** Select “Staff” as the account to send the fine to.
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.
* '''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:''' <code>/rg parent <regionName> <PlotRegion></code>.
*** i.e. <code>/rg parent EndStore1 c001</code>.
* '''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:''' <code>/as add rent <regionName>.</code>
* '''3.1 Set the landlord'''
** '''Command:''' <code>/as setlandlord <landlord> --region <regionName></code>, this usually is the player who is creating the region, rental money will go to the landlord.
* '''3.2 Set the price'''
** '''Command:''' <code>/as setprice <price> --region <regionName></code>
* '''3.3 Set the duration'''
** '''Command:''' <code>/as setduration <duration> --region <region></code>
** 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 <code>/staff-getsign</code>.
** 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: <code>/as addsign <regionName></code>, 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 <code>/rg info <regionName></code> - 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 <code>/rg info</code> 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 <code>/spec</code> 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 [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region 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 <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code>
# Click on Bounds to select the player's old claim
# Get some wool with <code>/staff-getwool</code> and mark the corners of the region, this will assist the player in claiming their region again later.
# Run <code>//count #yaxis</code> to get the number of surface blocks
# Run <code>/staff-grant-claim-blocks <username> <amount of blocks></code>, replacing <code><amount of blocks></code> with the number from <code>//count</code> This will send a message in <code>#staff-team</code> 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 <code>/as setowner DCGovernment</code> - this is very important :)
# Run <code>/rg-d <username></code> to kill the old region then <code>/as del --region <username></code>. 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 <code>/listclaims <username></code> to see information about a player, the command will show you something similar to this:
[[File:Listclaim.png|thumb|453x453px]]

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:'''

* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on.
* <code>/deleteclaim</code> (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 <code>#notes</code>. Search for the player’s full username, before creating a thread. (You can use <code>in:#notes playername</code>.) 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.

{{Note|type=warn|text=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!

=== Everything Senior Vice Presidents (SVPs) ===
Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

==== Elections ====
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

===== SVP Election Months =====

* January
* March
* June
* September
* November

==== SVP Morale ====
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

===== Responsibilities =====

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

==== SVP Talent (Administrators+) ====
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

===== Responsibilities =====

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

==== SVP Justice (Administrators+) ====
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

===== Responsibilities: =====

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

==== SVP Retention (Administrators+) ====
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

===== Responsibilities =====

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

==== SVP History ====
As SVP History, you are the owner/curator of the Staff/Server museum.

===== Responsibilities =====

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date 
{{Staff}}
'''''[[Category:Staff]]'''''

Staff Expectations and Disciplinary

2026-01-09T16:07:55Z

Technofied: Split from mega Staff Guide

Template:Staff

2026-01-09T16:05:15Z

Technofied: Fix lists and cleanup

<includeonly>{{Navbox
| name =
| title = [[Staff]]
| listclass = hlist

| image = [[File:stafficon.png|50px]]

| group1 = Leadership Guides
| list1 =
* [[Staff Guide]]

| group2 = Administration Guides
| list2 =
* [[Restoring Files]]
* [[Using LuckPerms Verbose]]
* [[Screening Players For VPNs]]
* [[Imagemap Naming Guide]]
* [[Getting CPI Data]]

| group3 = Staff-wide Guides
| list3 =
* [[Staff Guide]]
* [[Quick Reference Staff Guide]]
* [[Staff Discord Tickets Guide]]
* [[Issuing Punishments]]
* [[Vaulting]]
* [[WorldEdit]]

| group4 = Policy
| list4 =
* [[Staff Intent]]
* [[Staff Vetos]]
* [[Staff Conflict Of Interest Policy]]
* [[Client Modifications]]
* [[Replacement Policy]]

| group5 = Resources
| list5 =
* [[Bug Tracker]]
* [[Trial Moderator Checklist]]

| below = [[:Category:Staff|Category]]
}}
</includeonly><noinclude>
{{Staff}}
[[Category:Staff]]

</noinclude>

Template:Staff

2026-01-09T16:03:01Z

Technofied: Split out template into sections

<includeonly>{{Navbox
| name =
| title = [[Staff]]
| listclass = hlist

| image = [[File:stafficon.png|50px]]

| group1 = Leadership Guides
| list1 =
* [[Staff Guide]]

| group2 = Administrator Guides
| list1 =
* [[Restoring Files]]
* [[Using LuckPerms Verbose]]
* [[Screening Players For VPNs]]
* [[Imagemap Naming Guide]]
* [[Getting CPI Data]]
* [[WorldEdit]]

| group3 = General Guides
| list1 =
* [[Staff Guide]]
* [[Quick Reference Staff Guide]]
* [[Staff Discord Tickets Guide]]
* [[Issuing Punishments]]
* [[Vaulting]]
* [[WorldEdit]]

| group4 = Information
| list2 =
* [[Staff Intent]]
* [[Staff Vetos]]
* [[Staff Conflict Of Interest Policy]]
* [[Client Modifications]]
* [[Replacement Policy]]

| group5 = Resources
| list3 =
* [[Bug Tracker]]
* [[Trial Moderator Checklist]]

| below = [[:Category:Staff|Category]]
}}
</includeonly><noinclude>
{{Staff}}
[[Category:Staff]]

</noinclude>

Rules

2026-01-06T09:51:31Z

Technofied: Tidied up /ask addition

[[File:Rules_and_Laws_Enforcement.png|thumb|500px|Rules and Laws - Who enforces what?]]
Moderation is an important aspect of keeping our network a welcome and inclusive environment for everyone to enjoy. Below, we’ve included some guidelines that apply on all Minecraft Cities Network platforms.

Staff maintain full discretion in their enforcement of rules and general moderation.

Feel free to ask questions on {{DCDiscord|our Discord server}}<nowiki /> if you have any questions or concerns.

{{Note|type=info|text=Respect the spirit of the rules. These rules are here to protect you - not for us to come after you! You will never be punished for raising a concern regarding rules, regardless of whether it is about yourself or others. 
Something may not be explicitly defined here, that doesn’t necessary make it okay. If you have to consider whether it is allowed, ask!}}
=== 1. Respect ===

* Any form of harassment or discrimination, including (but not limited to): racism, homophobia, transphobia, sexism, antisemitism, stalking, and bigotry are not acceptable ever.
** Our Staff members are players who, in their own time, volunteer to help. Politicizing staff actions, for the sake of roleplay or otherwise, is strictly prohibited. There must be an undeniable separation between staffing and state and this is heavily policed.
** Examples of harassment include (but is not limited to):
*** Targeting a player or group of players through means of stalking, destruction of property or killings.
*** Repeatedly attempting to communicate with a player or groups of after they have explicitly expressed they do not wish to communicate with you.
*** Any other acts which in either frequency or act causes loss of enjoyment of the network on the basis of being an individual, or group, beyond conventional gameplay mechanics (i.e. politicking and running campaign ads against parties etc is still acceptable behaviour.)
* Discussions about controversial topics such as real world politics and world religion are not permitted in public channels.
* You are not allowed to impersonate, mimic, or make malicious doctored images of other players/staff members.
* Tickets must be used for assistance purposes only.
** Be truthful always. We rely on your honest recount alongside our evidence to keep our community safe.
** Trying to lie or misrepresent facts '''intentionally''' may result in additional disciplinary actions.
* All content on this network must be appropriate for minors. This includes all skins, language, and actions on all our platforms.

=== 2. Chat ===

* Please do not excessively repeat phrases, use profanity, and/or capital letters in your messages.
* Profanity or strong language is permitted when used to express emotion or opinion about a situation, but not when directed at or used to insult another person.
* You are not permitted to communicate in '''any''' other languages than English in public channels.
* If your speech is altered by in-game drinks, you are not permitted to speak in public channels.
* You may only use '''/ask''' to ask or answer questions in good faith.
* You '''must''' use the #➕ | Create VC channel on our [//discord.gg/democracy Discord] when you are streaming or recording.
** Inform people who join your voice channel that you are recording.
* Platforms, such as Discord servers, are split into different categories for the purpose of moderation
{| class="wikitable"
|+Categories of platforms
!'''Type'''
!'''Managed by'''
!'''Moderated by'''
!'''Registration required?'''
!'''Responsibilities'''
!'''Limitations'''
!'''Notes'''
|-
|'''Official'''
|Network (staff). If a Government platform → managed by Government but still reported to staff
|Staff or Government
|No
|Must comply with network rules
|Fully integrated with network
|Can be Government-managed but still Staff-moderated
|-
|'''Affiliate'''
|Private players. Associated with Network (e.g. businesses, political parties)
|Staff
|No
|Must comply with network rules. Owners must remove banned players. Must align with network values/responsibilities
|Can advertise on official and other affiliate platforms
|Considered part of Network ecosystem
|-
|'''Non-affiliated'''
|Private players. Not associated with Network
|Individuals (Staff only moderate if blatantly necessary)
|No
|None
|'''Cannot''' '''be advertised''' to network players or share on affiliate/official platforms
|Fully separate from Network
|-
|'''Private conversations'''
|Individuals
|Individuals (Staff only moderate if blatantly necessary)
|No
|None
|Not generally moderated
|Government '''cannot penalise''' players for refusing to provide private messages
|}


=== 3. Advertising ===

* Advertising must be kept to <code>/ad</code> in-game or appropriate advertisement channels on our main Discord platforms
** You must not advertise player-run gambling using <code>/ad</code>
* You must not advertise non-affiliated platforms to network players for any reason
* You must not actively encourage other players onto other major games where it would decrease their engagement in the network (excluding minor team/individual games like Discord games, Among Us, Jackbox)
* Non-affiliated platforms and Minecraft networks that are not allowed to be advertised anywhere
=== 4. Property ===

* Lava casting and flooding is not permitted '''anywhere.'''
* Stealing is not allowed inside regioned areas such as urban plots and wild claims
* You may not use lockable items (e.g., doors, buttons, etc.) to protect '''whole or partial structures'''
** It is acceptable to lock barrels, doors, etc for normal gameplay purposes
* You may not destroy, obstruct, or otherwise disturb property that you do not own, '''unless it is in the Wilderness''''''/End/Nether'''

=== 5. Lag Prevention ===

* Redstone clocks are not permitted in any builds. There must be a player interaction to activate the redstone circuit on each occurrence.
* All farms must either be manual or '''semi'''-automatic and are required to have player interactions.
* You must avoid using excessive tile entities (chests, hoppers, item frames) or regular entities (mobs) in builds and designated spaces.
** Item frames must only be used to display '''non-vanilla''' items. This applies especially for ChestShops
=== 6. Fair Play ===

* Permissions must be used strictly for the reasons you told you can have them for
** Many Government jobs contain additional features or access. It is your responsibility to use them responsibly and only for appropriate reasons
** Chatter directly inside government announcement channels are strictly prohibited
* You are allowed to use client modifications from our [[Client Modifications]] '''only'''
** Any proceeds from x-ray texture packs will be confiscated
* Any methods to avoid being kicked for being away-from-keyboard that is not genuine gameplay is not allowed
* Any form of exploitation is not permitted for any reason
** This includes abusing bugs in network features
** This includes any form of attempting to breach, exploit, scan, or otherwise gain access to systems, bots, accounts, or data without permission
* You can only play on this network with one Minecraft account across all network platforms
** Any activities that occur on this account are your responsibility
* Business entities cannot transact in '''real-world currency'''
* If your account is compromised, report it! We will try to help you out, and keep the account banned until you regain access to it
[[File:Bystanders.png|Rules and Laws - Let’s avoid Bystanders]]

=== Issuing Punishments ===
Punishments are not linear, and depend heavily on the circumstances of each contravention of the rules.

This means the following factors typically get considered prior to issuing a punishment:

* '''Severity''' of the contravention - how serious the behaviour was and its impact
* '''Intent -''' whether the action was deliberate, negligent, or accidental
* '''Context''' - what was happening at the time, including any provocation or misunderstandings
* '''Player history -''' any previous warnings, notes, or prior contraventions
* '''Attitude and cooperation''' - whether the player was honest, respectful, or attempted to evade responsibility
* '''Impact''' - whether other players or backend systems were affected, and to what extent
* '''Mitigating or aggravating factors''' - anything that reasonably reduces or increases culpability
** e.g., attempts to fix the issue vs. attempts to conceal it
* '''Behavioural patterns''' - whether there is recurring misconduct, ongoing negativity, or persistent disruptive behaviour
** This is not to be confused with player standing, only the player’s conduct and documented history may be considered

Where it is possible and reasonable to do so, we try to enforce '''punishment parity.'''

* e.g. if you are warned on our network's Discord platforms, you may be warned in-game as well

=== Types of Punishments ===

==== Permanent ====
* Banned from all network and affiliated platforms
* Cannot participate in network courts, events, or have assets distributed per their wishes
* Ban is indefinite; appeals via formal process only
* Must be removed from all official/affiliated platforms

==== Temporary ====
* Restricted from in-game servers and official Discords only
* Not required to leave affiliate or unofficial platforms
* Assets remain unless otherwise specified
* Can participate in network courts (forums only)
* Considered politically incapacitated for the period of their punishment

At the end of the day, our rules are here to foster safe and inclusive gameplay, accordingly Staff have discretion on how to enforce rules as they see fit.

Everything Senior Vice Presidents (SVPs)

2026-01-02T16:10:04Z

Technofied: Attempt to fix staff category yet again, oops

Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

== Elections ==
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

=== SVP Election Months ===

* January
* March
* June
* September
* November

== SVP Morale ==
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

=== Responsibilities ===

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

== SVP Talent (Administrators+) ==
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

=== Responsibilities ===

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

== SVP Justice (Administrators+) ==
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

=== Responsibilities ===

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

== SVP Retention (Administrators+) ==
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

=== Responsibilities ===

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

== SVP History ==
As SVP History, you are the owner/curator of the Staff/Server museum.

=== Responsibilities ===

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date

[[Category:Staff]]

Everything Senior Vice Presidents (SVPs)

2026-01-02T16:09:36Z

Technofied: Try to fix Staff category tag again

Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

== Elections ==
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

=== SVP Election Months ===

* January
* March
* June
* September
* November

== SVP Morale ==
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

=== Responsibilities ===

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

== SVP Talent (Administrators+) ==
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

=== Responsibilities ===

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

== SVP Justice (Administrators+) ==
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

=== Responsibilities ===

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

== SVP Retention (Administrators+) ==
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

=== Responsibilities ===

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

== SVP History ==
As SVP History, you are the owner/curator of the Staff/Server museum.

=== Responsibilities ===

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date

[[[Category:Staff]]]

Everything Senior Vice Presidents (SVPs)

2026-01-02T16:08:20Z

Technofied: Split SVP guide into its own page

Senior Vice Presidents or SVPs started as joke roles mocking mimicking corporate hierarchies. SVP roles now serve a function within the staff team and as development roles for staff members.

== Elections ==
Like the truly democratic server that we are, the outgoing SVP morale will conduct SVP elections every 2 months. How do these elections work? Its up to the SVP morale. SVP elections are not democratic, they are fun. You can’t have the same role back-to-back!

=== SVP Election Months ===

* January
* March
* June
* September
* November

== SVP Morale ==
As SVP Morale you are the Chief Happiness Officer of the team. The Monarch of the SVPs - you are the ringleader. Your mission: Organise. Epic. Staff. Events. Bring your event planning skills, meme expertise, and ability to juggle jokes and logistics together.

=== Responsibilities ===

* Organise Staff events
* Help others organise Staff events
* Organise Staff competitions

== SVP Talent (Administrators+) ==
As SVP Talent, you hold the vital role of the Staff Whisperer. Your mission: to attract suitable candidates and ensure a smooth application process. Bring your keen eye for character and the ability to navigate the intricate world of staff recruitment.

=== Responsibilities ===

* Seek out and encourage potential staff members to apply Monitor staff applications, ensuring they are promptly reviewed and presented for a fair and timely voting process.
** Can be posted by anyone, you just make sure its happening.

== SVP Justice (Administrators+) ==
As SVP Justice, you are the Judge, Jury, and Executioner. Your mission: to ensure that punishment appeals are reviewed promptly and fairly. You can also make summary decisions on frivolous appeals without putting them to the admin team for voting.

=== Responsibilities ===

* Oversee the appeals process, ensuring that punishment appeals are acknowledged and handled in a timely manner Facilitate discussions among staff members involved in the appeal, encouraging constructive dialogue and diverse perspectives
* Summarily decide the verdict of minor appeals which don’t need to go before the admin team (i.e. frivolous appeals, cake-less appeals, poem-less appeals, appeals that just should be accepted on the spot).
* Sends verdict in game via staff command.

== SVP Retention (Administrators+) ==
As SVP Retention, you are the mediator between Staff and the people. Your job is to collect information on what players want the most out of the server and then come up with ideas on how to implement it.

=== Responsibilities ===

* Gather information on most wanted features. Come up with your own ideas that would help with player retention
* Implement those ideas either with Staff help or Department of Education (depending on the feature)
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.
* Keep engaged in the #suggestions channel and respond on behalf of the staff team (if you don't know the answer, ask and then pass it on as well :)).

== SVP History ==
As SVP History, you are the owner/curator of the Staff/Server museum.

=== Responsibilities ===

* Keep the Staff/Server museum up-to-date
* Keep the spawn current staff wall up-to-date

[[[Category: Staff]]]

Client Modifications

2025-12-27T06:34:31Z

Technofied: Added More Overlays Updated

While most enjoy the Vanilla Minecraft experience, some of us prefer to make some changes. Below is a guide to the resourcepacks and client-side mods that have been approved by our staff team. This is not an exhaustive list, rather just a list of mods that we have already approved. Mods '''can be used''' outside of this list '''in accordance with the client modifications rule.'''


== Resource Packs (Texture Packs) ==

Resource Packs are used to change the appearance of the game.


=== Prohibited Resource Packs ===
Any pack which may give a player a tangible and material '''unfair advantage''', these include:
* X-Ray packs
** These give a player the ability to see through non-transparent blocks
* Full Bright packs

{{Note|type=info|text=It never hurts to ask! If you have a mod you are thinking of playing with but don’t see it here. You can always ask a staff member for approval within a Support Ticket on discord!}}

== Modifications ==

Below are the lists of approved modifications for Fabric and Forge respectively.

* Cosmetic mods and performance enhancing mods are not included in these lists as they aren’t typically problematic
* Any supporting/dependency mods for the below listed mods are also permitted

'''Fabric Mods'''

* AppleSkin - https://www.curseforge.com/minecraft/mc-mods/appleskin
* Inventory HUD+ - https://www.curseforge.com/minecraft/mc-mods/inventory-hud-forge
* Inventory Tweak - https://modrinth.com/mod/inventorytweak
* Jade - https://www.curseforge.com/minecraft/mc-mods/jade
* Litematica - https://www.curseforge.com/minecraft/mc-mods/litematica
* MiniHUD - https://www.curseforge.com/minecraft/mc-mods/minihud
* Mod Menu - https://www.curseforge.com/minecraft/mc-mods/modmenu
* More Overlays Updated - https://www.curseforge.com/minecraft/mc-mods/more-overlays-updated
* Roughly Enough Items - https://www.curseforge.com/minecraft/mc-mods/roughly-enough-items
* ShulkerBoxTooltip - https://www.curseforge.com/minecraft/mc-mods/shulkerboxtooltip
* Status Effect Timer - https://www.curseforge.com/minecraft/mc-mods/status-effect-timer
* Xaero’s Minimap (Fair-Play Edition) - https://www.curseforge.com/minecraft/mc-mods/xaeros-minimap-fair-play-edition
* Xaero’s World Map - https://www.curseforge.com/minecraft/mc-mods/xaeros-world-map

'''Forge Mods'''

* AppleSkin - https://www.curseforge.com/minecraft/mc-mods/appleskin
* Inventory HUD+ - https://www.curseforge.com/minecraft/mc-mods/inventory-hud-forge
* Inventory Tweak - https://www.curseforge.com/minecraft/mc-mods/inventory-sorter
* Jade - https://www.curseforge.com/minecraft/mc-mods/jade
* More Overlays Updated - https://www.curseforge.com/minecraft/mc-mods/more-overlays-updated
* Roughly Enough Items - https://www.curseforge.com/minecraft/mc-mods/roughly-enough-items
* Shulker Tooltip - https://www.curseforge.com/minecraft/mc-mods/shulker-tooltip
* Xaero’s Minimap (Fair-Play Edition) - https://www.curseforge.com/minecraft/mc-mods/xaeros-minimap-fair-play-edition
* Xaero’s World Map - https://www.curseforge.com/minecraft/mc-mods/xaeros-world-map

'''Other Allowed Mods'''

* Vivecraft - https://www.vivecraft.org/
* Questcraft - https://sidequestvr.com/app/7150/questcraft

'''Cinematic Recording and Replay Mods'''

We permit the use of mods that allow you to spectate outside a player's physical character for the purposes of recording and producing media and '''must not be used to locate players, entities, or resources''' that would otherwise be hidden.

* A general rule of the thumb is not to use these mods to visit areas your player physically cannot access, unless it is a public property (e.g. Government building) that you are not restricted from in any way
{{Note
| type = warn
| text = Staff are consistently monitoring gameplay to ensure compliance with the rules. Violating the rules could result in '''disciplinary action!'''
}}

== Mod Packs ==

Here are some mod packs that you can use on our server. All mods within these mod packs are approved, so feel free to mix and match them with the other approved mods, as shown above.

'''Fabric Packs'''

* Fabulously Optimized - https://www.curseforge.com/minecraft/modpacks/fabulously-optimized
* Performance+ - https://www.curseforge.com/minecraft/modpacks/performance
* Performance+ Extended - https://www.curseforge.com/minecraft/modpacks/performance-extended

'''Forge'''

None currently approved.

{{Note|type=info|text=Have a suggestion? Head to #suggestions on the {{DCDiscord|DemocracyCraft Discord}} to give us a recommendation! }}

{{Staff}}
[[Category:Staff]]

ExcellentJobs

2025-11-21T04:41:37Z

Technofied: Fix codeblock

This is the plugin we use to control levelling up and rewards for the following jobs listed below.
{| class="wikitable"
|+Available Jobs
!Name
!Maximum Level Attainable
|-
|Farmer
|100
|-
|Fisher
|100
|-
|Hunter
|100
|-
|Lumberjack
|100
|}

== Levelling ==
The maximum level is simply an integer (number) that is assigned to each job. It can be increased or decreased as such.

== Income ==
The maximum amount of income a player can earn is dependent on the '''level''' of the job they have.

* As such, you '''cannot set a maximum amount of earned income for all levels.'''

Each job’s income is determined by four options:
{| class="wikitable"
!Option
!Meaning
|-
|<code>Base</code>
|Starting amount (paid regardless of level).
|-
|<code>Per_Level</code>
|Amount added (or multiplied) per step of levels.
|-
|<code>Step</code>
|How often the increment is applied (in levels).
|-
|<code>Action</code>
|Whether <code>Per_Level</code> is added to or multiplies the base.
|}
The formula applied is:<syntaxhighlight>
steps = floor(jobLevel / Step)
floor() means the number inside the brackets is rounded DOWN

If Action is ADD
perLevel = steps * Per_Level
result = (Base + perLevel)

If Action is MULTIPLY
result = (Base * perLevel)
</syntaxhighlight>'''Remember, there is no clamp or hard limit built into this formula.'''

To hit a maximum payout (e.g. $1,500 at level 100), you must design the formula so the values '''reach that amount''' at the '''highest possible level.'''

== Example (ADD Action) ==
<syntaxhighlight lang="yaml" line="1">
Currency:
money:
Base: 0
Per_Level: 15
Step: 1
Action: ADD
</syntaxhighlight>At level 100:

<code>steps = 100 / 1 = 100</code>

<code>income = 0 + (100 × 15) = $1,500</code>

== Adjusting the Rate of Increase ==
If income grows too quickly, increase the <code>Step</code> value.
{| class="wikitable"
!Step
!Per_Level
!Max (Level 100)
|-
|1
|15
|$1,500
|-
|5
|75
|$1,500
|-
|10
|150
|$1,500
|}
The higher the step, the slower the progression is. However, the formula must still '''equal the target at level 100.'''

[[Category:Plugins]]

ExcellentJobs

2025-11-21T04:39:49Z

Technofied: Basic rundown of ExcellentJobs

This is the plugin we use to control levelling up and rewards for the following jobs listed below.
{| class="wikitable"
|+Available Jobs
!Name
!Maximum Level Attainable
|-
|Farmer
|100
|-
|Fisher
|100
|-
|Hunter
|100
|-
|Lumberjack
|100
|}

== Levelling ==
The maximum level is simply an integer (number) that is assigned to each job. It can be increased or decreased as such.

== Income ==
The maximum amount of income a player can earn is dependent on the '''level''' of the job they have.

* As such, you '''cannot set a maximum amount of earned income for all levels.'''

Each job’s income is determined by four options:
{| class="wikitable"
!Option
!Meaning
|-
|<code>Base</code>
|Starting amount (paid regardless of level).
|-
|<code>Per_Level</code>
|Amount added (or multiplied) per step of levels.
|-
|<code>Step</code>
|How often the increment is applied (in levels).
|-
|<code>Action</code>
|Whether <code>Per_Level</code> is added to or multiplies the base.
|}
The formula applied is:<syntaxhighlight>
steps = floor(jobLevel / Step)
floor() means the number inside the brackets is rounded DOWN

If Action is ADD
perLevel = steps * Per_Level result = (Base + perLevel)

If Action is MULTIPLY
result = (Base * perLevel)
</syntaxhighlight>'''Remember, there is no clamp or hard limit built into this formula.'''

To hit a maximum payout (e.g. $1,500 at level 100), you must design the formula so the values '''reach that amount''' at the '''highest possible level.'''

== Example (ADD Action) ==
<syntaxhighlight lang="yaml" line="1">
Currency:
money:
Base: 0
Per_Level: 15
Step: 1
Action: ADD
</syntaxhighlight>At level 100:

<code>steps = 100 / 1 = 100</code>

<code>income = 0 + (100 × 15) = $1,500</code>

== Adjusting the Rate of Increase ==
If income grows too quickly, increase the <code>Step</code> value.
{| class="wikitable"
!Step
!Per_Level
!Max (Level 100)
|-
|1
|15
|$1,500
|-
|5
|75
|$1,500
|-
|10
|150
|$1,500
|}
The higher the step, the slower the progression is. However, the formula must still '''equal the target at level 100.'''

[[Category:Plugins]]