https://wiki.democracycraft.net/api.php?action=feedcontributions&feedformat=atom&user=Goldendude15DemocracyCraft Wiki - User contributions [en-gb]2026-04-12T16:06:14ZUser contributionsMediaWiki 1.43.1https://wiki.democracycraft.net/index.php?title=Armourer&diff=9525Armourer2026-04-11T10:52:57Z<p>Goldendude15: Adjusted the page to include relevant information pertaining to current firearms license legislation.</p>
<hr />
<div>{{Jobs}}<br />
<br />
As an Armourer, you are responsible for contributing to the server’s arms-based industry. This is achieved by crafting weapons and armour to sell to the community. In general, anyone with a valid firearms license can own a firearm as long as it's not a WMD (Weapon of Mass Destruction, e.g. a Fatman or Mininuke).<br />
<br />
If crafting weaponry is your forte, while of course staying legal, then we recommend this job for you!<br />
<br />
[[File:Yeet Boy with a Firearm.png|462x462px|image]]<br />
<br />
== What Armourers Do ==<br />
<br />
Armourers on DemocracyCraft have several essential roles:<br />
<br />
* '''Crafting Weapons:''' Your primary task is crafting various weapons that are legal on the server. Recipe books containing the recipes for all the guns and ammo can be found in the government store.<br />
* '''Selling Firearms:''' You can sell firearms in a chest shop. Utilize the <code>/iteminfo</code> command to obtain the name for the chest shop, making it easier for players to find your products. Alternatively, you can make the final line on the chest shop a '''?''', which you can right click with your held item to register.<br />
* '''Understanding Firearms Laws (essential):''' To ensure you abide the law you must familiarize yourself with the server’s laws regarding firearms, particularly the [https://www.democracycraft.net/threads/firearms-licensing-act.34448/ Firearms Licensing Act]. This law requires players to have a firearms license in order to possess, purchase, operate, distribute, or craft any firearms — if you do so without a license you may be breaking the law and be subject to heavy penalties! To obtain a license head to the Reveille Police station <code>/gps police</code> to submit an application. <br />
* '''Crafting Ammo:''' In addition to weapons, crafting ammunition is a part of your job. Ensure you have the knowledge and materials to craft various types of ammo.<br />
<br />
== Crafting ==<br />
<br />
To craft a firearm yourself, you need to place materials in the right shape in a crafting table. Recipe books containing the recipes for all the guns and ammo you can make can be found on the second floor of the government store, which can be found in the town hall. Find the town hall by following the arrow after running the command <code>/gps start govshop</code>. Or, you can find recipes through the <code>/recipes</code> command, under the Weaponry tab.<br />
<br />
To gather resources for crafting, you can either buy them from other player shops ''or'' obtain them yourself in the [[The Wild|wild]]. Buying from other players is more expensive, but it's less time-consuming.<br />
<br />
==== Recipe Examples ====<br />
<br />
'''Combat knife''': 1 iron sword and 2 iron ingots<br />
<br />
'''M16''': 5 redstone dust, 3 iron blocks<br />
<br />
'''5.56 NATO''': 1 iron ingot, 1 redstone dust, 1 gunpowder<br />
<br />
== Making Money ==<br />
<br />
There are a few different ways to start earning money with your new profession (don't forget that you need a firearms license to legally sell firearms):<br />
<br />
* Purchase or rent a shop to sell your products. You can find available plots for sale/lease under #realty-adverts on our Discord server. For more information on how to set up a chest shop, check out the [https://wiki.democracycraft.net/features/chestshops/ Chest Shops Guide].<br />
* Use the #marketplace channel in Discord to auction off your goods. You get to choose the starting price, and interested players can bid higher on your auctions.<br />
* If you don't want to do all of the business on your own, you can join a player-owned company to work for with the Discord #employment channel: [https://discord.gg/democracy DC Employment]<span id="recipes"></span><br />
[[Category:Professions]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Everything_Senior_Vice_Presidents_(SVPs)&diff=8570Everything Senior Vice Presidents (SVPs)2026-01-20T11:39:31Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
== Elections ==<br />
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!<br />
<br />
=== SVP Election Months ===<br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November<br />
<br />
== SVP Morale ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions<br />
<br />
== SVP Talent (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening.<br />
<br />
== SVP Justice (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* 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<br />
* 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).<br />
<br />
== SVP Retention (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)).<br />
<br />
== SVP History ==<br />
As SVP History, you are the owner/curator of the Staff/Server museum. Go to /gps staff-museum to have a look!<br />
<br />
=== Responsibilities ===<br />
<br />
* Keep the Staff/Server museum up-to-date, /gps staff-museum. This includes adding new signs in the staff museum as new staff arrive and keeping current signs up-to-date!<br />
* Keep the spawn current staff pillars up-to-date<br />
* Keep the advent museum up to date during the Christmas season, /gps advent-museum<br />
<br />
{{Staff}}<br />
[[Category:Staff]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Client_Modifications&diff=8565Client Modifications2026-01-20T01:12:23Z<p>Goldendude15: Added Stendhal mod.</p>
<hr />
<div><span id="client-modifications"></span><br />
<br />
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.'''<br />
<br />
<span id="resourcepacks"></span><br />
== Resource Packs (Texture Packs) ==<br />
<br />
Resource Packs are used to change the appearance of the game.<br />
<br />
<span id="prohibited-resourcepacks"></span><br />
=== Prohibited Resource Packs ===<br />
Any pack which may give a player a tangible and material '''unfair advantage''', these include:<br />
* X-Ray packs <br />
** These give a player the ability to see through non-transparent blocks<br />
* Full Bright packs<br />
<br />
{{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!}}<br />
<br />
== Modifications ==<br />
<br />
Below are the lists of approved modifications for Fabric and Forge respectively.<br />
<br />
* Cosmetic mods and performance enhancing mods are not included in these lists as they aren’t typically problematic<br />
* Any supporting/dependency mods for the below listed mods are also permitted<br />
<br />
'''Fabric Mods'''<br />
<br />
* AppleSkin - https://www.curseforge.com/minecraft/mc-mods/appleskin<br />
* Inventory HUD+ - https://www.curseforge.com/minecraft/mc-mods/inventory-hud-forge<br />
* Inventory Tweak - https://modrinth.com/mod/inventorytweak<br />
* Jade - https://www.curseforge.com/minecraft/mc-mods/jade<br />
* Litematica - https://www.curseforge.com/minecraft/mc-mods/litematica<br />
* MiniHUD - https://www.curseforge.com/minecraft/mc-mods/minihud<br />
* Mod Menu - https://www.curseforge.com/minecraft/mc-mods/modmenu<br />
* More Overlays Updated - https://www.curseforge.com/minecraft/mc-mods/more-overlays-updated<br />
* Roughly Enough Items - https://www.curseforge.com/minecraft/mc-mods/roughly-enough-items<br />
* ShulkerBoxTooltip - https://www.curseforge.com/minecraft/mc-mods/shulkerboxtooltip<br />
* Stendhal - https://modrinth.com/mod/stendhal<br />
* Status Effect Timer - https://www.curseforge.com/minecraft/mc-mods/status-effect-timer<br />
* Xaero’s Minimap (Fair-Play Edition) - https://www.curseforge.com/minecraft/mc-mods/xaeros-minimap-fair-play-edition<br />
* Xaero’s World Map - https://www.curseforge.com/minecraft/mc-mods/xaeros-world-map<br />
<br />
'''Forge Mods'''<br />
<br />
* AppleSkin - https://www.curseforge.com/minecraft/mc-mods/appleskin<br />
* Inventory HUD+ - https://www.curseforge.com/minecraft/mc-mods/inventory-hud-forge<br />
* Inventory Tweak - https://www.curseforge.com/minecraft/mc-mods/inventory-sorter<br />
* Jade - https://www.curseforge.com/minecraft/mc-mods/jade<br />
* More Overlays Updated - https://www.curseforge.com/minecraft/mc-mods/more-overlays-updated<br />
* Roughly Enough Items - https://www.curseforge.com/minecraft/mc-mods/roughly-enough-items<br />
* Shulker Tooltip - https://www.curseforge.com/minecraft/mc-mods/shulker-tooltip<br />
* Xaero’s Minimap (Fair-Play Edition) - https://www.curseforge.com/minecraft/mc-mods/xaeros-minimap-fair-play-edition<br />
* Xaero’s World Map - https://www.curseforge.com/minecraft/mc-mods/xaeros-world-map<br />
<br />
'''Other Allowed Mods'''<br />
<br />
* Vivecraft - https://www.vivecraft.org/<br />
* Questcraft - https://sidequestvr.com/app/7150/questcraft<br />
<br />
<br />
'''Cinematic Recording and Replay Mods'''<br />
<br />
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.<br />
<br />
* 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<br />
{{Note<br />
| type = warn<br />
| text = Staff are consistently monitoring gameplay to ensure compliance with the rules. Violating the rules could result in '''disciplinary action!'''<br />
}}<br />
<br />
== Mod Packs ==<br />
<br />
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.<br />
<br />
'''Fabric Packs'''<br />
<br />
* Fabulously Optimized - https://www.curseforge.com/minecraft/modpacks/fabulously-optimized<br />
* Performance+ - https://www.curseforge.com/minecraft/modpacks/performance<br />
* Performance+ Extended - https://www.curseforge.com/minecraft/modpacks/performance-extended<br />
<br />
'''Forge''' <br />
<br />
None currently approved.<br />
<br />
{{Note|type=info|text=Have a suggestion? Head to #suggestions on the {{DCDiscord|DemocracyCraft Discord}} to give us a recommendation! }}<br />
<br />
{{Staff}}<br />
[[Category:Staff]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=8320Staff Guide2026-01-05T21:31:45Z<p>Goldendude15: Added rental duration policy.</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
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. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code> <br />
** 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.<br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <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!)<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br /><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Everything_Senior_Vice_Presidents_(SVPs)&diff=8319Everything Senior Vice Presidents (SVPs)2026-01-05T21:30:02Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
== Elections ==<br />
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!<br />
<br />
=== SVP Election Months ===<br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November<br />
<br />
== SVP Morale ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions<br />
<br />
== SVP Talent (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening.<br />
<br />
== SVP Justice (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command.<br />
<br />
== SVP Retention (Administrators+) ==<br />
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.<br />
<br />
=== Responsibilities ===<br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)).<br />
<br />
== SVP History ==<br />
As SVP History, you are the owner/curator of the Staff/Server museum. Go to /gps staff-museum to have a look!<br />
<br />
=== Responsibilities ===<br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
[[Category:Staff]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=8175Staff Guide2026-01-01T09:28:58Z<p>Goldendude15: Added disease cure command.</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
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. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <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!)<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Command:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Use this command to cure any diseases you have!<br />
<br />
* This is ''only'' to be used for staff duties, e.g. getting ill during a ticket - usage is logged!<br />
* '''Command:''' <code>/staff-disease-cure</code><br />
<br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=8174Staff Guide2026-01-01T09:25:26Z<p>Goldendude15: Added disease cure command.</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
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. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <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!)<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code>Use this to cure yourself of any diseases you have!.<br />
* This can ''only'' be used during staff duties, e.g. a ticket - usage is logged! <br />
* '''Commands:''' <code>/staff-disease-cure <reason></code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7664Staff Guide2025-12-13T10:57:03Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
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. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <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!)<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7583Staff Guide2025-12-08T10:36:52Z<p>Goldendude15: Clarification of plot types to be merged; more specific.</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
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. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <code>/deleteclaim</code> (Use this to delete the claim your standing on even if you're not the owner - be careful!<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Plots_and_regions&diff=7278Plots and regions2025-10-26T03:55:22Z<p>Goldendude15: </p>
<hr />
<div><span id="plots-regions"></span><br />
<br />
DemocracyCraft utilises Areashop (AS) for region management. <span id="wild-region"></span><br />
== Wild region ==<br />
<br />
Players can build freely in the wilderness, but some may desire protection for their bases. You can claim one region with a maximum of 4096 blocks for $10 per block. To claim a wild region follow the instructions contained within [[Wilderness Claiming]]. <br />
== Urban regions ==<br />
<br />
There are three main types of plots within Redmont: <br />
# Commercial – Identified by the c- or cbd- tags. Only commercial buildings like stores and apartments are allowed on these plots.<br />
# Residential – Marked with the r- tag. Only houses with up to three visible floors can be built on residential plots.<br />
# Skyscraper – Denoted by the s- tag. Skyscraper plots can only have skyscrapers and are not meant for industrial or residential use.<br />
<br />
To find available plots in the city, look for reselling properties with the corresponding tags (e.g., c-000). Use <code>/as info reselling</code> to locate resold plots and use <code>/gps start [plot]</code> to get to that location.<span id="rental-regions"></span><br />
== Rental regions ==<br />
<br />
There are four main types of rental regions on the server: <br />
# Farm plot – Located in the farming town [[Willow]], these special farm regions can be rented by players (up to two per person). Denoted by the f- tag, they can be rented from the Willow Train Station. <br />
# Apartment – Some commercial buildings offer rentable apartments with prices based on the number of days. These real-life durations provide an affordable option for new players seeking a city residence.<br />
# Shop/market stall – Rentable stores are available in some regions, such as Vestire Mall, allowing players to sell items without purchasing an entire plot.<br />
# Shulker regions – Certain city and town locations have free or low-cost shulker regions with rental durations of 1-10 minutes. Intended for temporary use, such as accessing a shulker box or ender chest.<br />
<br />
You may also encounter other, less popular rental regions. To check information about a rental region, use <code>/as info region --region [rental region name]</code>.<br />
== Property regulations ==<br />
<br />
Upon purchasing or renting a property, you must adhere to specific regulations and laws. For owned plots, the Department of Construction and Transport (DCT) may issue eviction reports for building violations. Meanwhile, landlords may evict tenants who breach their rental agreements.<br />
<br />
For further details, consult the [https://www.democracycraft.net/threads/property-standards-act.13387/ Property Standards] and the [https://www.democracycraft.net/threads/evictions-policy.26813/ Eviction Policy].<br />
<br />
<span id="commands"></span><br />
<br />
== Commands ==<br />
<br />
* /as help – Shows this help page<br />
* /as rent – Rent a region or extend your current rent<br />
* /as unrent – Unrent a region<br />
* /as buy – Buy a region<br />
* /as sell – Sell a region<br />
* /as me – Check which regions you have and their expiration dates<br />
* /as info – Get info about current regions<br />
* /as info forsale – Regions currently for sale from the Government<br />
* /as info reselling – Regions currently for sale from other players<br />
* /as info region (region name) – Information about a particular region<br />
* /as addfriend – Grant someone building permissions<br />
* /as delfriend – Delete a friend from a region<br />
* /as resell – Put a region into resell mode<br />
* /as stopresell – Put a region back into sold mode<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Security_Cameras&diff=7277Security Cameras2025-10-26T03:53:32Z<p>Goldendude15: Specified how plugin isn;t enabled</p>
<hr />
<div><span id="security-cameras"></span><br />
<br />
Do you need to keep an eye on your valuables or watch out for unwelcome visitors? These simple steps will help you get started! '''NOTE: This plugin is currently NOT enabled hence recipes will not work'''<br />
<br />
<div class="figure"><br />
<br />
[[File:security_camera.png|thumb|A security camera mounted to the wall]]<br />
<br />
</div><br />
<span id="crafting-the-cameras-and-computers"></span><br />
== Crafting the Cameras and Computers ==<br />
<br />
To begin, follow the recipe below to craft both a camera and computer.<br />
<br />
<div class="figure"><br />
<br />
[[File:Security camera craft.png|400px]]<br />
<br />
</div><br />
<span id="linking-cameras"></span><br />
== Linking Cameras ==<br />
<br />
# Create a group for your cameras with this command: <code>/cctv group create &lt;name&gt;</code><br />
# After creating the group, add cameras to it using: <code>/cctv group addcamera &lt;groupName&gt; &lt;cameraName&gt;</code><br />
<br />
The <code>&lt;cameraName&gt;</code> is visible when you right-click the placed camera to open the Camera GUI.<br />
<br />
<div class="figure"><br />
<br />
[[File:Security camera linking.png|400px]]<br />
<br />
</div><br />
<span id="setting-up-computers"></span><br />
== Setting Up Computers ==<br />
<br />
Computers are your tools for accessing the cameras. You can craft them by following the recipe provided.<br />
<br />
<div class="figure"><br />
<br />
[[File:Security computer.png|400px]]<br />
<br />
</div><br />
Once you’ve placed a computer, right click it and you’ll see a menu with options:<br />
<br />
<div class="figure"><br />
<br />
[[File:security_pc_options.png|400px]]<br />
<br />
</div><br />
* '''Ender Chest:''' “Computer Access” - Add or remove players (left-click) or toggle between private and public access (shift left-click).<br />
* '''Chest:''' “Add camera group” - Select the camera group for the computer.<br />
* '''Camera:''' “Add Cameras” - Add new cameras to the group selected for the computer.<br />
<br />
<span id="viewing-cameras"></span><br />
<br />
== Viewing Cameras ==<br />
<br />
Now that you’ve set up your cameras, camera group, and computers, you can easily manage them from the main dashboard of the GUI, which will display all cameras belonging to the camera group.<br />
<br />
<div class="figure"><br />
<br />
[[File:Security viewing cameras.png|400px]]<br />
<br />
</div><br />
''Note: To remove items, use ‘Drop to remove’ by pressing Q or the Drop button while hovering over the item.''<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Main_Page&diff=7276Main Page2025-10-26T03:34:33Z<p>Goldendude15: Smol edit for clarity</p>
<hr />
<div>= <p style="text-align: center;"> Welcome to DemocracyCraft! </p> =<br />
DemocracyCraft, or DC, is a City Roleplay server focused on the player's ability to create, amend, and remove the rules and laws that govern them. Our server boasts cars, helicopters, a democratically elected government, businesses, economy, among other realistic, life-like features! <br />
<br />
----<br />
<br />
=== Joining the Server ===<br />
Currently, the server is running on <code>{{DCVersion}}</code>.<br />
<br />
You can join the server on both Java Edition & Bedrock Edition using these IPs:<br />
* '''Java Edition''': play.democracycraft.net <br />
* '''Bedrock Edition''': play.democracycraft.net:19132<br />
----<br />
<br />
= Getting Started! =<br />
<br />
Once you join the server, if a guide is online, they will come to you and give you a tour. If there are no guides online, feel free to ask in chat when you see one join, or open a Department of Education ticket on the {{code|#support}} channel in the Discord server. A link can be found here: {{DCDiscord}}<br />
=== Need help? ===<br />
Our staff team is a group of amazing people who are here to help you. Should you have any issues, please run {{code|/ticket}} while you are in-game and follow the prompts.<br />
<br />
If there are no staff members online, you can go to the {{code|#support}} Discord channel and create a ticket. A staff member will reply as soon as they can. <br />
== Forums & Discord ==<br />
[[File:Reveillepolicestation.png|thumb|600px]]<br />
The Discord server and our forums are the two main places where announcements are posted. You can find the Discord [//discord.gg/democracy here] and you can find the forums [//democracycraft.net here].<br />
<br />
You can apply for government jobs, view our constitution, and do much more on the forums. To fully view the forums you need to create an account. <br />
* Link your account from in-game with <code>/link-forums</code>!<br />
<br />
On the Discord server, you can get into contact with government departments, make staff tickets, talk to players, and more!<br />
* Link your account from in-game with <code>/link-discord</code>!<br />
<br />
{{Note|type=error|text=These platforms come '''highly recommended'''!<br />
<br /> A lot of our server interacts and relies on Discord and Forums. All of our platforms are moderated by our Staff team. <br />
}}<br />
<br />
{{Note|type=reminder|text=Good job on making it this far!<br />
<br />
Most people who don't read this far have a hard time understanding the server. :(}}<br />
<br />
----<br />
<br />
=== Making money ===<br />
On joining the server, you start off with $1200. While that's no small sum, you will find you might need more money to buy plots, groceries or rent your first apartment. Here are some suggestions on how to make money:<br />
<br />
* Getting hired by a company<br />
* Selling materials to player-owned chestshops<br />
* Starting a business<br />
* Real estate opportunities<br />
* Auctions<br />
<br />
[[Money|You can learn more about making money by reading our guide on it!]]<br />
<br />
=== Chestshops ===<br />
[[Chestshops]] are where you can buy or sell materials from or to players and firms. To buy an item, right click on the sign. To sell an item, left click on the sign. You can shift click to buy or sell an entire stack!<br />
<br />
To find chest shops for an item you need, run the command <code>/find (item)</code>!<br />
<br />
[[Chestshops|You can learn more about creating chest shops by reading our guide.]]<br />
<br />
=== Jobs and exams ===<br />
One of the first things you should do is get your first job! You can do this by going to our [[University]] by entering {{code|/university}} in game. <br />
<br />
We have '''three''' main categories of jobs:<br />
<br />
# '''Trade''' - these are considered manual labour jobs with not many special perks.<br />
#* They are good for beginners who want an easier starting off point. Many allow you to gather resources easier to sell or to craft into other items.<br />
#'''Professions''' - these jobs build on trade jobs by having more advanced or special perks.<br />
#* This could be specialised crafting recipes or plugin features. <br />
#'''Government''' - you cannot get a government job immediately, but after around 24 hours of in-game playtime a lot of players apply for these jobs on [//democracycraft.net our forums.]<br />
#* Government jobs will provide wages, and many also have additional commission based pay.<br />
<br />
At any given time, you can have two trade jobs, one profession, and unlimited government jobs!<br />
<br />
For more detailed information, check out individual [[:Category:Jobs|job guides]] that interest you!<br />
<br />
----<br />
<br />
=== Chat ===<br />
Our server is unique, as there are three chat channels you use to talk to other players. Please <b>read this carefully</b> as you will need to use these channels quite often!<br />
<br />
* '''Global (<code>/g</code>)''' - this is the default channel for everyone. You only need to run the alias command when you aren't in the channel. This channel allows <b>everyone</b> to read your messages.<br />
* '''Local (<code>/l</code>)''' - this is a channel with a 50 block radius. Only people within 50 blocks can read your messages (hear you!). Please use this when you are: talking to players right in front of you, seeking treatment from a Doctor, or in an event.<br />
* '''Murmur (<code>/murmur</code>) -''' This channel has a 5 block radius, for more secretive chats in-game!<br />
* '''Private Messages (<code>/msg <username></code>)''' - this allows you to have a one on one conversation with anyone. Replace <code><username></code> with whomever you want to talk to!<br />
<br />
<br />
In addition to these channel commands, you may want to learn some other handy commands. We recommend you visit [[Useful commands| this guide]] sometime after you finish this one!<br />
<br />
----<br />
[[File:Deadwax_and_derpy_at_hospital.png|500px|thumb]]<br />
=== Health ===<br />
<br />
<br />
On this server, we have a custom health plugin which enables players to experience sickness and injuries. You will most likely experience broken legs and flesh wounds, both will give you slowness and/or random damage. Monitor your health status at any time by entering {{code|/health symptoms}} in-game!<br />
<br />
If you fall ill, head to the Hospital and click the computer head to request a doctor. You can get to the hospital by dying (not recommended!) or by entering {{code|/gps start hospital}} in-game.<br />
<br />
<br />
{{Note |text=<b>Medicare</b><br />
<br>All of your health expenses will be covered by Medicare - a free universal healthcare program!|type=reminder}}<br />
<br />
----<br />
<br />
[[file:will_you_be_our_next_president.png|400px|thumb]]<br />
<br />
=== Government ===<br />
Our government consists of three branches: legislative, executive, and [[Judiciary|judicial]].<br />
<br />
The legislative branch, or [[Congress]], is split into two parts: the [[House of Representatives]] (HoR) and the [[Senate]]. Representatives in the HoR are responsible for creating and voting on legislation, while Senators review and vote on proposed bills from the HoR.<br />
<br />
The executive branch comprises the [[president]], [[vice president]], and the [[Cabinet]]. The [[president]] and [[vice president]] are elected <b>democratically by the players</b> every four months, leading the government as a whole! This is the same electoral system we use to elect our legislative branch. The Cabinet consists of advisors who oversee various government departments.<br />
<br />
The [[Judiciary|judicial branch]] runs the court system. Citizens have the right to bring legal disputes against each other, with judges presiding over cases and determining appropriate punishments based on {{DCForums|Link=/threads/constitution.6/#post-6|Forums=our constitution}}.<br />
<br />
Apart from judges and Cabinet members, who require presidential nomination and [[Senate]] approval, anyone can run for a government position. To participate in an election, simply join the race in our {{DCForums|Link=/forums/elections-referendums.27|Forums=Election and Referendums forum}}<br />
<br />
----<br />
<br />
== Worlds ==<br />
<br />
We have a mixture of creative, survival, wilderness, and urban worlds! Here's a breakdown of what you can expect from each:<br />
<br />
=== Wilderness ===<br />
<br />
* Keep Inventory: ON<br />
* Plot Claiming: ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: SOME APPLY (See https://www.democracycraft.net/threads/wilderness-laws-clarification-3-0-act.20744/)<br />
* Resets: NEVER<br />
<br />
The [[Wild|Wilderness]] is a naturally generated world where players can explore, gather resources, build bases, and engage in various unregulated activities. In this world, you are free to roam and create, but keep in mind that some laws still apply.<br />
<br />
Use the command <code>/airport</code>, then right-click on one of the nearby computer monitors to open a menu, where you can select your wilderness destination. <br />
<br />
{{Note<br />
| text = <b>Plot claiming</b><br />
<br>There are limited laws in the wild, protect your belongings by creating a claim for $10/block and by /locking your containers. See https://wiki.democracycraft.net/Wilderness_Claiming<br />
| type = error<br />
}}<br />
<br />
=== Everwild, End, and Nether ===<br />
<br />
* Keep Inventory: OFF<br />
* Plot Claiming: NOT ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: LAWLESS<br />
* Resets: REGULARLY<br />
<br />
The Everwild, End, and Nether are treacherous and lawless realms, with no governing laws to guide your actions. These dangerous worlds are perfect for players looking for high-risk adventures, where survival is up to your skill and luck. <br />
<br />
To reach the Everwild, use <code>/airport</code> and interact with a computer monitor to get your ticket. The End and Nether can be accessed through the Wilderness or Everwild worlds. <br />
<br />
{{Note|text=<b>Protect your items!</b><br />
<br>Keep Inventory is OFF in the End, Nether, and Everwild. When you die, you will drop all of your inventory.|type=warn}}<br />
<br />
=== Property, plots and apartments ===<br />
<br />
Players have the opportunity to rent and own various properties both in the city and the wilderness. These plots are technically referred to as "regions". If you own a plot in the city, you are able to build anything on it as long as it meets {{DCForums|Link=/threads/evictions-policy.26813/|Forums=government regulations}}. Most new players don't start off with plots, you will usually need to save up a lot of money first.<br />
<br />
[[file:reveille_city.png|thumb|600px]]<br />
<br />
To see plots for sale, run the commands <code>/as info forsale</code> and <code>/as info reselling</code>. On the Discord, eviction auctions are hosted periodically, and many plots go for sale there as well. <br />
<br />
For new players, we recommend that you wander inside large skyscrapers/apartment buildings for an apartment or rental shop instead. You can right click signs that say "[For Rent]" to rent your first apartment!<br />
<br />
You can check properties you own or rent using <code>/as me</code>. To see information on a region, use the command <code>/as info region --region (region name) </code><br />
<br />
<br />
=== Businesses ===<br />
[[file:sausage_sizzle_stands.png|thumb|600px]]<br />
<br />
You will often see [[chestshops]] and plots that are branded or owned by businesses. Chestshops will often have <code>b:<company name></code> and plots will have company logos on them. You are able to start your own business by getting an entrepreneur license from our University.<br />
<br />
<br />
<br />
== That's all! ==<br />
Great job on making it this far! We're excited to have you! Feel free to ask questions in-game, and if you haven't already, be sure to join our {{DCDiscord}}</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Main_Page&diff=7275Main Page2025-10-26T03:32:16Z<p>Goldendude15: </p>
<hr />
<div>= <p style="text-align: center;"> Welcome to DemocracyCraft! </p> =<br />
DemocracyCraft, or DC, is a City Roleplay server focused on the player's ability to create, amend, and remove the rules and laws that govern them. Our server boasts cars, helicopters, a democratically elected government, businesses, economy, among other realistic, life-like features! <br />
<br />
----<br />
<br />
=== Joining the Server ===<br />
Currently, the server is running on <code>{{DCVersion}}</code>.<br />
<br />
You can join the server on both Java Edition & Bedrock Edition using these IPs:<br />
* '''Java Edition''': play.democracycraft.net <br />
* '''Bedrock Edition''': play.democracycraft.net:19132<br />
----<br />
<br />
= Getting Started! =<br />
<br />
Once you join the server, if a guide is online, they will come to you and give you a tour. If there are no guides online, feel free to ask in chat when you see one join, or open a Department of Education ticket on the {{code|#support}} channel in the Discord server. A link can be found here: {{DCDiscord}}<br />
=== Need help? ===<br />
Our staff team is a group of amazing people who are here to help you. Should you have any issues, please run {{code|/ticket}} while you are in-game and follow the prompts.<br />
<br />
If there are no staff members online, you can go to the {{code|#support}} Discord channel and create a ticket. A staff member will reply as soon as they can. <br />
== Forums & Discord ==<br />
[[File:Reveillepolicestation.png|thumb|600px]]<br />
The Discord server and our forums are the two main places where announcements are posted. You can find the Discord [//discord.gg/democracy here] and you can find the forums [//democracycraft.net here].<br />
<br />
You can apply for government jobs, view our constitution, and do much more on the forums. To fully view the forums you need to create an account. <br />
* Link your account from in-game with <code>/link-forums</code>!<br />
<br />
On the Discord server, you can get into contact with government departments, make staff tickets, talk to players, and more!<br />
* Link your account from in-game with <code>/link-discord</code>!<br />
<br />
{{Note|type=error|text=These platforms come '''highly recommended'''!<br />
<br /> A lot of our server interacts and relies on Discord and Forums. All of our platforms are moderated by our Staff team. <br />
}}<br />
<br />
{{Note|type=reminder|text=Good job on making it this far!<br />
<br />
Most people who don't read this far have a hard time understanding the server. :(}}<br />
<br />
----<br />
<br />
=== Making money ===<br />
On joining the server, you start off with $1200. While that's no small sum, you will find you might need more money to buy plots, groceries or rent your first apartment. Here are some suggestions on how to make money:<br />
<br />
* Getting hired by a company<br />
* Selling materials to player-owned chestshops<br />
* Starting a business<br />
* Real estate opportunities<br />
* Auctions<br />
<br />
[[Money|You can learn more about making money by reading our guide on it!]]<br />
<br />
=== Chestshops ===<br />
[[Chestshops]] are where you can buy or sell materials from or to players and firms. To buy an item, right click on the sign. To sell an item, left click on the sign. You can shift click to buy or sell an entire stack!<br />
<br />
To find chest shops for an item you need, run the command <code>/find (item)</code>!<br />
<br />
[[Chestshops|You can learn more about creating chest shops by reading our guide.]]<br />
<br />
=== Jobs and exams ===<br />
One of the first things you should do is get your first job! You can do this by going to our [[University]] by entering {{code|/university}} in game. <br />
<br />
We have '''three''' main categories of jobs:<br />
<br />
# '''Trade''' - these are considered manual labour jobs with not many special perks.<br />
#* They are good for beginners who want an easier starting off point. Many allow you to gather resources easier to sell or to craft into other items.<br />
#'''Professions''' - these jobs build on trade jobs by having more advanced or special perks.<br />
#* This could be specialised crafting recipes or plugin features. <br />
#'''Government''' - you cannot get a government job immediately, but after around 24 hours of in-game playtime a lot of players apply for these jobs on [//democracycraft.net our forums.]<br />
#* Government jobs will provide wages, and many also have additional commission based pay.<br />
<br />
At any given time, you can have two trade jobs, one profession, and unlimited government jobs!<br />
<br />
For more detailed information, check out individual [[:Category:Jobs|job guides]] that interest you!<br />
<br />
----<br />
<br />
=== Chat ===<br />
Our server is unique, as there are three chat channels you use to talk to other players. Please <b>read this carefully</b> as you will need to use these channels quite often!<br />
<br />
* '''Global (<code>/g</code>)''' - this is the default channel for everyone. You only need to run the alias command when you aren't in the channel. This channel allows <b>everyone</b> to read your messages.<br />
* '''Local (<code>/l</code>)''' - this is a channel with a 50 block radius. Only people within 50 blocks can read your messages (hear you!). Please use this when you are: talking to players right in front of you, seeking treatment from a Doctor, or in an event.<br />
* '''Murmur (<code>/murmur</code>) -''' This channel has a 5 block radius, for more secretive chats in-game!<br />
* '''Private Messages (<code>/msg <username></code>)''' - this allows you to have a one on one conversation with anyone. Replace <code><username></code> with whomever you want to talk to!<br />
<br />
<br />
In addition to these channel commands, you may want to learn some other handy commands. We recommend you visit [[Useful commands| this guide]] sometime after you finish this one!<br />
<br />
----<br />
[[File:Deadwax_and_derpy_at_hospital.png|500px|thumb]]<br />
=== Health ===<br />
<br />
<br />
On this server, we have a custom health plugin which enables players to experience sickness and injuries. You will most likely experience broken legs and flesh wounds, both will give you slowness and/or random damage. Monitor your health status at any time by entering {{code|/health symptoms}} in-game!<br />
<br />
If you fall ill, head to the Hospital and click the computer head to request a doctor. You can get to the hospital by dying (not recommended!) or by entering {{code|/gps start hospital}} in-game.<br />
<br />
<br />
{{Note |text=<b>Medicare</b><br />
<br>All of your health expenses will be covered by Medicare - a free universal healthcare program!|type=reminder}}<br />
<br />
----<br />
<br />
[[file:will_you_be_our_next_president.png|400px|thumb]]<br />
<br />
=== Government ===<br />
Our government consists of three branches: legislative, executive, and [[Judiciary|judicial]].<br />
<br />
The legislative branch, or [[Congress]], is split into two parts: the [[House of Representatives]] (HoR) and the [[Senate]]. Representatives in the HoR are responsible for creating and voting on legislation, while Senators review and vote on proposed bills from the HoR.<br />
<br />
The executive branch comprises the [[president]], [[vice president]], and the [[Cabinet]]. The [[president]] and [[vice president]] are elected <b>democratically by the players</b> every four months, leading the government as a whole! This is the same electoral system we use to elect our legislative branch. The Cabinet consists of advisors who oversee various government departments.<br />
<br />
The [[Judiciary|judicial branch]] runs the court system. Citizens have the right to bring legal disputes against each other, with judges presiding over cases and determining appropriate punishments based on {{DCForums|Link=/threads/constitution.6/#post-6|Forums=our constitution}}.<br />
<br />
Apart from judges and Cabinet members, who require presidential nomination and [[Senate]] approval, anyone can run for a government position. To participate in an election, simply join the race in our {{DCForums|Link=/forums/elections-referendums.27|Forums=Election and Referendums forum}}<br />
<br />
----<br />
<br />
== Worlds ==<br />
<br />
We have a mixture of creative, survival, wilderness, and urban worlds! Here's a breakdown of what you can expect from each:<br />
<br />
=== Wilderness ===<br />
<br />
* Keep Inventory: ON<br />
* Plot Claiming: ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: SOME APPLY (See https://www.democracycraft.net/threads/wilderness-laws-clarification-3-0-act.20744/)<br />
* Resets: NEVER<br />
<br />
The [[Wild|Wilderness]] is a naturally generated world where players can explore, gather resources, build bases, and engage in various unregulated activities. In this world, you are free to roam and create, but keep in mind that some laws still apply.<br />
<br />
Use the command <code>/airport</code>, then right-click on one of the nearby computer monitors to open a menu, where you can select your wilderness destination. <br />
<br />
{{Note<br />
| text = <b>Plot claiming</b><br />
<br>There are limited laws in the wild, protect your belongings by creating a claim for $10/block and by /locking your containers. See https://wiki.democracycraft.net/Wilderness_Claiming<br />
| type = error<br />
}}<br />
<br />
=== Everwild, End, and Nether ===<br />
<br />
* Keep Inventory: OFF<br />
* Plot Claiming: NOT ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: LAWLESS<br />
* Resets: REGULARLY<br />
<br />
The Everwild, End, and Nether are treacherous and lawless realms, with no governing rules to guide your actions. These dangerous worlds are perfect for players looking for high-risk adventures, where survival is up to your skill and luck. <br />
<br />
To reach the Everwild, use <code>/airport</code> and interact with a computer monitor to get your ticket. The End and Nether can be accessed through the Wilderness or Everwild worlds. <br />
<br />
{{Note|text=<b>Protect your items!</b><br />
<br>Keep Inventory is OFF in the End, Nether, and Everwild. When you die, you will drop all of your inventory.|type=warn}}<br />
<br />
=== Property, plots and apartments ===<br />
<br />
Players have the opportunity to rent and own various properties both in the city and the wilderness. These plots are technically referred to as "regions". If you own a plot in the city, you are able to build anything on it as long as it meets {{DCForums|Link=/threads/evictions-policy.26813/|Forums=government regulations}}. Most new players don't start off with plots, you will usually need to save up a lot of money first.<br />
<br />
[[file:reveille_city.png|thumb|600px]]<br />
<br />
To see plots for sale, run the commands <code>/as info forsale</code> and <code>/as info reselling</code>. On the Discord, eviction auctions are hosted periodically, and many plots go for sale there as well. <br />
<br />
For new players, we recommend that you wander inside large skyscrapers/apartment buildings for an apartment or rental shop instead. You can right click signs that say "[For Rent]" to rent your first apartment!<br />
<br />
You can check properties you own or rent using <code>/as me</code>. To see information on a region, use the command <code>/as info region --region (region name) </code><br />
<br />
<br />
=== Businesses ===<br />
[[file:sausage_sizzle_stands.png|thumb|600px]]<br />
<br />
You will often see [[chestshops]] and plots that are branded or owned by businesses. Chestshops will often have <code>b:<company name></code> and plots will have company logos on them. You are able to start your own business by getting an entrepreneur license from our University.<br />
<br />
<br />
<br />
== That's all! ==<br />
Great job on making it this far! We're excited to have you! Feel free to ask questions in-game, and if you haven't already, be sure to join our {{DCDiscord}}</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Main_Page&diff=7274Main Page2025-10-26T03:29:47Z<p>Goldendude15: </p>
<hr />
<div>= <p style="text-align: center;"> Welcome to DemocracyCraft! </p> =<br />
DemocracyCraft, or DC, is a City Roleplay server focused on the player's ability to create, amend, and remove the rules and laws that govern them. Our server boasts cars, helicopters, a democratically elected government, businesses, economy, among other realistic, life-like features! <br />
<br />
----<br />
<br />
=== Joining the Server ===<br />
Currently, the server is running on <code>{{DCVersion}}</code>.<br />
<br />
You can join the server on both Java Edition & Bedrock Edition using these IPs:<br />
* '''Java Edition''': play.democracycraft.net <br />
* '''Bedrock Edition''': play.democracycraft.net:19132<br />
----<br />
<br />
= Getting Started! =<br />
<br />
Once you join the server, if a guide is online, they will come to you and give you a tour. If there are no guides online, feel free to ask in chat when you see one join, or open a Department of Education ticket on the {{code|#support}} channel in the Discord server. A link can be found here: {{DCDiscord}}<br />
=== Need help? ===<br />
Our staff team is a group of amazing people who are here to help you. Should you have any issues, please run {{code|/ticket}} while you are in-game and follow the prompts.<br />
<br />
If there are no staff members online, you can go to the {{code|#support}} Discord channel and create a ticket. A staff member will reply as soon as they can. <br />
== Forums & Discord ==<br />
[[File:Reveillepolicestation.png|thumb|600px]]<br />
The Discord server and our forums are the two main places where announcements are posted. You can find the Discord [//discord.gg/democracy here] and you can find the forums [//democracycraft.net here].<br />
<br />
You can apply for government jobs, view our constitution, and do much more on the forums. To fully view the forums you need to create an account. <br />
* Link your account from in-game with <code>/link-forums</code>!<br />
<br />
On the Discord server, you can get into contact with government departments, make staff tickets, talk to players, and more!<br />
* Link your account from in-game with <code>/link-discord</code>!<br />
<br />
{{Note|type=error|text=These platforms come '''highly recommended'''!<br />
<br /> A lot of our server interacts and relies on Discord and Forums. All of our platforms are moderated by our Staff team. <br />
}}<br />
<br />
{{Note|type=reminder|text=Good job on making it this far!<br />
<br />
Most people who don't read this far have a hard time understanding the server. :(}}<br />
<br />
----<br />
<br />
=== Making money ===<br />
On joining the server, you start off with $1200. While that's no small sum, you will find you might need more money to buy plots, groceries or rent your first apartment. Here are some suggestions on how to make money:<br />
<br />
* Getting hired by a company<br />
* Selling materials to player-owned chestshops<br />
* Starting a business<br />
* Real estate opportunities<br />
* Auctions<br />
<br />
[[Money|You can learn more about making money by reading our guide on it!]]<br />
<br />
=== Chestshops ===<br />
[[Chestshops]] are where you can buy or sell materials from or to players and firms. To buy an item, right click on the sign. To sell an item, left click on the sign. You can shift click to buy or sell an entire stack!<br />
<br />
To find chest shops for an item you need, run the command <code>/find (item)</code>!<br />
<br />
[[Chestshops|You can learn more about creating chest shops by reading our guide.]]<br />
<br />
=== Jobs and exams ===<br />
One of the first things you should do is get your first job! You can do this by going to our [[University]] by entering {{code|/university}} in game. <br />
<br />
We have '''three''' main categories of jobs:<br />
<br />
# '''Trade''' - these are considered manual labour jobs with not many special perks.<br />
#* They are good for beginners who want an easier starting off point. Many allow you to gather resources easier to sell or to craft into other items.<br />
#'''Professions''' - these jobs build on trade jobs by having more advanced or special perks.<br />
#* This could be specialised crafting recipes or plugin features. <br />
#'''Government''' - you cannot get a government job immediately, but after around 24 hours of in-game playtime a lot of players apply for these jobs on [//democracycraft.net our forums.]<br />
#* Government jobs will provide wages, and many also have additional commission based pay.<br />
<br />
At any given time, you can have two trade jobs, one profession, and unlimited government jobs!<br />
<br />
For more detailed information, check out individual [[:Category:Jobs|job guides]] that interest you!<br />
<br />
----<br />
<br />
=== Chat ===<br />
Our server is unique, as there are three chat channels you use to talk to other players. Please <b>read this carefully</b> as you will need to use these channels quite often!<br />
<br />
* '''Global (<code>/g</code>)''' - this is the default channel for everyone. You only need to run the alias command when you aren't in the channel. This channel allows <b>everyone</b> to read your messages.<br />
* '''Local (<code>/l</code>)''' - this is a channel with a 50 block radius. Only people within 50 blocks can read your messages (hear you!). Please use this when you are: talking to players right in front of you, seeking treatment from a Doctor, or in an event.<br />
* '''Murmur (<code>/murmur</code>) -''' This channel has a 5 block radius, for more secretive chats in-game!<br />
* '''Private Messages (<code>/msg <username></code>)''' - this allows you to have a one on one conversation with anyone. Replace <code><username></code> with whomever you want to talk to!<br />
<br />
<br />
In addition to these channel commands, you may want to learn some other handy commands. We recommend you visit [[Useful commands| this guide]] sometime after you finish this one!<br />
<br />
----<br />
[[File:Deadwax_and_derpy_at_hospital.png|500px|thumb]]<br />
=== Health ===<br />
<br />
<br />
On this server, we have a custom health plugin which enables players to experience sickness and injuries. You will most likely experience broken legs and flesh wounds, both will give you slowness and/or random damage. Monitor your health status at any time by entering {{code|/health symptoms}} in-game!<br />
<br />
If you fall ill, head to the Hospital and click the computer head to request a doctor. You can get to the hospital by dying (not recommended!) or by entering {{code|/gps start hospital}} in-game.<br />
<br />
<br />
{{Note |text=<b>Medicare</b><br />
<br>All of your health expenses will be covered by Medicare - a free universal healthcare program!|type=reminder}}<br />
<br />
----<br />
<br />
[[file:will_you_be_our_next_president.png|400px|thumb]]<br />
<br />
=== Government ===<br />
Our government consists of three branches: legislative, executive, and [[Judiciary|judicial]].<br />
<br />
The legislative branch, or [[Congress]], is split into two parts: the [[House of Representatives]] (HoR) and the [[Senate]]. Representatives in the HoR are responsible for creating and voting on legislation, while Senators review and vote on proposed bills from the HoR.<br />
<br />
The executive branch comprises the [[president]], [[vice president]], and the [[Cabinet]]. The [[president]] and [[vice president]] are elected <b>democratically by the players</b> every four months, leading the government as a whole! This is the same electoral system we use to elect our legislative branch. The Cabinet consists of advisors who oversee various government departments.<br />
<br />
The [[Judiciary|judicial branch]] runs the court system. Citizens have the right to bring legal disputes against each other, with judges presiding over cases and determining appropriate punishments based on {{DCForums|Link=/threads/constitution.6/#post-6|Forums=our constitution}}.<br />
<br />
Apart from judges and Cabinet members, who require presidential nomination and [[Senate]] approval, anyone can run for a government position. To participate in an election, simply join the race in our {{DCForums|Link=/forums/elections-referendums.27|Forums=Election and Referendums forum}}<br />
<br />
----<br />
<br />
== Worlds ==<br />
<br />
We have a mixture of creative, survival, wilderness, and urban worlds! Here's a breakdown of what you can expect from each:<br />
<br />
=== Wilderness ===<br />
<br />
* Keep Inventory: ON<br />
* Plot Claiming: ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: SOME APPLY (See https://www.democracycraft.net/threads/wilderness-laws-clarification-3-0-act.20744/)<br />
* Resets: NEVER<br />
<br />
The [[Wild|Wilderness]] is a naturally generated world where players can explore, gather resources, build bases, and engage in various unregulated activities. In this world, you are free to roam and create, but keep in mind that some laws still apply.<br />
<br />
Use the command <code>/airport</code>, then right-click on one of the nearby computer monitors to open a menu, where you can select your wilderness destination. <br />
<br />
{{Note|text=<b>Plot claiming</b><br />
<br>There are limited laws in the wild, protect your belongings by regioning land through a staff ticket for $10/block and by /locking your containers.|type=error}}<br />
<br />
=== Everwild, End, and Nether ===<br />
<br />
* Keep Inventory: OFF<br />
* Plot Claiming: NOT ALLOWED<br />
* PVP: ALLOWED<br />
* Laws: LAWLESS<br />
* Resets: REGULARLY<br />
<br />
The Everwild, End, and Nether are treacherous and lawless realms, with no governing rules to guide your actions. These dangerous worlds are perfect for players looking for high-risk adventures, where survival is up to your skill and luck. <br />
<br />
To reach the Everwild, use <code>/airport</code> and interact with a computer monitor to get your ticket. The End and Nether can be accessed through the Wilderness or Everwild worlds. <br />
<br />
{{Note|text=<b>Protect your items!</b><br />
<br>Keep Inventory is OFF in the End, Nether, and Everwild. When you die, you will drop all of your inventory.|type=warn}}<br />
<br />
=== Property, plots and apartments ===<br />
<br />
Players have the opportunity to rent and own various properties both in the city and the wilderness. These plots are technically referred to as "regions". If you own a plot in the city, you are able to build anything on it as long as it meets {{DCForums|Link=/threads/evictions-policy.26813/|Forums=government regulations}}. Most new players don't start off with plots, you will usually need to save up a lot of money first.<br />
<br />
[[file:reveille_city.png|thumb|600px]]<br />
<br />
To see plots for sale, run the commands <code>/as info forsale</code> and <code>/as info reselling</code>. On the Discord, eviction auctions are hosted periodically, and many plots go for sale there as well. <br />
<br />
For new players, we recommend that you wander inside large skyscrapers/apartment buildings for an apartment or rental shop instead. You can right click signs that say "[For Rent]" to rent your first apartment!<br />
<br />
You can check properties you own or rent using <code>/as me</code>. To see information on a region, use the command <code>/as info region --region (region name) </code><br />
<br />
<br />
=== Businesses ===<br />
[[file:sausage_sizzle_stands.png|thumb|600px]]<br />
<br />
You will often see [[chestshops]] and plots that are branded or owned by businesses. Chestshops will often have <code>b:<company name></code> and plots will have company logos on them. You are able to start your own business by getting an entrepreneur license from our University.<br />
<br />
<br />
<br />
== That's all! ==<br />
Great job on making it this far! We're excited to have you! Feel free to ask questions in-game, and if you haven't already, be sure to join our {{DCDiscord}}</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Block_protection&diff=7273Block protection2025-10-26T02:57:57Z<p>Goldendude15: Added some useful commands such as how to make a door auto-close, how to add a password to a protection etc.</p>
<hr />
<div><br />
DemocracyCraft features a simple block protection plugin to protect all your valuable goods. Take a few minutes to read this guide so you know how to best protect your loot!<span id="commands"></span><br />
== Commands ==<br />
<span id="lock"></span><br />
=== Lock ===<br />
<br />
Usage: <code>/bolt lock [type] (alias: /lock [type])</code> <br />
<br />
Description: Lock something. Optionally provide a protection type to lock with (defaults to private).<br />
<br />
<span id="unlock"></span><br />
=== Unlock ===<br />
<br />
Usage: <code>/bolt unlock (alias: /unlock)</code> <br />
<br />
Description: Unlock something.<br />
<br />
<span id="edit"></span><br />
=== Edit ===<br />
<br />
Usage: <code>/bolt edit (add|remove) &lt;player&gt;</code> <br />
<br />
Description: Edit a protection to add or remove a player’s access.<br />
<br />
<span id="modify"></span><br />
=== Modify ===<br />
<br />
Usage: <code>/bolt modify (add|remove) &lt;access&gt; &lt;source-type&gt; &lt;sources...&gt;</code> <br />
<br />
Description: Add or remove sources with given access to a protection’s access list (ACL).<br />
<br />
'''Useful variations:'''<br />
<br />
<code>/bolt modify add normal permission group.(groupname)</code> adds the specified group to a protection, if your unsure of a group name ask a staff member! Example: <code>/bolt modify add normal permission group.doctor</code> adds doctors to the permission.<br />
<br />
<code>/bolt modify add auto_close door True</code> makes the specified door have the auto-close property! '''IMPORTANT:''' The door/s need to first be closed ''and'' unlocked then you need to lock again and then apply the command otherwise the door will not become auto-close.<br />
<br />
<span id="group"></span><br />
=== Group ===<br />
<br />
Usage: <code>/bolt group (create|delete|add|remove|list) &lt;group&gt; [players...]</code> <br />
<br />
Description: Manage custom player groups, which can be used in access lists (ACLs).<br />
<br />
<span id="trust"></span><br />
=== Trust ===<br />
<br />
Usage: <code>/bolt trust [list|confirm|add|remove] [player]</code> <br />
<br />
Description: Prompt, list, or confirm changes to your trust access list.<br />
<br />
<span id="transfer"></span><br />
=== Transfer ===<br />
<br />
Usage: <code>/bolt transfer &lt;player&gt;</code> <br />
<br />
Description: Transfer a protection that you own to another player.<br />
<br />
<span id="password"></span><br />
=== Password ===<br />
<br />
Usage: <code>/bolt password &lt;password&gt;</code> <br />
<br />
Description: Enter a password for a protection that has a password source added.<br />
<br />
To set up a password for an already locked protection use the following command:<br />
<br />
<code>/bolt modify add normal password <your password></code><span id="mode"></span><br />
=== Mode ===<br />
<br />
Usage: <code>/bolt mode &lt;mode&gt;</code> <br />
<br />
Description: Toggle a player mode. For example: persist, no lock, no spam.<br />
<br />
{{Note| Example <code>/bolt persist</code> | Toggles persistent mode which let you perform your last action (command) on all blocks you left click without needing to re-type the command. Run this command again to toggle this mode off. <br />
::* <code>/bolt nolock</code> Toggles nolock mode which lets you place down all blocks without any of them locking by default. Run this command again to toggle this mode off. <br />
::* <code>/bolt nospam</code> Toggles nospam mode which reduces messages that you see in game, such as when you interact with a protection it will no longer say who it is protected by in chat (including your own protections). Run this command again to toggle this mode off.|}}<span id="help"></span><br />
<br />
=== Help ===<br />
<br />
Usage: <code>/bolt help [command]</code> Description: Displays help.<span id="info"></span><br />
=== Info ===<br />
<br />
Usage: <code>/bolt info</code> Description: Display protection information.<span id="what-can-i-protect"></span><br />
== What Can I Protect? ==<br />
<br />
You can protect the following:<br />
<br />
* Chests<br />
* Barrels<br />
* Furnaces<br />
* Lecterns<br />
* Buttons<br />
* Levers<br />
* Hoppers<br />
* ChestShop<br />
* Doors<br />
* Trap Doors<span id="container-guarentee"></span><br />
<br />
== Container Guarentee ==<br />
<br />
'''Any container that is stolen from in a regioned area (i.e. Wild or Urban) is covered by this staff guarantee.'''<br />
<br />
* Staff will recover the items and investigate those who stole from the container. <br />
* The container '''does not''' have to be locked, however, we strongly recommend you lock your containers to prevent this from occurring. If your chest is siphoned with a hopper or stolen from by someone with permissions to the chest, it will also be investigated and covered by the guarantee.<span id="conclusion"></span><br />
== Conclusion ==<br />
<br />
Hopefully this guide has helped you navigate the fun world of block protection! If you have any questions, join our Discord Server, we’ll be more than happy to help you there!<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7258Staff Guide2025-10-25T07:42:41Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots (e.g farms) are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <code>/deleteclaim</code> (Use this to delete the claim your standing on even if you're not the owner - be careful!<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7257Staff Guide2025-10-25T07:24:13Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots (e.g farms) are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
Wilderness regions are private wild plots that any players 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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <code>/deleteclaim</code> (Use this to delete the claim your standing on even if you're not the owner - be careful!<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7256Staff Guide2025-10-25T07:20:48Z<p>Goldendude15: I made some updates to the staff guide (missed something in previous edit oopsies): Added /staff-tp, /staff-removearmorstands, echest open command, //thru, specified how /tp2p is for admin+, specified how flags can only be modified by admin+, and updated the Wild regioning section. Also fixed some grammar and punctuation :</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots (e.g farms) are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</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.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
Wilderness regions are private wild plots that any players 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!<br />
<br />
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. <br />
<br />
'''Instructions:'''<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# 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!<br />
# Do <code>/as setowner DCGovernment</code> - this is very important :)<br />
# 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!''' <br />
# 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.<br />
<br />
'''Useful information:'''<br />
<br />
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:<br />
[[File:Listclaim.png|thumb|453x453px]]<br />
<br />
<br />
<br />
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. <br />
<br />
'''Other relevant commands:'''<br />
<br />
* <code>/ignoreclaims</code> Use this to bypass claim protections of the claim you're standing on. <br />
* <code>/deleteclaim</code> (Use this to delete the claim your standing on even if you're not the owner - be careful!<br />
<br />
If you're unsure with anything always consult with fellow staff members :)<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner/curator of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the spawn current staff wall up-to-date<br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands:''' <code>/staff-tp <player> <reason></code><br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from <code>/as tp</code><br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you through a wall in the direction your facing.<br />
<br />
* '''Commands:''' <code>//thru</code><br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
Create a GPS point.<br />
<br />
* '''Please stand still until the Editor says it is deactivated otherwise the command won't work!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
* Use <code>/gpsc editor</code> to visualize gps points as a particle enclosed block''', WARNING - this must be turned off by issuing the command again before you use''' /<code>staff-gps-create</code> or <code>/staff-gps-delete'''!'''</code> <br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting and other relevant staff duties!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
Removes armour stands in the specified radius around you. Useful for dealing with bugged custom items, bugged GPS arrows etc, go into /spec to identify armour stands.<br />
<br />
* '''Commands: <code>/staff-removearmorstands <radius></code>'''<br />
<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=File:Listclaim.png&diff=7255File:Listclaim.png2025-10-25T05:38:15Z<p>Goldendude15: </p>
<hr />
<div>Listclaim command output</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7254Staff Guide2025-10-25T05:31:13Z<p>Goldendude15: I made some updates to the staff guide: Added /staff-tp, echest open command, specified how /tp2p is for admin+, specified how flags can only be modified by admin+, updated the Wild regioning section. Also fixed some grammar and punctuation :(</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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]]<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
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. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
<br />
Here is a basic rundown (not exhaustive) of some flags you might come across or may need to add/change. <br />
<br />
'''NOTE:''' Only Admin+ are able to modify region flags but it's good to be aware of what flags exist. <br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <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<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is omitted from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use CoreProtect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots (e.g farms) are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each individual region costs '''$25''' to create excluding shulker regions, those are free. Don't forget the fee! <br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount> <reason&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25 Staff rental creation</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region, rental money will go to the landlord.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access it.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** 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.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning: ====<br />
Wilderness regions are private wild plots that any players 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. See [[Wilderness Claiming]].<br />
<br />
Some players still have an wild claim of the old system where they were made using a WorldGuard region and added to AreaShop, you may be needed to transfer this claim to the new system. The instructions to do so are as follows:<br />
<br />
# Do <code>/rg i</code> on the player's old claim or <code>/rg info <claim name (will be the playername)></code><br />
# Click on Bounds to select the player's old claim<br />
# 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.<br />
# Run <code>//count #yaxis</code> to get the number of surface blocks<br />
# Run <code>/staff-grant-claim-blocks <username> <amount of blocks></code>, replacing <code><amount of blocks></code> with the number from <code>//count</code><br />
# Do <code>/as setowner DCGovernment</code> while standing inside the old Wilderness claim<br />
# Run <code>/rg-d <username></code> to kill the old region. The player won’t be refunded anything as their claim is being transferred,not refunded. <br />
# The player then has the correct number of blocks to re-claim their new region, direct them to [[Wilderness Claiming]] and assist them if needed. <br />
<br />
Useful information:<br />
<br />
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:<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== '''Supporter Chests''' ====<br />
Opens the specified player’s supporter chest (only supporters have the echest) in real time.<br />
<br />
<code>/chest <player></code><br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
Teleports you to a specified player.<br />
<br />
* '''Commands: <code>/staff-tp <player> <reason></code>'''<br />
<br />
<br />
Teleports the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> '''Note:''' This command is only accessible to Admin+ <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting etc!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Vaulting&diff=7252Staff Vaulting2025-10-24T10:45:04Z<p>Goldendude15: minor</p>
<hr />
<div>This will be a guide covering how to vault players items, chests, and structures.<br />
<br />
This guide assumes you are familiar with WorldEdit. See [[Staff Guide]] and/or review WorldEdit documentation if need be. <br />
<br />
== Vaulting ==<br />
<br />
<br />
=== Locating the vault ===<br />
<br />
Use <code>/staff-tpvault</code>. This command will automatically search for a player's vault plot or create a new one if they dont already have one! If that doesn't work use <code>/plot visit <name> NewVault</code><br />
<br />
If a player does not have a vault created yet, you can warp to the NewVault world.<br />
* <code>/plot auto</code><br />
* <code>/plot setowner <name></code><br />
<br />
=== Cutting items ===<br />
<br />
Select your corners with world-edit, and use <code>//cut -e</code><br />
<br />
=== Pasting items ===<br />
<br />
All you need to do is find a good spot to <code>//paste</code> Try to keep plots semi-organized when pasting items, it becomes harder to paste when you're playing Tetris!<br />
<br />
=== Finishing up === <br />
<br />
Once you're finished furnishing the vault, you'll need to notify the player that they've had items vaulted.<br />
<code>/staff-vault <name></code><br />
This will send them a mail notification!<br />
<br />
All that's left to do is run <code>/staff-cleanup-locks</code> When you world-edit locked containers, the locks sometimes persist, this command ensured they're cleaned up properly.<br />
<br />
{{Staff}}<br />
[[category:staff]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Wilderness_Claiming&diff=7166Wilderness Claiming2025-10-04T21:29:48Z<p>Goldendude15: Added how to make a new claim</p>
<hr />
<div>DemocracyCraft utilises a simple '''self-service claiming system''' for claiming up to '''4,096 blocks''' in the Wilderness!<br />
<br />
* Each block costs '''$10''', and can be bought as you acquire the funds<br />
* You start out with '''10 free blocks''' (very generous we know)<br />
* You can only '''claim in the Wilderness, not the Everwild!'''<br />
<br />
[[File:Create a Claim in Claims Menu.png|thumb|496x496px|Click '''Create a Claim''' in order to create your claim!]]<br />
<br />
== How to get started ==<br />
<br />
# Travel to the Wilderness (<code>/airport</code>)<br />
# Find a piece of land that you would like to claim<br />
# Run <code>/claim</code> and select '''Create a Claim!'''<br />
<br />
<br />
You can add people to your claims and more in the <code>/claim</code> menu!<br />
<br />
* You can also '''buy more claim blocks in the same menu!'''<br />
<br />
== How to make a new claim ==<br />
<br />
# 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.'''<br />
# Make sure you have enough claim blocks to create the claim you want, hover over the grass block in the /claim gui to check! If you need more buy more buy selecting the grass block! <br />
# Once you confident you have enough claim blocks use your wand to select the first corner of your claim, you shall see a diamond block to indicate this corner selection!<br />
# Go to your other corner of the proposed claim (claims can only be rectangular in shape) and select that corner. Gold block indicators should show up to outline your new claim. These indicators will disappear after a certain amount of time :D<br />
<br />
== How to expand a claim ==<br />
<br />
# 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.'''<br />
# <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!''']]<br />
# <code>'''RIGHT CLICK'''</code> with the claim wand '''any <u>corner</u>''' ('''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!''']]<br />
# <code>'''RIGHT CLICK'''</code> the new position for your corner. '''If you have enough claim blocks, your claim will automatically resize!'''<br />
<br />
[[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.''']]<br />
<br />
* '''Don't have enough claim blocks?''' Buy more from '''<code>/claim</code>'''!<br />
<br />
== What about my old AreaShop Wilderness claim? ==<br />
You '''CANNOT''' have both. <br />
<br />
* If Staff find you have both, your old AreaShop claim may be '''deregistered without notice!'''<br />
<br />
You can ask a Staff member to give you the equivalent claim blocks. The Staff member will<br />
<br />
* '''Calculate''' how large your AreaShop Wilderness claim is using WorldEdit<br />
* '''Give''' you the appropriate number of claim blocks (using <code>/staff-grant-claim-blocks</code>)<br />
* '''Delete''' your old AreaShop claim<br />
<br />
Your locked items will '''remain locked''', you can readd players to your claim in the Trusted section of <code>/claim</code>!</div>Goldendude15https://wiki.democracycraft.net/index.php?title=File:Goldendude15_sitting.png&diff=7141File:Goldendude15 sitting.png2025-09-26T05:51:45Z<p>Goldendude15: </p>
<hr />
<div>sitting</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Vice_president&diff=7140Vice president2025-09-26T05:42:06Z<p>Goldendude15: Added VP Technofied</p>
<hr />
<div>The '''vice president of Redmont''' is the second-highest ranking officer of the executive branch and acts as an adviser to the [[president]].<ref name=":0">https://www.democracycraft.net/threads/constitution.6/</ref><br />
<br />
The vice president is elected with the president for a four month term. In the event that the vice president is removed or resigns from their position, the president may then nominate a replacement, with approval from two-thirds of the [[Senate]].<ref name=":0" /><br />
<br />
The vice president has no executive authority unless delegated by the president. In the event of a tie in the Senate, the vice president casts the tie-breaking vote.<ref name=":0" /><br />
<br />
In order to be eligible to be vice president, a citizen must have at least 12 hours of active playtime in the last 30 days, joined at least 4 months ago, accrued at least 150 hours of active playtime, and cannot be the most recently elected president.<ref name=":0" /><br />
<br />
== List of vice presidents ==<br />
'''Note: this list is a work in progress.'''<br />
<br />
Note: With the ratification of the [https://www.democracycraft.net/threads/presidential-inauguration-amendment.3150/ Presidential Inauguration Amendment] on 4 February 2021, every presidential election from that point onwards has resulted in the presidential term starting and ending on the 15th of the month.<br />
{| class="wikitable sortable"<br />
|+ Vice presidents of Redmont<br />
!No.<br />
!Portrait<br />
!Name<br />
!Term (UTC)<br />
!President<br />
!Ref.<br />
|-<br />
|1<br />
|[[File:Jaynormous face.png|frameless|140px]]<br />
|[[Jaynormous]]<br />
|12 April 2020 - Unknown<br />
| rowspan="3" |[[xEndeavour]]<br />
|<ref>[[File:Screenshot 2025-07-06 at 1.43.32 AM.png|thumb]]<br />
https://discord.com/channels/673612908868927498/686158870435201035/698865164497322024</ref><br />
|-<br />
|2<br />
|[[File:Temujim face.png|frameless|140px]]<br />
|[[Temujim]]<br />
|9 June - 26 August 2020 (Resigned)<br />
|<ref>[[File:Appointments Announcement 9 June 2020.png|thumb]]<br />
https://discord.com/channels/673612908868927498/686158870435201035/719876731858845849</ref> <ref>https://www.democracycraft.net/threads/sotg-report-may-2020.369/ (Nominations section)</ref> <ref name=":1">[[File:Temujim Resignation Announcement.png|thumb]]<br />
https://discord.com/channels/673612908868927498/686158870435201035/748128924558688306</ref><br />
|-<br />
|3<br />
|[[File:Technofied face.png|frameless|140px]]<br />
|[[Technofied]]<br />
|26 August - 14 October 2020<br />
|<ref name=":1" /> <ref name=":10">[[File:1st Presidential Election Results Announcement.png|thumb]]<br />
https://discord.com/channels/673612908868927498/686158870435201035/766082034950995988</ref><br />
|-<br />
|4<br />
|[[File:Doxxx_ face.png|frameless|140px]]<br />
|[[Doxxx_]]<br />
|14 October 2020 - 7 February 2021 (Resigned)<br />
| rowspan="2" |[[Westray]]<br />
|<ref name=":10" /><ref>https://www.democracycraft.net/threads/presidential-elections-october-2020.1094/</ref> <ref name=":2">[[File:Vice Presidential Nomination Announcement byeSprite.png|thumb]]<br />
https://discord.com/channels/673612908868927498/686158870435201035/808120268073336882</ref><br />
|-<br />
|5<br />
|[[File:byeSprite face.png|frameless|140px]]<br />
|[[byeSprite]]<br />
|7 February 2021 - 14 February 2021<br />
|<ref name=":2" /> <ref name=":3">https://discord.com/channels/673612908868927498/686158870435201035/810684083574145086</ref> <ref name=":4">https://www.democracycraft.net/threads/presidential-elections-february-2021.3354/</ref><br />
|-<br />
|6<br />
|[[File:hugebob23456 face.png|frameless|140px]]<br />
|[[hugebob23456]]<br />
|14 February 2021 - 31 March 2021 (Continued as president)<br />
|[[Krix]]<br />
|<ref name=":3" /> <ref name=":4" /> <ref>https://discord.com/channels/673612908868927498/686158870435201035/826986451970818098</ref><br />
|-<br />
|7<br />
|[[File:_Zab_ face.png|frameless|140px]]<br />
|[[_Zab_]]<br />
|2 April 2021 - 15 June 2021 <br />
|[[hugebob23456]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/827641888524992592</ref> <ref name=":5">https://discord.com/channels/673612908868927498/686158870435201035/854464937170567168</ref><br />
|-<br />
|8<br />
|[[File:Vanquish69 face.png|frameless|140px]]<br />
|[[Vanquish69]]<br />
|15 June 2021 - 15 October 2021<br />
|[[_Austin27_]]<br />
|<ref name=":5" /> <ref name=":6">https://discord.com/channels/673612908868927498/686158870435201035/898824847411527680</ref><br />
|-<br />
|9<br />
|[[File:GoldBlooded face.png|frameless|140px]]<br />
|[[GoldBlooded]]<br />
|15 October 2021 - 7 December 2021 (Resigned)<br />
| rowspan="2" |[[218218Consumer]]<br />
|<ref name=":6" /> <ref>https://www.democracycraft.net/threads/presidential-elections-october-2021.9266/</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/917815292514685019</ref> <br />
|-<br />
|10<br />
|[[File:LilDigiVert face.png|frameless|140px]]<br />
|[[LilDigiVert]]<br />
|7 December 2021 - 6 February 2022 (Continued as president)<br />
|<ref>https://discord.com/channels/794162227837534208/794283346565922847/917816224799416370</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/917839678424645663</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/940108259874988062</ref><br />
|-<br />
|11<br />
|<br />
|[[_Austin27_]]<br />
|7 February 2022 - 15 February 2022<br />
|[[LilDigiVert]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/940396365807235114</ref> <ref name=":7">https://discord.com/channels/673612908868927498/686158870435201035/943323611014504499</ref> <br />
|-<br />
|12<br />
|[[File:Muffins29 face.png|frameless|140px]]<br />
|[[Muffins29]]<br />
|15 February 2022 - 15 June 2022<br />
|[[Westray]]<br />
|<ref name=":7" /> <ref>https://www.democracycraft.net/threads/presidential-elections-february-2022.11511/</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/988087144163737652</ref><br />
|-<br />
|13<br />
|[[File:huney69 face.png|frameless|140px]]<br />
|[[huney69]]<br />
|15 June 2022 - 9 October 2022 (Continued as president)<br />
|[[LilDigiVert]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/988087144163737652</ref> <ref>https://www.democracycraft.net/threads/presidential-elections-june-2022.13224/</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1028852122382508112</ref><br />
|-<br />
|14<br />
|[[File:LilDigiVert face.png|frameless|140px]]<br />
|[[LilDigiVert]]<br />
|9 October 2022 - 15 October 2022<br />
|[[huney69]]<br />
|<ref>https://discord.com/channels/794162227837534208/918003510795202640/1028773682673361027</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1030938821715558450</ref><br />
|-<br />
|15<br />
|[[File:Derpy_Bird face.png|frameless|140px]]<br />
|[[Derpy_Bird]]<br />
|15 October 2022 - 1 December 2022 (Continued as president)<br />
|[[Deadwax]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/1030938821715558450</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1048090472989605961</ref> <ref>https://www.democracycraft.net/threads/presidential-elections-october-2022.14630/</ref><br />
|-<br />
|16<br />
|[[File:Rurge face.png|frameless|140px]]<br />
|[[Rurge]]<br />
|2 December 2022 - 17 February 2023<br />
|[[Derpy_Bird]]<br />
|<ref>https://discord.com/channels/794162227837534208/918003510795202640/1048441100597207080</ref> <ref>https://discord.com/channels/794162227837534208/918003510795202640/1048441964384751726</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1076305828153393236</ref><br />
|-<br />
|17<br />
|[[File:sleepyjay_ face.png|frameless|140px]]<br />
|[[sleepyjay_]]<br />
|17 February 2023 - 18 June 2023<br />
|[[Twixted]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/1074156150309797968</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1076305828153393236</ref><br />
|-<br />
|18<br />
|[[File:Vanquish69 face.png|frameless|140px]]<br />
|[[Vanquish69]]<br />
|18 June 2023 - 15 October 2023<br />
|[[LilDigiVert]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/1117253817705168956</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1119742653274271744</ref> <ref name=":8">https://discord.com/channels/673612908868927498/686158870435201035/1163257421091831912</ref><br />
|-<br />
|19<br />
|[[File:Nacholebraa face.png|frameless|140px]]<br />
|[[Nacholebraa]]<br />
|15 October 2023 - 15 February 2024<br />
|[[xlayzur]]<br />
|<ref name=":8" /> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1207576222494625813</ref><br />
|-<br />
|20<br />
|[[File:SomeHumanOnEarth face.png|frameless|140px]]<br />
|[[SomeHumanOnEarth]]<br />
|15 February 2024 - 15 June 2024<br />
|[[GoldBlooded]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/1207576222494625813</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1251638805195395134</ref><br />
|-<br />
|21<br />
|[[File:JediAJMan face.png|frameless|140px]]<br />
|[[JediAJMan]]<br />
|15 June 2024 - 15 October 2024<br />
|[[Bezzergeezer]]<br />
|<ref>https://www.democracycraft.net/threads/presidential-elections-june-2024.21537/</ref> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1251638805195395134</ref> <ref name=":9">https://www.democracycraft.net/threads/presidential-elections-october-2024.23503/</ref><br />
|-<br />
|22<br />
|[[File:lcn face.png|frameless|140px]]<br />
|[[lcn]]<br />
|15 October 2024 - 18 January 2024 (Continued as president)<br />
|[[UnityMaster]]<br />
|<ref name=":9" /> <ref>https://discord.com/channels/673612908868927498/686158870435201035/1330387890152276012</ref><br />
|-<br />
| rowspan="2" |23<br />
| rowspan="2" |[[File:Yeet_Boy face.png|frameless|140px]]<br />
| rowspan="2" |[[Yeet_Boy]]<br />
| rowspan="2" |21 January 2025 - 15 June 2025<br />
|[[lcn]]<br />
|<ref>https://discord.com/channels/673612908868927498/686158870435201035/1331404785122934936</ref><br />
|-<br />
|[[1950minecrafter]]<br />
|<ref>https://www.democracycraft.net/threads/presidential-elections-february-2025.24616/</ref><br />
|-<br />
|24<br />
|[[File:juniperfig face.png|frameless|140px]]<br />
|[[juniperfig]]<br />
|15 June 2025 - 25th August 2025<br />
|[[Kaiserin_]]<br />
|<ref>https://www.democracycraft.net/threads/presidential-elections-june-2025.26419/</ref><br />
|-<br />
|25<br />
|[[File:Technofied face.png|thumb|125x125px]]<br />
|[[technofied]]<br />
|29 August 2025 - Present<br />
|[[juniperfig]]<br />
|<ref>https://discord.com/channels/794162227837534208/1410238779431845948</ref><br />
|}<br />
<br />
== References ==<br />
<references /><br />
<br />
{{Vice presidents}}<br />
<br />
[[Category:Vice presidents| ]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Technofied&diff=7139Technofied2025-09-26T05:33:23Z<p>Goldendude15: Updated to include Vice Presidency info</p>
<hr />
<div>{{Infobox<br />
| name = Technofied<br />
| image = https://www.mc-heads.net/body/7f002e0c-72ea-4b6b-b989-8ff45bd6dd3b/100.png<br />
| above = Technofied<br />
| header1 = Personal details<br />
| label2 = Join date<br />
| data2 = 16 March 2020<br />
| label3 = Occupation<br />
| data3 = Politician<br />
| label4 = Political party<br />
| data4 = Independent<br />
| label5 = Pronouns<br />
| data5 = He/him<br />
| label6 = Nationality<br />
| data6 = {{ISO|AU}}<br />
<br />
}}<br />
'''Technofied''' (joined 16 March 2020), also known as '''Tech''', or occasionally '''Tuk''', is a Redmontian politician, senior administrator, and owner of DemocracyCraft, along with [[xEndeavour]] (End). He is currently serving as the Vice President to President Juniperfig. <br />
<br />
== Early life and server ownership ==<br />
[[File:CoatofArms.png|200px|thumb|left|alt=Redmont Coat of Arms|The Redmont Coat of Arms, referencing Tech]]<br />
Tech joined the server just over a week after its foundation, while it was still in Beta. He was quickly made a member of staff, one of the server's first. <br />
<br />
In September 2020, after the retirement of founder and owner [[Jaynormous]], Technofied took up co-ownership of the server along with End and has been an instrumental driver in optimisation and server progression ever since. Tech is often regarded as the server’s technical specialist while End primarily manages the player base and staff team.<br />
<br />
== Political career ==<br />
Unlike his fellow co-owner End, Tech has never sought the office of the Presidency,<ref>[[List of presidential elections]]</ref> however, he has served on a number of occasions in various positions in the Executive and further afield.<br />
<br />
=== xEndeavour administration ===<br />
==== Vice president ====<br />
On the 26<sup>th</sup> of August 2020, Technofied was appointed as the third [[Vice President]] of the Commonwealth of Redmont by then-president, xEndeavour. He served the rest of End's term, his tenure ending in October of the same year. As one of the first Vice Presidents of Redmont, he helped set precedents for how the position of VP should be run, as well as the executive branch as a whole.<br />
<br />
=== Bezzergeezer administration ===<br />
==== Secretary of Homeland Security ====<br />
Tech was appointed to the position of Secretary of Homeland Security in June of 2024 by President [[Bezzergeezer]]. During his term, he revitalised the Department of Homeland Security, offered strong leadership and provided guidance to not only the President, but others in the administration and wider community.<br />
<br />
He was succeeded by [[HellsideBurnton]].<br />
<br />
==== Secretary of Construction & Transport ====<br />
He was also appointed the Secretary of Construction & Transport, in which capacity he reformed the Department, restoring its efficiency and making it operate smoothly.<br />
<br />
==== Presidential commendation ====<br />
In the President's words, "[his] unwavering commitment to improving Redmont’s government is clear in every action he takes ... His remarkable contributions deserve recognition and respect for his tireless efforts".<ref name="PC">[https://www.democracycraft.net/threads/executive-order-23-24-president-bezzers-commendations.23593/ "Executive Order - Executive Order 23/24 - President Bezzers Commendations"]</ref><br />
<br />
For his work in these positions, he was given a [[List of presidential commendations|presidential commendation]].<ref name="PC"/><br />
<br />
=== List of offices held ===<br />
<blockquote>''This list is incomplete; you can help by adding missing items.''</blockquote><br />
<br />
A list of all the government positions held by Technofied can be found below:<br />
<br />
{| class="wikitable"<br />
!Position<br />
!Administration<br />
!Tenure<br />
!Refs.<br />
|-<br />
|Vice President<br />
| rowspan="3" |[[XEndeavour administration|xEndeavour]]<br />
|August 2020 - October 2020<br />
| rowspan="4" |<ref name=":0">https://discord.com/channels/673612908868927498/673617846277767168/1350666578437341184</ref><br />
|-<br />
| rowspan="3" |Secretary of Education & Commerce<br />
|May 2020 - August 2020<br />
|-<br />
|September 2020 - October 2020<br />
|-<br />
|[[Westray#First Term|Westray]] (1)<br />
|October 2020 - December 2020<br />
|-<br />
|Treasurer of Redmont<br />
|[[Deadwax]]<br />
|''unknown''<br />
|<ref>https://discord.com/channels/673612908868927498/673617846277767168/1350668462476890276</ref><br />
|-<br />
|Secretary of Justice<br />
|[[Derpy Bird]]<br />
|October 2022 - February 2023<br />
| rowspan="7" |<ref name=":0" /><br />
|-<br />
|Secretary of Commerce<br />
| rowspan="2" |[[Twixted]]<br />
|May 2023 - June 2023<br />
|-<br />
| rowspan="2" |Secretary of Justice<br />
|June 2023<br />
|-<br />
| rowspan="2" |[[Xlayzur]]<br />
|October 2023 - February 2024<br />
|-<br />
| rowspan="2" |Secretary of Commerce<br />
|January 2024 - February 2024<br />
|-<br />
|[[Nacholebraa]]<br />
| rowspan="2" |February 2024<br />
|-<br />
|Secretary of Commerce (''Acting'')<br />
| rowspan="2" |[[GoldBlooded]]<br />
|-<br />
|Reserve Member of the [[Federal Reserve Bank|FRB]]<br />
|''unknown''<br />
|<ref>https://discord.com/channels/673612908868927498/673617846277767168/1350662448864301119</ref><br />
|-<br />
|Secretary of Homeland Security<br />
| rowspan="2" |[[Bezzergeezer]]<br />
|June 2024 - October 2024<br />
| rowspan="6" |<br />
|-<br />
|Secretary of Construction & Transport<br />
| rowspan="2" |''unknown''<br />
|-<br />
|Executive Advisor<br />
| rowspan="2" |[[UnityMaster]]<br />
|-<br />
| rowspan="2" |Secretary of Commerce<br />
|October 2024<br />
|-<br />
|[[lcn]]<br />
|October 2024 - February 2025<br />
|-<br />
|Secretary of State<br />
|[[1950minecrafter]]<br />
|March 2025 - June 2025<br />
|-<br />
|Vice President<br />
|[[Juniperfig]]<br />
|August 2025 - Present<br />
|<br />
|}<br />
<br />
== Lore ==<br />
=== A god ===<br />
Tech is often humorously referred to as a 'god', especially in [[Redmont]]'s national motto "In End and Tech We Trust" as found on the [[Government Branding#Coat of Arms|Coat of Arms]], a play on [https://en.wikipedia.org/wiki/In_God_We_Trust "In God We Trust"], the official motto of the United States.<br />
<br />
The reason for this is unclear, however, may be explained by a combination of factors:<br />
* There is a [https://www.democracycraft.net//threads/constitution.6/#post-6:~:text=It%27s%20important%20to%20note%20that%20the%20Government%20and%20the%20Server%20Staff%20have%20completely%20different%20roles%20and%20functions constitutional mandate] for staff and government to "have completely different roles and functions"<ref>https://www.democracycraft.net//threads/constitution.6/#post-6:~:text=It%27s%20important%20to%20note%20that%20the%20Government%20and%20the%20Server%20Staff%20have%20completely%20different%20roles%20and%20functions</ref> <br />
* Although there is no ''explicit'' hierarchy between staff and government, the fact that staff have the final decision on certain matters, such as which plugins can be added, or the size of the map,<ref>https://www.democracycraft.net//threads/constitution.6/#post-6:~:text=For%20the%20Benefit%20of%20the%20server%2C%20Network%20Staff/Server%20Manager%20retain%20the%20reserve%20power%20to%20completely%20override%20any%20Government%20decision.</ref> makes them in a sense, a higher authority than the government.<br />
* The owners, Tech and End, have the final say on all staff matters.<br />
* Since staff can veto government decisions, and the owners are the heads of the staff team, they act, in a sense, as higher powers to which there is no course for debate.<br />
* The closest equivalent to this, in the real world, is a God.<br />
<br />
=== Tukmas ===<br />
<blockquote>Main article: [[Tukmas]]</blockquote><br />
"[[Tukmas]]" is a humorous term for Christmas derived from Technofied's name. The Tuk- prefix, which is also used in the name of [[St. Tuk Cathedral]], is widely used in the DemocracyCraft community, and is often applied more broadly to Christmas-related terms.<br />
<br />
== Personal life ==<br />
[[File:Technofied's House.png|300px|thumb|right|An aerial image of the property east of Willow, owned and maintined by Technofied, as of 16/Mar/2025<ref>https://map.democracycraft.net/#reveille:2561:10:2059:429:0:0:0:1:flat</ref>]]<br />
Technofied is British-Australian in real life, hailing from [[wikipedia:Manchester|Manchester]]. In-game, he largely resides in [[Reveille]],<ref>https://discord.com/channels/673612908868927498/673617846277767168/1350667541793476739</ref> however, he maintains a property just east of [[Willow]].<ref>https://discord.com/channels/673612908868927498/673617846277767168/1350667292702146620</ref><br />
<br />
On the 13<sup>th</sup> of June 2020, Tech called fellow staff member [[Taelor]] evil. [[Dusty_3]] agreed with Technofied and showed disapproval of Taelor.<ref>[https://discord.com/channels/673612908868927498/673617846277767168/721271157470396457 Discord | #global | DemocracyCraft]</ref> As of mid-March 2025, this feud seems to have subsided.<br />
<br />
== Accolades ==<br />
In his storied tenure on the server, Tech has won a number of awards. Some of these include:<br />
{| class="wikitable"<br />
!Award<br />
!Organisation, event, or official<br />
!Date<br />
|-<br />
|Funniest Player<br />
|[[DC Awards]]<br />
|September 2020<br />
|-<br />
|Order of Redmont<ref>https://www.democracycraft.net/threads/executive-order-26-23-president-lildigivert-order-of-redmont-awards-ii.19034/</ref><br />
|President [[LilDigiVert]]<br />
|October 2023<br />
|-<br />
|Presidential commendation<ref>https://www.democracycraft.net/threads/executive-order-23-24-president-bezzers-commendations.23593/</ref><br />
|President [[Bezzergeezer]]<br />
|October 2024<br />
|-<br />
|Order of Service<ref>https://www.democracycraft.net/threads/executive-order-11-25-president-lcns-order-of-service-awards.24782/</ref><br />
|President [[lcn]]<br />
|February 2025<br />
|-<br />
|Most Dedicated Person of the Year<br />
| rowspan="2" |[[2024 Players' Choice Awards]]<br />
| rowspan="2" |10 February 2025<br />
|-<br />
|Staff Member of the Year<br />
|}<br />
<br />
== References ==<br />
<references/><br />
<br />
{{Vice presidents}}<br />
{{Department of Commerce}}<br />
{{Department of State}}<br />
<br />
[[Category:Technofied| ]]<br />
[[Category:2020 joins]]<br />
[[Category:2021 people]]<br />
[[Category:2022 people]]<br />
[[Category:2023 people]]<br />
[[Category:2024 people]]<br />
[[Category:2025 people]]<br />
[[Category:Executive advisors to UnityMaster]]<br />
[[Category:Inaugural administration]]<br />
[[Category:Staff members]]<br />
[[Category:UnityMaster administration]]<br />
[[Category:Vice presidents]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=File:Technofied_face.png&diff=7138File:Technofied face.png2025-09-26T05:30:03Z<p>Goldendude15: </p>
<hr />
<div>Tech face</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7137Staff Guide2025-09-25T03:38:54Z<p>Goldendude15: Removed svp links 🫠</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment --region &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice --region &#x3C;price&#x3E; &#x3C;region&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting etc!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Useful_commands&diff=7135Useful commands2025-09-24T03:17:07Z<p>Goldendude15: Added there is no longer a fee for /ad</p>
<hr />
<div>Welcome to the commands guide! Whether you’re a seasoned player or new to the server, this resource provides quick references for essential player commands. For commands that are specific to certain plugins, review the specific guide! Let’s dive in!<br />
[[File:Qsdt_msg.png|770x770px]]<div class="figure">[[File:Lets_learn_more_about_commands.png|769x769px]]</div><br />
== Chat Commands ==<br />
<br />
<code>/g</code> - switch to global chat.<br />
<br />
<code>/l</code> - switch to local chat.<br />
<br />
<code>/murmur</code> - switch to whisper chat.<br />
<br />
<code>/vc</code> - to talk to players in voice chat via text.<br />
<br />
<code>/msg &lt;user&gt; &lt;message&gt;</code> - send a direct message to someone.<br />
<br />
<code>/tell &lt;user&gt; &lt;message&gt;</code> - send a direct message to someone.<br />
<br />
<code>/r &lt;message&gt;</code> - reply to the player who just messaged you.<br />
<br />
<code>/mail send &lt;user&gt; &lt;message&gt;</code> - send mail to someone on or offline.<br />
<br />
<code>/ad &lt;message&gt;</code> - to send an ad in chat, please note you need to complete the entrepreneur exam to use. There is a 10 minute cooldown between your ads!<br />
<br />
<code>/nexo emojis</code> - see a list of emojis available to put in chat. Put them in chat using <code>:emoji_name:</code><br />
<br />
{{Note|type=info|Other Channels - If you are a member of a government department or institution, chances are you may have additional channels to talk in.}} <br />
For example : <br />
::- Members of the Department of Justice can speak in the <code>/doj</code> channel. <br />
::- Members of the Senate can speak in the <code>/sen</code> channel. <br />
::- Members of the courts can speak in the <code>/jud</code> channel.<br />
<br />
== Economy Commands ==<br />
<br />
<code>/pay &lt;user&gt;</code> - send an user money.<br />
<br />
<code>/vote</code> - earn money by voting on serverlist sites.<br />
<br />
<code>/firm deposit &lt;company&gt; &lt;amount&gt;</code> - send a company money.<br />
<br />
<code>/firm withdraw &lt;company&gt; &lt;amount&gt;</code> - withdraw money from a company.<br />
<br />
<code>/firm sales &lt;company&gt;</code> - view your company chestshop sales.<br />
<br />
<code>/firm menu</code> - view your companies.<br />
<br />
See [[Business]] for more commands.<br />
<br />
<code>/csn history</code> - view your personal chestshop sales.<br />
<br />
<code>/baltop</code> - view the top balance rankings.<br />
<br />
<code>/bal</code> - view your balance.<br />
<br />
<span id="job-commands"></span><br />
== Job Commands ==<br />
<br />
<code>/guides</code> - learn more about the server.<br />
<br />
<code>/jobguides</code> - learn more about jobs.<br />
<br />
<code>/quitjob</code> - quit your regular job.<br />
<br />
<code>/quitprofession</code> - quit your professional job.<br />
<br />
<code>/about &lt;player&gt;</code> - view the player’s information and jobs.<br />
<br />
<code>/find &lt;item&gt;</code> - search for chestshops with the specified item.<br />
* <code>/find toggle</code> - while looking at air, will disable the holograms above chestshops.<br />
<br />
<span id="ticket-commands"></span><br />
== Ticket Commands ==<br />
<br />
<code>/ticket</code> - open a ticket with staff :)<br />
<br />
<span id="location-commands"></span><br />
== Location Commands ==<br />
<code>/map</code> - link to the dynmap.<br />
<br />
<code>/coords</code> - to show the coordinates of where you are.<br />
<br />
<code>/sendcoords &lt;user&gt;</code> - send a direct message of your coordinates to someone.<br />
<br />
<code>/gps start &lt;plot number&gt;</code> - to find directions to a specific plot number.<br />
<br />
<code>/gps stop</code> - turns off GPS.<br />
<br />
<code>/find &lt;item&gt;</code> - search for chestshops with the specified item.<br />
<br />
<code>/sethome &lt;home name&gt;</code> - set a home. <br />
<br />
<code>/home &lt;home name&gt;</code> - go to your set home.<br />
<br />
<code>/spawn</code> - teleport to Spawn.<br />
<br />
<code>/spawn-north</code> or <code>/zoo</code> - teleport to North Spawn.<br />
<br />
<code>/spawn-south</code> or <code>/courts</code> - teleport to South Spawn.<br />
<br />
<code>/spawn-university</code> or <code>university</code> - teleport to the University.<br />
<br />
<code>/spawn-airport</code> or <code>airport</code> - teleport to the Airport.<br />
<br />
<code>/spawn-oakridge</code> or <code>/oakridge</code> - teleport to Oakridge, the logging town.<br />
<br />
<code>/spawn-willow</code> or <code>/willow</code> - teleport to Willow, the farming district.<br />
<br />
<code>/spawn-aventura</code> or <code>/aventura</code> - teleport to Aventura, the fishing town.<br />
<br />
== General Commands ==<br />
<br />
<code>/health symptoms</code> - see your current symptoms.<br />
<br />
<code>/health temperature</code> - see your current temperature.<br />
<br />
<code>/government</code> - link to list of government officials.<br />
<br />
<code>/constitution</code> - link to the constitution page.<br />
<br />
<code>/complaint</code> - to report a player to the police after being murdered.<br />
<br />
<code>/laws</code> - link to the rules and laws list.<br />
<br />
<code>/rules</code> - link to the rules and laws list.<br />
<br />
<code>/sit</code> - sit down.<br />
<br />
<code>/crawl</code> - lay down.<br />
<br />
<code>/about &lt;user&gt;</code> - view info such as playtime + jobs that you hold!<br />
<br />
<code>/plan register</code> - register to view your personal analytics, more information here.<br />
<br />
<code>/cmodify</code> - allows you to change permission to your items such as chests and doors.<br />
<br />
<code>/updateitems</code> - Updates your custom items to their new version - helpful if they have been changed! Applies to the container (chest, barrel) you are looking at.<br />
* <code>/updateitems -o</code> Add the -o to overwrite it's lore, if you are still having trouble. Gets rid of autographs.<br />
* <code>/updatehand</code> Updates the item in your hand instead.<br />
<br />
== Real estate commands ==<br />
<br />
<code>/as me</code> - shows you all real estate that you own.<br />
<br />
<code>/as resell <price> --region <plot #></code> - puts your plot on sale (other players can buy it).<br />
<br />
<code>/as stopresell <price> --region <plot #></code> - reverts the resell command (other players will not be able to buy the plot anymore).<br />
<br />
<code>/as sell --region <plot #></code> - instantly sells your plot back to DCGovernment for the price listed in 'selling payback'. <br />
<br />
<code>/as buy --region <plot #></code> - instantly buys a plot.<br />
<br />
<code>/as addfriend <username> --region <plot #></code> - adds your friend to the plot (they will be able to place/destroy blocks).<br />
<br />
<code>/as delfriend <username> --region <plot #></code> - deletes your friend's permissions to build/destroy on your plot.<br />
<br />
<code>/as rent --region <plot #></code> - rents an available plot.<br />
<br />
<code>/as unrent --region <plot #></code> - unrents a plot you're renting (you will get your remaining money back).<br />
<br />
<code>/as info region --region <plot #></code> - shows you all the information about a plot.<br />
<br />
<span id="department-commands"></span><br />
== Department Commands ==<br />
<br />
Each department and government institutions have unique commands. You can find these commands by running the department/institution prefix and choosing commands from the tab options.<br />
<br />
{{Note| If you are in the Department of Justice. You can view Department of Justice commands by typing <code>/doj</code> and selecting from tab-able commands.|}}<br />
<br />
[[category:Tips and Tricks]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Plots_and_regions&diff=7134Plots and regions2025-09-24T02:06:35Z<p>Goldendude15: Formatting</p>
<hr />
<div><span id="plots-regions"></span><br />
<br />
DemocracyCraft utilises Areashop (AS) for region management. <span id="wild-region"></span><br />
== Wild region ==<br />
<br />
Players can build freely in the wilderness, but some may desire protection for their bases. You can claim one region with a maximum of 4096 blocks for $10 per block. To claim a wild region at a cost of $10 per block, open a staff ticket using /ticket for wild claiming; if there are no staff online players may open a ticket in the DemocracyCraft main discord. Players may also request to staff that their wild regions be deleted, the player shall then be refunded 90% of the original price when deleted. <br />
<br />
'''*Note, players may not sell their wild plots to other players.'''<span id="urban-regions"></span><br />
== Urban regions ==<br />
<br />
There are three main types of plots within Redmont: <br />
# Commercial – Identified by the c- or cbd- tags. Only commercial buildings like stores and apartments are allowed on these plots.<br />
# Residential – Marked with the r- tag. Only houses with up to three visible floors can be built on residential plots.<br />
# Skyscraper – Denoted by the s- tag. Skyscraper plots can only have skyscrapers and are not meant for industrial or residential use.<br />
<br />
To find available plots in the city, look for reselling properties with the corresponding tags (e.g., c-000). Use <code>/as info reselling</code> to locate resold plots and use <code>/gps start [plot]</code> to get to that location.<span id="rental-regions"></span><br />
== Rental regions ==<br />
<br />
There are four main types of rental regions on the server: <br />
# Farm plot – Located in the farming town [[Willow]], these special farm regions can be rented by players (up to two per person). Denoted by the f- tag, they can be rented from the Willow Train Station. <br />
# Apartment – Some commercial buildings offer rentable apartments with prices based on the number of days. These real-life durations provide an affordable option for new players seeking a city residence.<br />
# Shop/market stall – Rentable stores are available in some regions, such as Vestire Mall, allowing players to sell items without purchasing an entire plot.<br />
# Shulker regions – Certain city and town locations have free or low-cost shulker regions with rental durations of 1-10 minutes. Intended for temporary use, such as accessing a shulker box or ender chest.<br />
<br />
You may also encounter other, less popular rental regions. To check information about a rental region, use <code>/as info region [rental region name]</code>.<span id="property-regulations"></span><br />
== Property regulations ==<br />
<br />
Upon purchasing or renting a property, you must adhere to specific regulations and laws. For owned plots, the Department of Construction and Transport (DCT) may issue eviction reports for building violations. Meanwhile, landlords may evict tenants who breach their rental agreements.<br />
<br />
For further details, consult the {{DCForums|Link=threads/rules-laws.5|Forums=Laws}} and the {{DCForums|Link=threads/plot-regulations.17|Forums=Plot Regulations}} threads.<br />
<br />
<span id="commands"></span><br />
<br />
== Commands ==<br />
<br />
* /as help – Shows this help page<br />
* /as rent – Rent a region or extend your current rent<br />
* /as unrent – Unrent a region<br />
* /as buy – Buy a region<br />
* /as sell – Sell a region<br />
* /as me – Check which regions you have and their expiration dates<br />
* /as info – Get info about current regions<br />
* /as info forsale – Regions currently for sale from the Government<br />
* /as info reselling – Regions currently for sale from other players<br />
* /as info region (region name) – Information about a particular region<br />
* /as addfriend – Grant someone building permissions<br />
* /as delfriend – Delete a friend from a region<br />
* /as resell – Put a region into resell mode<br />
* /as stopresell – Put a region back into sold mode<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Plots_and_regions&diff=7133Plots and regions2025-09-24T02:06:11Z<p>Goldendude15: Formatting</p>
<hr />
<div><span id="plots-regions"></span><br />
<br />
DemocracyCraft utilises Areashop (AS) for region management. <span id="wild-region"></span><br />
== Wild region ==<br />
<br />
Players can build freely in the wilderness, but some may desire protection for their bases. You can claim one region with a maximum of 4096 blocks for $10 per block. To claim a wild region at a cost of $10 per block, open a staff ticket using /ticket for wild claiming; if there are no staff online players may open a ticket in the DemocracyCraft main discord. Players may also request to staff that their wild regions be deleted, the player shall then be refunded 90% of the original price when deleted. '''*Note, players may not sell their wild plots to other players.'''<br />
<br />
<span id="urban-regions"></span><br />
== Urban regions ==<br />
<br />
There are three main types of plots within Redmont: <br />
# Commercial – Identified by the c- or cbd- tags. Only commercial buildings like stores and apartments are allowed on these plots.<br />
# Residential – Marked with the r- tag. Only houses with up to three visible floors can be built on residential plots.<br />
# Skyscraper – Denoted by the s- tag. Skyscraper plots can only have skyscrapers and are not meant for industrial or residential use.<br />
<br />
To find available plots in the city, look for reselling properties with the corresponding tags (e.g., c-000). Use <code>/as info reselling</code> to locate resold plots and use <code>/gps start [plot]</code> to get to that location.<span id="rental-regions"></span><br />
== Rental regions ==<br />
<br />
There are four main types of rental regions on the server: <br />
# Farm plot – Located in the farming town [[Willow]], these special farm regions can be rented by players (up to two per person). Denoted by the f- tag, they can be rented from the Willow Train Station. <br />
# Apartment – Some commercial buildings offer rentable apartments with prices based on the number of days. These real-life durations provide an affordable option for new players seeking a city residence.<br />
# Shop/market stall – Rentable stores are available in some regions, such as Vestire Mall, allowing players to sell items without purchasing an entire plot.<br />
# Shulker regions – Certain city and town locations have free or low-cost shulker regions with rental durations of 1-10 minutes. Intended for temporary use, such as accessing a shulker box or ender chest.<br />
<br />
You may also encounter other, less popular rental regions. To check information about a rental region, use <code>/as info region [rental region name]</code>.<span id="property-regulations"></span><br />
== Property regulations ==<br />
<br />
Upon purchasing or renting a property, you must adhere to specific regulations and laws. For owned plots, the Department of Construction and Transport (DCT) may issue eviction reports for building violations. Meanwhile, landlords may evict tenants who breach their rental agreements.<br />
<br />
For further details, consult the {{DCForums|Link=threads/rules-laws.5|Forums=Laws}} and the {{DCForums|Link=threads/plot-regulations.17|Forums=Plot Regulations}} threads.<br />
<br />
<span id="commands"></span><br />
<br />
== Commands ==<br />
<br />
* /as help – Shows this help page<br />
* /as rent – Rent a region or extend your current rent<br />
* /as unrent – Unrent a region<br />
* /as buy – Buy a region<br />
* /as sell – Sell a region<br />
* /as me – Check which regions you have and their expiration dates<br />
* /as info – Get info about current regions<br />
* /as info forsale – Regions currently for sale from the Government<br />
* /as info reselling – Regions currently for sale from other players<br />
* /as info region (region name) – Information about a particular region<br />
* /as addfriend – Grant someone building permissions<br />
* /as delfriend – Delete a friend from a region<br />
* /as resell – Put a region into resell mode<br />
* /as stopresell – Put a region back into sold mode<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7117Staff Guide2025-09-23T09:32:49Z<p>Goldendude15: Updated some A/S commands</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; --region &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; --region &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; --region &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
*<code>/as info region --region <region></code> - provides information about a region added to AreaShop, e.g. owner, landlord etc.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
'''Note:''' <code>--region</code> is just a part of the syntax of some areashop commands, this isn't variable :)<br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; --region &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; --region &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; --region &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment --region &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice --region &#x3C;price&#x3E; &#x3C;region&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting etc!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7116Staff Guide2025-09-23T09:04:47Z<p>Goldendude15: Formatting</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
<br />
Turns night vision for staff duties on or off. Useful for vaulting etc!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7115Staff Guide2025-09-23T09:03:50Z<p>Goldendude15: Added night vision command</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
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. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
Turns night vision for staff duties on or off. Useful for vaulting etc!<br />
* '''Commands:''' <code>/staff-nightvision on</code> <code>/staff-nightvision off</code><br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7111Staff Guide2025-09-22T09:52:30Z<p>Goldendude15: Minor edits, added that /staff-not-an-alt adds a message to the automod channel, not #notes</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in the <code>#automod</code> channel of the main discord. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
In order to keep comprehensive notes on our players that are easily accessible, we use the discord channel <code>#relations</code>. Search for the player’s full username, before creating a thread. In these threads we record evidence and general notes about players behaviours and punishments. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' <code>/spectator</code><br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7110Staff Guide2025-09-22T09:36:43Z<p>Goldendude15: Added /fly stop</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in <code>#notes</code>. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
In order to keep comprehensive notes on our players that are easily accessible, we use the discord channel <code>#relations</code>. Search for the player’s full username, before creating a thread. In these threads we record evidence and general notes about players behaviours and punishments. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' /spectator <br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code> <code>/fly off</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7109Staff Guide2025-09-22T09:33:25Z<p>Goldendude15: </p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in <code>#notes</code>. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount> <reason&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
In order to keep comprehensive notes on our players that are easily accessible, we use the discord channel <code>#relations</code>. Search for the player’s full username, before creating a thread. In these threads we record evidence and general notes about players behaviours and punishments. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' /spectator <br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Staff_Guide&diff=7108Staff Guide2025-09-22T09:19:14Z<p>Goldendude15: Updated tp commands</p>
<hr />
<div>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.<br />
<br />
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.<br />
<br />
With enough time, you might end up contributing to this guide!<br />
<br />
[[File:Staff.png|center|frameless|858x858px]]<br />
<br />
== Staff-wide Policies ==<br />
These are policies every Staff member should be familiar with!<br />
<br />
=== Career Progression and Disciplinary ===<br />
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.<br />
<br />
==== Values ====<br />
The Staff team operates on four core values<br />
<br />
# '''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.<br />
# '''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'''.<br />
# '''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.<br />
# '''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!''''<br />
<br />
==== Progression ====<br />
Staff progression is determined by a series of factors such as, but not limited to:<br />
<br />
# Activity<br />
# Character<br />
# Competence<br />
# Suitability for promotion<br />
# Engagement with the Server and it’s community<br />
# Adherence to Staff Values and Expectations<br />
# You're ability to communicate (i.e. challenging ideas, speaking up when you believe something is wrong).<br />
# Initiative (this is massive! What elevates you above your peers?)<br />
<br />
===== What staff progression is '''not''' determined by =====<br />
<br />
* Your political or business affiliations, spicy or not.<br />
* Your friendship with other staff members. Your rapport, however, will be considered.<br />
* Whether you simp for, or are politically aligned to, End or Tech.<br />
<br />
===== Who determines your progression to these ranks =====<br />
<br />
* '''All''': Your mentor will advise in if and when you are promoted.<br />
* '''Senior Administrator''': Server Leadership<br />
* '''Administrator''': Senior Staff<br />
* '''Moderator''': Administration Team+<br />
* '''Trial Moderator''': Administration Team+<br />
<br />
===== How does it work? =====<br />
<br />
# 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).<br />
# A discussion is had about the member’s suitability and other defining factors.<br />
# 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.<br />
# An outcome is reached over time or after further discussion.<br />
<br />
=== Staff Disciplinary System ===<br />
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.<br />
<br />
==== 1. Coaching ====<br />
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.<br />
<br />
==== 2. Warning ====<br />
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).<br />
<br />
==== 3. Notice to Show Cause (NTSC) ====<br />
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.<br />
<br />
=== Duties and Expectations ===<br />
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.<br />
<br />
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.<br />
{| class="wikitable"<br />
!<br />
!Corporate Management<br />
!Systems Management<br />
!Mentor/Monitor Administrators<br />
!Mentor/Monitor Moderators<br />
!Staff Dispute Resolution<br />
!Player Dispute Resolution<br />
!Manage Forums<br />
!Manage Server<br />
!Staff Application Verdicts<br />
!Manage Permissions<br />
!Conduct Rollbacks<br />
!Discord Roles<br />
!Spawn Items<br />
!Regioning<br />
!Vaulting<br />
!Player Support/Tickets<br />
|-<br />
|Server Leadership<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Senior Staff<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Administrators<br />
|<br />
|<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|✅<br />
|-<br />
|Moderators<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|✅<br />
|<br />
|✅<br />
|✅<br />
|✅<br />
|}<br />
<br />
==== Expectations ====<br />
<br />
* 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.<br />
* Be integral. Don’t steal. Don’t lie.<br />
* We all make mistakes and we learn through them. Don’t try and cover them up, it doesn’t help anyone!<br />
* If you aren’t sure, ask your fellow staff members!<br />
* Approach tickets in a timely, friendly, and helpful manner.<br />
* Respect and value the advice of staff that are senior to you.<br />
* Staff permissions are used for tickets while assisting other players only.<br />
* Be positive! - Smile :)<br />
<br />
== For Managers ==<br />
=== Panel Access ===<br />
Managers are responsible for adding Senior Administrators and Administrators to our server control panel. To add a user, follow the steps below.<br />
<br />
# Open the <code>DemocracyCraft</code> server.<br />
# Navigate to <code>Users</code> and click <code>New User</code>.<br />
# Enter the Staff member’s email address, and select <code>Manage</code> under <code>Subdomain</code>. This is a temporary permission.<br />
# You will now notice a new user entry, on the right-hand side next to the bin click on <code>Import user permissions</code>.<br />
# Grab the list of permissions in the next section below, that corresponds to the Staff member’s rank in the team.<br />
# Paste it in the input box, and click <code>Import</code>.<br />
# Repeat Steps 2-6 after opening the <code>DemocracyCraft Playground</code> server.<br />
# Great work! All done. :)<br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Remind the Staff member that all activities are logged, and that we have a mandatory two factor authentication requirement!}}<br />
<br />
==== Ranks and Privileges ====<br />
===== Senior Administrators =====<br />
<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><br />
<br />
===== Administrators =====<br />
<pre>[&quot;control.read-console&quot;,&quot;control.console&quot;,&quot;control.start&quot;,&quot;control.restart&quot;,&quot;file.create&quot;,&quot;file.read&quot;,&quot;file.read-content&quot;,&quot;file.update&quot;,&quot;file.archive&quot;,&quot;recycle.read&quot;,&quot;recycle.restore&quot;,&quot;backup.create&quot;,&quot;backup.read&quot;,&quot;database.read&quot;,&quot;schedule.read&quot;,&quot;activity.read&quot;,&quot;websocket.connect&quot;,&quot;control.stop&quot;,&quot;allocation.read&quot;,&quot;startup.read&quot;]</pre><br />
<br />
== For Senior Administrators ==<br />
=== Console ===<br />
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.<br />
{{Note|text=<b>Note</b><br><br />
There is no one set way of learning how to do these things. <br />
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=<b>Tip</b><br><br />
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!}}<br />
<br />
== For System Administrators ==<br />
=== Resetting the Nether and End ===<br />
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.<br />
<br />
==== Steps ====<br />
<br />
# Try to make an announcement in #server-announcements one week away for the desired data.<br />
#* 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!<br />
<br />
# Turn on the whitelist via <code>/whitelist on</code> to ensure those pesky players stay out of our way.<br />
# Delete both Reveille_nether and Reveille_the_end using <code>/mw delete &#x3C;world&#x3E;</code>.<br />
# Recreate both Reveille_nether and Reveille_the_end using <code>/mw create &#x3C;world&#x3E;</code>.<br />
# 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>.<br />
# Merge inventories between the worlds by running <code>/mw inventory merge Reveille Reveille_nether Reveille_the_end Wilderness NewHamilton</code>.<br />
# Have a staff member check that keeping inventory is off, and that death messages don’t show in the Nether and End respectively.<br />
# Link nether portals correctly via <code>/world netherportal destination Reveille_nether Wilderness</code> and <code>/world netherportal destination Wilderness Reveille_nether</code>.<br />
# Run <code>/mw gamemode survival Reveille_the_end</code> and <code>/mw gamemode survival Reveille_nether</code> in Console (without the slash!).<br />
# Turn off the server.<br />
# 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)<br />
# 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)<br />
# Start the server.<br />
# Open the server back up by removing the whitelist. (<code>/whitelist off</code>).<br />
# Announce the change in #server-announcements!<br />
<br />
=== Red v. Blue Event Guide for Staff ===<br />
<br />
==== 1. Purge old teams ====<br />
<br />
# Run the following commands in Console, noting that you will be prompted to confirm these commands with a follow up command.<br />
## <code>lp bulkupdate all delete &#x22;permission == group.blue&#x22;</code><br />
## <code>lp bulkupdate all delete &#x22;permission == group.red&#x22;</code><br />
<br />
==== 2. Setting up Team Selection ====<br />
<br />
# Identify where the team selection block will be, to do this please ask the Department of Public Affairs.<br />
# Run <code>/mycmd-blockset create</code> while looking at the target block.<br />
# Run <code>/mycmd-blockset add /redblue</code> while still looking at the target block.<br />
<br />
==== 3. Team Verification / Checks ====<br />
<br />
# You should be able to see the teams displayed on TAB<br />
# Make sure that it is assisnging the teams at random through the GUI.<br />
# Announce the change in #changelog!<br />
<br />
==== 4. Post Event Checks ====<br />
<br />
# Create and provide rewards to the DPA.<br />
# Purge teams again, by following Step 1.<br />
<br />
== For Administrators ==<br />
=== How to manage Billboards ===<br />
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!<br />
[[File:Google_imagemap_example.png|thumb|Here is an example of a pasted image.]]<br />
<br />
==== Steps ====<br />
<br />
# Upload your image to an image hosting service such as [http://imgur.com/ Imgur] or [https://imgbb.com/ ImgBB]<br />
# Download the image in-game by running <code>/imagemap download &#x3C;filename&#x3E; &#x3C;sourceURL&#x3E;</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with an easy to identify name, without any file extensions such as <code>.png</code>.<br />
#* Replace <code>&#x3C;sourceurl&#x3E;</code> with a link to the image, this '''should include''' the file extension such as <code>.png</code>.<br />
# Place the image in-game by running <code>/imagemap place &#x3C;filename&#x3E; [frameInvisible] [frameFixed] [frameGlowing] [size]</code><br />
#* Replace <code>&#x3C;filename&#x3E;</code> with the file name you selected in Step 2. Please add the file extension featured in the <code>&#x3C;sourceurl&#x3E;</code> you used earlier.<br />
#* 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.<br />
#* Replace <code>[frameFixed]</code> with “true”, no quotation marks. This ensures a clean removal of the image by punching the item frames in creative.<br />
#* Replace <code>[frameGlowing]</code> with “false”, no quotation marks. This the frames are not glowing.<br />
#* Replace <code>[size]</code> the height (A) and width (A) in the following format: AxB<br />
#** i.e. for a 2 by 2 image, it would be: <code>2x2</code><br />
# Admire your work!<br />
<br />
=== Understanding your Forums Privilages ===<br />
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.<br />
<br />
You can login to the control panel with the same credentials you use for the forums [https://www.democracycraft.net/admin.php here]<br />
<br />
==== User Confidentiality ====<br />
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.<br />
<br />
==== User Role Management ====<br />
{{Note|type=error|text=<b>Attention</b><br><br />
<b>Never</b> update a user’s primary group. It should always be <code>Registered</code>.}}<br />
[[File:Registered_group.png|902x902px]]<br />
<br />
When updating groups, all you should be modifying are <code>Secondary Groups</code>. '''Do not modify regular Department or otherwise automated roles (jobs).'''<br />
<br />
<br />
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.<br />
<br />
[[File:Secondary_group.png|898x898px]]<br />
<br />
==== Broken Role Syncing ====<br />
When a player’s roles are not syncing properly, here are three simple steps you can do to fix this.<br />
{{Note|type=reminder|text=<b>Reminder</b><br><br />
Make sure the player has linked their in-game account to their Forums account first! They can do <b>/register</b> any time to confirm this.}}<br />
<br />
===== Steps =====<br />
<br />
# Remove all their Secondary Group Roles (excluding Staff roles!)<br />
# Ask them to log in, wait 5 minutes, then log out.<br />
# Ask them to log back in after 2-3 seconds<br />
<br />
=== How to conduct Rollbacks ===<br />
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.<br />
<br />
==== Commands ====<br />
<br />
* <code>/co help</code> - help command; displays all commands.<br />
* <code>/co rb; /co rollback</code> - rollback block data based on certain parameters.<br />
** '''Usage:''' <code>/co rb u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code><br />
* <code>/co undo</code> - revert a rollback.<br />
<br />
You can see a list of parameters for these commands [[Staff Guide#coreprotect-parameters|here]].<br />
<br />
==== Additional Information ====<br />
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.<br />
<br />
=== How to manage VPN Bypasses ===<br />
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.<br />
<br />
==== VPN ====<br />
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].<br />
<br />
If you offer this option, please provide the player with the <code>antivpn.bypass</code> permission node in-game.<br />
<br />
=== Administrative Commands ===<br />
These are useful commands to know with your position.<br />
<br />
==== LuckPerms ====<br />
<br />
* <code>/lp; /luckperms; /perm; /perms: /permissions</code> - Main alias. Put these before any LuckPerms command.<br />
* <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.<br />
** <code>[type]</code> - the types to include in the editor session. can be <code>all</code>, <code>users</code> or <code>groups</code>.<br />
<br />
===== User Commands =====<br />
<br />
* <code>/lp user &#x3C;user&#x3E; info</code><br />
* <code>/lp user &#x3C;user&#x3E; permission</code><br />
* <code>/lp user &#x3C;user&#x3E; parent</code><br />
* <code>/lp user &#x3C;user&#x3E; meta</code><br />
* <code>/lp user &#x3C;user&#x3E; editor</code><br />
* <code>/lp user &#x3C;user&#x3E; promote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; demote &#x3C;track&#x3E; [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; showtracks</code><br />
* <code>/lp user &#x3C;user&#x3E; clear [context...]</code><br />
* <code>/lp user &#x3C;user&#x3E; clone &#x3C;user&#x3E;</code><br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
Add in-game roles via <code>/lp user &lt;user&gt; parent add &lt;job&gt;</code>}}<br />
<br />
===== Group Commands =====<br />
<br />
* <code>/lp group &#x3C;group&#x3E; info</code><br />
* <code>/lp group &#x3C;group&#x3E; permission</code><br />
* <code>/lp group &#x3C;group&#x3E; parent</code><br />
* <code>/lp group &#x3C;group&#x3E; meta</code><br />
* <code>/lp group &#x3C;group&#x3E; editor</code><br />
* <code>/lp group &#x3C;group&#x3E; listmembers [page]</code><br />
* <code>/lp group &#x3C;group&#x3E; setweight &#x3C;weight&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; setdisplayname &#x3C;name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; showtracks</code><br />
* <code>/lp group &#x3C;group&#x3E; clear [context...]</code><br />
* <code>/lp group &#x3C;group&#x3E; rename &#x3C;new name&#x3E;</code><br />
* <code>/lp group &#x3C;group&#x3E; clone &#x3C;name of clone&#x3E;</code> <br />
<br />
===== General ===== <br />
<br />
* <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.<br />
* <code>/socialspy</code> - able to see players private messages.<br />
<br />
===== Crates =====<br />
<br />
* You can replace players' crate keys by running <code>/crate key give &#x3C;user&#x3E; &#x3C;crate&#x3E;</code> .<br />
<br />
== For Moderators == <br />
Here is everything a Moderator needs to know! <br />
<br />
=== Managing Players === <br />
Players are tricky business but shouldn’t be feared - after all you are one! Here are some guides on scenarios and managing behaviour. <br />
<br />
See also: [[Issuing Punishments|Punishment Guide]] <br />
<br />
==== How to check for Alternative Accounts ==== <br />
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. <br />
<br />
{{Note|type=info|text=<b>Information</b><br><br />
Players who have alternative accounts will receive all of the punishments associated on their main account. The alternative accounts should be banned.}} <br />
<br />
===== 1. Assessing ===== <br />
When someone first joins the server, our punishments plugin automatically runs a check on them (the same thing can be achieved with <code>/alts &#x3C;username&#x3E;</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. <br />
<br />
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>#relations</code> to see if they have passed the alternative accounts test before. If they haven’t, make a note in <code>#relations</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. <br />
<br />
[[File:Flagged_alt_account_examples.png|1291x1291px]]<br />
<br />
===== Testing ===== <br />
If both accounts are online you can first try conducting the movement test. <br />
<br />
# You can warp yourself and the other players to the testing area using <code>/staff-alttest <player1> <player2></code><br />
# 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.<br />
# Ask one player to run on the pink line and the other on the blue line.<br />
# You then look to verify that both accounts are making independent movements from one another (they are both moving at the same time).<br />
<br />
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; <br />
<br />
# One of the players is not moving or moving every so often<br />
# Only one player moves at a time<br />
# One is uncooperative with the test (not responding to anything)<br />
# One or both accounts log off and do not return after a while.<br />
<br />
However, if the players pass, you can run <code>/staff-notanalt &#x3C;username 1&#x3E; &#x3C;username 2&#x3E;</code> and it will remove the warning and add a message in <code>#notes</code>. <br />
<br />
You can also return players back to spawn using <code>/staff-sendtospawn <player></code> <br />
<br />
Additionally, you could go into <code>/spectator</code> and <code>/staff-tp</code> to them to further investigate/watch their movements to verify that they aren’t alts. <br />
<br />
=== Understanding Basics === <br />
==== WorldGuard ==== <br />
<br />
* <code>/rg define &#x3C;name&#x3E;</code> - Creates a region.<br />
* <code>/rg remove &#x3C;region&#x3E;</code> - Removes the specified region.<br />
* <code>/rg redefine &#x3C;name&#x3E;</code> - Re-sets an existing region to your current selection.<br />
* <code>/rg setparent &#x3C;region&#x3E; &#x3C;parent&#x3E;</code> - Sets the specified region to be a child of the second given region. Used for when creating apartment regions.<br />
** Ex.: <code>/rg setparent ExampleRegion dc-001</code> - Sets dc-001 as the parent of region ExampleRegion<br />
<br />
<br />
Here is a basic rundown of some flags you might come across or may need to add/change.<br />
{| class="wikitable"<br />
|+Flags<br />
!Flag<br />
!Type<br />
!description<br />
!<br />
|-<br />
|build<br />
|state<br />
|Everything:<br />
<br />
* Whether blocks can be mined or placed<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether entities and blocks can be interacted with<br />
* Whether player versus player combat is permitted<br />
* Whether sleeping in a bed is permitted<br />
* Whether inventories can be accessed<br />
* Whether vehicles (boats, minecarts) can be placed<br />
* etc.<br />
|<br />
|-<br />
|interact<br />
|state<br />
|Everything that involves ‘using’ a block or entity:<br />
<br />
* Whether doors, levers, etc. (but not inventories) can be used<br />
* Whether vehicles (including animals) can be mounted<br />
* etc.<br />
|<br />
|-<br />
|block-break<br />
|state<br />
|Whether blocks can be broken<br />
|<br />
|-<br />
|block-place<br />
|state<br />
|Whether blocks can be placed<br />
|<br />
|-<br />
|use<br />
|state<br />
|Whether doors, levers, etc. (but not inventories) can be used<br />
|<br />
|-<br />
|damage-animals<br />
|state<br />
|Whether players can harm friendly animals (cows, sheep, etc)<br />
|<br />
|-<br />
|chest-access<br />
|state<br />
|Whether inventories can be accessed<br />
|<br />
|-<br />
|ride<br />
|state<br />
|Whether vehicles (including animals) can be mounted<br />
|<br />
|-<br />
|pvp<br />
|state<br />
|Whether player versus player combat is permitted<br />
|<br />
|-<br />
|sleep<br />
|state<br />
|Whether sleeping in a bed is permitted<br />
|<br />
|-<br />
|respawn-anchors<br />
|state<br />
|Whether respawn anchors can be activated<br />
|<br />
|-<br />
|tnt<br />
|state<br />
|Whether TNT detonation or block damage is permitted<br />
|<br />
|-<br />
|vehicle-place<br />
|state<br />
|Whether vehicles (boats, minecarts) can be placed<br />
|<br />
|-<br />
|vehicle-destroy<br />
|state<br />
|Whether vehicles can be destroyed<br />
|<br />
|-<br />
|lighter<br />
|state<br />
|Whether flint and steel or a fire charge can be used<br />
|<br />
|-<br />
|block-trampling<br />
|state<br />
|Whether farmland and turtle or sniffer eggs can be trampled<br />
|<br />
|-<br />
|frosted-ice-form<br />
|state<br />
|Whether players with frost walker boots will form ice<br />
|<br />
|-<br />
|item-frame-rotation<br />
|state<br />
|Whether items can be rotated within item frames<br />
|<br />
|-<br />
|firework-damage<br />
|state<br />
|Whether fireworks can deal damage to entities<br />
|<br />
|-<br />
|use-anvil<br />
|state<br />
|Whether anvils can be used<br />
|<br />
|-<br />
|use-dripleaf<br />
|state<br />
|Whether dripleaf can be used<br />
|<br />
|}<br />
For more information, please check out [https://worldguard.enginehub.org/en/latest/regions/flags/ WorldGuard’s Documentation]. <br />
<br />
==== WorldEdit ==== <br />
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. <br />
<br />
It may seem like a lot to learn at first, however it’s quite straight forward after a bit of time and experience. <br />
<br />
===== Getting Started =====<br />
<br />
====== Making a selection ======<br />
A cuboid is like 3D rectangle. In WorldEdit, you select the region that you want by setting two points of a cuboid. <br />
<br />
====== How do you choose the two points? You can… ====== <br />
<br />
* Left and right click blocks while holding a wooden axe (use <code>//wand</code> to get a wooden axe)<br />
* Stand somewhere and enter <code>//pos1</code> and <code>//pos2</code><br />
* Look at a block and enter <code>//hpos1</code> and <code>//hpos2</code> <br />
<br />
===== Commands ===== <br />
<br />
* <code>//wand</code> - gives you a World Edit tool.Left click a block while holding it to make your first selectionRight click a block while holding it to make your second selection<br />
* <code>//wandoff</code> - takes away a World Edit tool from your inventory.<br />
* <code>//cut</code> - copies and clears your current selection.<br />
* <code>//paste</code> - pastes your previous cut selection.<br />
* <code>//expand &#x3C;amount&#x3E; [direction]</code> - makes your current selection expand by the amount specified in the specified direction.<br />
** Amount is either specfified as a number or <code>vert</code> (infinitely vertical).<br />
* <code>//calc</code> - short for ‘calculate’. Allows you to do equations in-game. Example: <code>//calc 100*7</code><br />
* <code>//sel [poly/cuboid]</code> - select the type of region.<br />
** <code>Cuboid</code> is the '''default''' selection type; basic two point selection<br />
** Left click a block to set first selection<br />
** Right click a block to set a second selection.<br />
** Poly is the '''advanced''' selection type.<br />
** Left click a block to set first selection<br />
** Right click a block to set a second, third, fourth, etc. selection<br />
* <code>//sel</code> - when used like this this command will clear your current selection.<br />
* <code>//rotate &#x3C;degrees&#x3E;</code> - rotates your current clipboard (cut/copy) the specified degrees.<br />
** Degrees have to be in multiples of 90 or it won’t work.<br />
** 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>.<br />
* <code>//move &#x3C;amount of blocks&#x3E; [direction]</code> - moves your current selection by the amount specified in the specified direction.<br />
* <code>/expand &#x3C;number&#x3E; [direction]</code> - modifies your selection in the direction specified by the amount of blocks specific. <br />
<br />
====== Directions can be… ====== <br />
<br />
* '''Relative to the world'''<br />
** i.e. <code>up</code>, <code>down</code>, <code>north</code>, <code>east</code>, <code>south</code>, <code>west</code>.<br />
* '''Relative to the player'''<br />
** i.e. <code>forward</code>, <code>back</code>, <code>left</code>, and <code>right</code>. <br />
<br />
If a direction is ommited from the command, the region will expand in the direction the player is looking. <br />
<br />
'''Examples:''' <br />
<br />
* <code>//expand 6</code> - Expand 6 blocks in the direction you’re facing <br />
* <code>//expand 10 up</code> - Expand 10 blocks upwards <br />
* <code>//expand vert</code> - Expand the region selection from bedrock to the sky. Do '''not''' use when making rentable regions (i.e. apartment rooms)<br />
<br />
You can learn more by reading the [https://worldedit.enginehub.org/en/latest/usage/ WorldEdit 7.2 documentation]<br />
<br />
==== AreaShop Basics ==== <br />
AreaShop is essentially a real estate plugin for world guard regions, allowing us to sell and rent them. <br />
<br />
* '''These are only basic commands, further down are sections dedicated to regioning.''' <br />
<br />
===== Commands ===== <br />
<br />
* <code>/as add &#x3C;buy/sell&#x3E; &#x3C;region&#x3E;</code> - makes a region either a buyable or rentable region.<br />
** Used when making wilderness or apartment/shop regions. <br />
{{Note|text=<b>IMPORTANT</b><br><br />
You must <b>always</b> specify the shop/apartment’s region name when making it rentable, otherwise you might accidentally put a plot for sale/rent.}}<br />
* <code>/as del &#x3C;region&#x3E;</code> - deletes the specified region from AreaShop.<br />
* <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> - used to set the selling/renting price of an AreaShop region.<br />
* <code>/as setlandlord &#x3C;name&#x3E; &#x3C;region&#x3E;</code> - used to set the landlord of an Areashop region.<br />
** Wilderness regions will always have the landlord be <code>“DCGovernment</code><br />
** Apartment and/or shop regions, will have the owner of the parent region be the landlord unless told otherwise.<br />
* <code>/as setowner &#x3C;player&#x3E; &#x3C;region&#x3E;</code> - used for when transferring ownership of a region to another player.<br />
* <code>/as addsign &#x3C;region&#x3E;</code> - used to add an Areashop sign to the sign you’re looking at.<br />
* <code>/as delsign</code> - used to delete the Areashop sign you’re looking at.<br />
* <code>/as tp &#x3C;region&#x3E;</code> - Teleports you to the specified Area Shop region.<br />
** Sometimes this command can teleport you to an underground cave, If this happens, just use /top to get above ground.<br />
** Don’t use this for personal transportation to your regions.<br />
* <code>/as info player &#x3C;player&#x3E;</code> - lists all of the regions the specified player owns or is added to. Sometimes doesn’t work.<br />
** An alias of this command is <code>/as me &#x3C;player&#x3E;</code>.<br />
* <code>/staff-getsign</code> - gives you a sign which you can use to make AreaShop signs.<br />
** Can also be used to label chests/buildings when vaulting.<br />
* <code>/staff-getwool</code> - gives you wool which you can use for selection points. <br />
<br />
=== How-tos === <br />
==== Managing disputes ==== <br />
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. <br />
<br />
===== Solve problems as early as possible at the lowest level ===== <br />
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. <br />
<br />
===== Steer clear of drama ===== <br />
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. <br />
<br />
===== Evidence ===== <br />
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. <br />
<br />
===== There are two sides to every story ===== <br />
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. <br />
<br />
==== Searching for Items ==== <br />
We use Coreprotect to log all of block interactions. This allows us to lookup certain interactions. <br />
<br />
===== Commands ===== <br />
<br />
* <code>/co l; /co lookup</code> - used to lookup specific block data.<br />
* <code>/co l u:&#x3C;user&#x3E; t:&#x3C;time&#x3E; r:&#x3C;radius&#x3E; a:&#x3C;action&#x3E; b:&#x3C;blocks&#x3E; e:&#x3C;exclude&#x3E;</code> <br />
<br />
==== Using CoreProtect Parameters ====<br />
These can be used in almost every CoreProtect command. <br />
<br />
==== <code>u:&#x3C;user&#x3E;</code> ==== <br />
<br />
* Specify a user to rollback. Example: u:Technofied <br />
<br />
==== <code>t:&#x3C;time&#x3E;</code> ==== <br />
Specify the amount of time to rollback. You can specify weeks, days, hours, minutes and seconds. '''Example:''' t:2w,5d,7h,2m,10s <br />
<br />
You can pick and choose time amounts. '''Example:''' t:5d2h You can also use decimals '''Example:''' t:2.50h (2 and a half hours) <br />
<br />
==== <code>r:&#x3C;radius&#x3E;</code> ==== <br />
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>) <br />
<br />
For example, the following would only rollback damage within 10 blocks of where you are standing: <code>r:10</code> <br />
<br />
==== <code>a:&#x3C;action&#x3E;</code> ==== <br />
Restrict the rollback to a certain action. '''Example:''' If you wanted to only rollback blocks placed, you would use <code>a:+block</code>. <br />
<br />
'''Here’s a list of all the actions:''' <br />
<br />
* <code>a:block</code> - blocks placed/broken <br />
* <code>a:+block</code> - blocks placed <br />
* <code>a:-block</code> - blocks broken <br />
* <code>a:chat</code> - messages sent in chat <br />
* <code>a:click</code> - player interactions<br />
* <code>a:command</code> - commands used <br />
* <code>a:container</code> - items taken from or put in chests <br />
* <code>a:+container</code> - items put in chests <br />
* <code>a:-container</code> - items taken from chests <br />
* <code>a:inventory</code> - items dropped or picked up by players <br />
* <code>a:+inventory</code> - items picked up by players <br />
* <code>a:-inventory</code> - items dropped by players <br />
* <code>a:item</code> - items dropped, picked up, taken from, or put in chests <br />
* <code>a:+item</code> - items picked up or put in chests <br />
* <code>a:-item</code> - items dropped or taken from chests <br />
* <code>a:kill</code> - mobs/animals killed <br />
* <code>a:session</code> - player logins/logouts <br />
* <code>a:+session</code> - player logins <br />
* <code>a:-session</code> - player logouts <br />
* <code>a:sign</code> - messages written on signs <br />
* <code>a:username</code> - username changes <br />
<br />
==== <code>b:&#x3C;blocks&#x3E;</code> ==== <br />
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 <br />
<br />
==== <code>e:&#x3C;exclude&#x3E;</code> ====<br />
Exclude certain block types from the rollback.<br />
<br />
'''Example:''' If you don’t want TNT to come back during a rollback, you would type e:46 <br />
<br />
==== <code>#&#x3C;hashtag&#x3E;</code> ====<br />
Add a hashtag to the end of your command to perform additional actions.<br />
<br />
'''Example:''' To perform a rollback preview, you would use <code>#preview</code> <br />
<br />
'''Here is a list of all available hashtags''' <br />
<br />
* <code>#preview</code> - preview a rollback/restore <br />
* <code>#verbose</code> - display additional information during a rollback/restore <br />
* <code>#silent</code> - display minimal information during a rollback/restore <br />
<br />
==== Merging regions ==== <br />
Players may merge certain regions to allow for larger plots, provided that they own two or more neighbouring regions.<br />
<br />
{{Note|type=error|text=<b>IMPORTANT</b><br><br />
<br />
Do NOT delete a region, or overlap another one whole. Only overlap the boundaries.}} <br />
<br />
===== Merging =====<br />
To merge a region is quite simple - all that is required is to redefine a region over the plot divider with <code>/rg redefine &#x3C;plot&#x3E;</code>. See below for an example.<div class="figure"><br />
[[File:Merge_regions_example.png|553x553px]]<br />
</div> <br />
<br />
===== What can be merged? ===== <br />
You can merge any commercial and industrial plots. Residential, CBD, and any other special plots are '''NOT''' to be merged. <br />
<br />
==== Urban Regioning ==== <br />
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.|}} <br />
<br />
===== Step by Step Guide ===== <br />
<br />
* '''1.1 Creating the WorldGuard region and fining the player.'''<br />
** After selecting the points for the region you can define the region to create it.<br />
** The owner of the building may choose the name of the region.<br />
** '''Command:''' <code>/rg define &#x3C;regionName&#x3E;</code>.<br />
*** i.e. <code>/rg define EndStore1</code>.<br />
* '''1.2 Make sure to fine the player for the creation of each region.'''<br />
** Each region costs $25 to create excluding shulker regions, those are free.<br />
** '''Command:''' <code>/fine &#x3C;user&#x3E; &#x3C;amount&#x3E;</code>.<br />
*** Select “Staff” as the account to send the fine to.<br />
*** i.e. <code>/fine xEndeavour 25</code>.<br />
* '''2.0 Setting the region parent.'''<br />
** 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.<br />
** The parent is the plot the room will inherit permissions from.<br />
** Setting the room’s parent will allow the plot owner and any other members of the plot to modify within the rooms.<br />
** '''Command:''' <code>/rg parent &#x3C;regionName&#x3E; &#x3C;PlotRegion&#x3E;</code>.<br />
*** i.e. <code>/rg parent EndStore1 c001</code>.<br />
* '''3.0 Adding the region to AreaShop'''<br />
** 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.<br />
** '''Command:''' <code>/as add rent &#x3C;regionName&#x3E;.</code><br />
* '''3.1 Set the landlord'''<br />
** '''Command:''' <code>/as setlandlord &#x3C;landlord&#x3E; &#x3C;regionName&#x3E;</code>, this usually is the player who is creating the region.<br />
* '''3.2 Set the price'''<br />
** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;regionName&#x3E;</code><br />
* '''3.3 Set the duration'''<br />
** '''Command:''' <code>/as setduration &#x3C;duration&#x3E; &#x3C;region&#x3E;</code><br />
* '''4.0 Adding an AreaShop sign'''<br />
** 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>.<br />
** After you get a sign, you can place it somewhere outside of the door/front of the region where any player can access.<br />
** The player will usually show you where they want the signs.<br />
** After the sign is placed look at it and use the command: <code>/as addsign &#x3C;regionName&#x3E;</code>, this will make the sign interactive and add the region’s information to it.<br />
* '''5.0 Quality Checks'''<br />
** Check the priority of the region is 30 or above via <code>/rg info &#x3C;regionName&#x3E;</code> - if not click on the priority and type in 30.<br />
** Make sure to get rid of the wool that you placed, don’t leave anything behind.<br />
<br />
===== Using the sign-based method ===== <br />
If you prefer doing region creation through signs, try [https://github.com/NLthijs48/AreaShop/wiki/Basic-regions-setup#rental-region this]! <br />
<br />
==== Wild Regioning ==== <br />
Wilderness regions are private wild plots that any players can obtain. It costs $10/block to claim land in the wilderness.{{Danger||Please note the following: - Players may only have '''one''' wild region up to '''4096 blocks''' in their wild region, and unless given permission, your region needs to be at least 20 blocks away from another player’s region.|}} <br />
<br />
===== Step By Step Guide ===== <br />
<br />
* '''1.0 Getting the price for the region'''<br />
** To get the price, you’re going to use your wand to select two corners but make sure they are on the same height (y level).<br />
** This will give you the total number of blocks within your selection<br />
** After this, multiply the total block number by 10 to get the price.<br />
** '''Command:''' <code>//calc &#x3C;totalblocks&#x3E;*10</code> <br />
<br />
<div class="figure"><br />
[[File:Wild_price_calculation_example.png|778x778px]]<br />
</div> <br />
<br />
* '''2.0 Seeing if the player can afford it'''<br />
** After getting the total price of the land, check the player’s balance to see if they can afford it.<br />
** Command: <code>/bal &#x3C;player&#x3E;</code><br />
** '''If they have enough money''', tell them the price and ask if it’s okay.<br />
** '''If they don’t have enough money''', let them know, maybe they’ll have money in their companies. <br />
*** Otherwise, offer to resize the selection.<br />
* '''3.0 Creating the WorldGuard region'''<br />
** Now that we have the region selected and we know the player can afford it, it’s time to define the region.<br />
** '''Command:''' <code>/rg define &#x3C;playerName&#x3E;</code><br />
*** i.e. <code>/rg define Technofied</code> <br />
{{Note|type=info|text=<b>Information</b><br><br />
All wild regions should have the same naming convention: <code><playerName></code>}}<br />
* '''4.0 Adding the region to AreaShop'''<br />
** After you’ve created the WorldGuard region, it’s now time to make it buyable.<br />
** '''4.1 Add the region'''<br />
*** '''Command:''' <code>/as add buy &#x3C;regionName&#x3E;</code><br />
** '''4.2 Set the landlord'''<br />
*** '''Command:''' <code>/as setlandlord DCGovernment &#x3C;region&#x3E;.</code><br />
** '''4.3 Set the price'''<br />
*** '''Command:''' <code>/as setprice &#x3C;price&#x3E; &#x3C;region&#x3E;</code> <br />
{{Note|type=reminder|text=<b>Tip</b><br><br />
<br />
Let the player know to not buy the region until you tell them to! Some people buy regions too soon, and if that happens you would need to correct how much they’ve paid.}}<br />
<br />
===== Expanding a region ===== <br />
Lets say a player already has a wild region, but would like to expand it. <br />
<br />
* '''1.0 Getting the price for the new region'''<br />
** Select two corners of the new area the player would like their region to be expanded to.<br />
** Note the number of blocks, and multiply it by 10 to get the total cost of the expansion and subtract it by the old region’s price.<br />
* '''2.0 Check if the player can afford it'''<br />
** '''Command:''' <code>/bal &#x3C;player&#x3E;</code> - ask if the player is okay with the price.<br />
* '''3.0 Fine the player the cost (after the subtraction)'''<br />
** '''Command:''' <code>/fine &#x3C;player&#x3E; &#x3C;amount&#x3E;</code> - this will open a menu up and the option of <code>Staff</code> should be selected.<br />
* '''4.0 Re-define the region to include BOTH their initial region AND their expanded area'''<br />
** Select the old region via <code>/rg select &#x3C;region&#x3E;</code><br />
** Expand it into the new region with WorldEdit.<br />
** Redefine region into the new size via <code>/rg redefine &#x3C;region&#x3E;</code>.<br />
<br />
== For Everyone == <br />
==== Note taking ==== <br />
In order to keep comprehensive notes on our players that are easily accessible, we use the discord channel <code>#relations</code>. Search for the player’s full username, before creating a thread. In these threads we record evidence and general notes about players behaviours and punishments. <br />
<br />
=== How and when to action warrants === <br />
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.<br />
<br />
{{Note|type=warn|text=<b>Warning</b><br><br />
<br />
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.}} <br />
<br />
==== Eligibility ==== <br />
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. <br />
<br />
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. <br />
<br />
==== Protecting Staff Information ==== <br />
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. <br />
<br />
==== Who can request what ==== <br />
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! <br />
<br />
=== Everything Senior Vice Presidents (SVPs) === <br />
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. <br />
<br />
==== Elections ==== <br />
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! <br />
<br />
===== SVP Election Months ===== <br />
<br />
* January<br />
* March<br />
* June<br />
* September<br />
* November <br />
<br />
==== SVP Morale ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Organise Staff events<br />
* Help others organise Staff events<br />
* Organise Staff competitions <br />
<br />
==== SVP Links ==== <br />
As the SVP Links, you hold the prestigious title of the Discord’s Master Linker. Your mission: to manage the #links channel, the gateway to wider DC platforms. Bring your expertise in hyperlinking and attention to detail to keep the channel organised. <br />
<br />
===== Responsibilities: ===== <br />
Keep the #links channel up-to-date <br />
<br />
==== SVP Talent (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* 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.<br />
** Can be posted by anyone, you just make sure its happening. <br />
<br />
==== SVP Justice (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities: ===== <br />
<br />
* 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<br />
* 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).<br />
* Sends verdict in game via staff command. <br />
<br />
==== SVP Retention (Administrators+) ==== <br />
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. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Gather information on most wanted features. Come up with your own ideas that would help with player retention<br />
* Implement those ideas either with Staff help or Department of Education (depending on the feature)<br />
* Most new features require both Staff and DOE engagement, so you will be the person who encourages and helps both teams.<br />
* 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 :)). <br />
<br />
==== SVP History ==== <br />
As SVP History, you are the owner of the Staff/Server museum. <br />
<br />
===== Responsibilities ===== <br />
<br />
* Keep the Staff/Server museum up-to-date<br />
* Keep the tutorial staff wall up-to-date <br />
<br />
=== Commands === <br />
Here are a list of commands that all Staff members have access to. Remember that they are only for Staff duties, and nothing is for personal benefit! <br />
<br />
==== Vanish ==== <br />
You’re able to become invisible to all non-staff players, and seen as in spectator mode on tab to other staff as a physical floating head. <br />
<br />
* This can be used in multiple situations: <br />
** Watching for suspicious illegal activity <br />
** Getting away from players if feeling overwhelmed <br />
* '''Commands:''' <code>/vanish; /v</code> - Silently puts you into vanish mode and notifies other Staff members.<br />
<br />
<br />
==== Inventory ==== <br />
You can open players’ inventory in real time. <br />
<br />
* Used to take items out of a player’s inventory if they’re not supposed to have it, or in the case something is accidentally (or maliciously) stolen.<br />
* '''Commands:''' <code>/openinv &#x3C;player&#x3E;; /oi</code><br />
<br />
<br />
==== Ender Chests ==== <br />
Opens the specified player’s enderchest in real time. <br />
<br />
* '''Commands:''' <code>/openender &#x3C;player&#x3E;; /oe</code> <br />
<br />
==== Teleportation ==== <br />
Teleports the specified player to spawn. <br />
<br />
* Used if a player seems to be stuck from glitching.<br />
* '''Commands:''' <code>/staff-sendtospawn &#x3C;player&#x3E;</code><br />
<br />
<br />
Teleport the player to another player<br />
<br />
* '''Commands:''' <code>/tp2p &#x3C;player&#x3E; [player]</code> <br />
<br />
<br />
Teleports the specified player to your location <br />
<br />
* '''Commands:''' <code>/staff-tph &#x3C;player&#x3E;</code><br />
<br />
<br />
Returns you to your previous location. <br />
<br />
* Elevators count as a previous location if used <br />
* Used after closing a ticket or doing a staff duty. <br />
* '''Commands:''' <code>/back</code><br />
<br />
<br />
Teleports you to the highest block above your head. <br />
<br />
* Used for when teleported underground from /as tp <br />
* '''Commands:''' <code>/top</code> <br />
<br />
<br />
Teleports you to the specified coordinates<br />
<br />
* '''Commands:''' <code>/staff-tpc &#x3C;coords&#x3E; <reason></code><br />
<br />
<br />
Create a GPS point. <br />
<br />
* '''Please stand still until the Editor says it is deactivated!'''<br />
* '''Commands:''' <code>/staff-gps-create &#x3C;name&#x3E;</code>, <code>/staff-gps-delete</code> <br />
<br />
==== Other ==== <br />
Puts you into or out of spectator mode. <br />
<br />
* Used for searching for chests when vaulting, and when vaulting a building that has a basement.<br />
* '''Commands:''' /spectator <br />
<br />
<br />
Turns fly mode on or off. <br />
<br />
* '''Commands:''' <code>/fly &#x3C;reason&#x3E;</code><br />
<br />
<br />
Sets your in-game drunkenness to 0%. <br />
<br />
* '''Commands:''' <code>/staff-sober</code><br />
<br />
<br />
Resets a player’s in game nickname/display name - Use this to correct incorrect usernames or inappropriate nicknames.<br />
<br />
* '''Commands:''' <code>/nickname player &#x3C;player&#x3E; reset</code><br />
<br />
<br />
Use this to remove any ghost locks. <br />
<br />
* Must be run after vaulting and can be used when players complain about Air etc being locked. <br />
* '''Commands:''' <code>/staff-cleanup-locks</code><br />
<br />
{{Staff}}<br />
'''''[[Category:Staff]]'''''</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Plots_and_regions&diff=7107Plots and regions2025-09-22T09:00:02Z<p>Goldendude15: </p>
<hr />
<div><span id="plots-regions"></span><br />
<br />
DemocracyCraft utilises Areashop (AS) for region management. <span id="wild-region"></span><br />
== Wild region ==<br />
<br />
Players can build freely in the wilderness, but some may desire protection for their bases. You can claim one region with a maximum of 4096 blocks for $10 per block. To claim a wild region at a cost of $10 per block, open a staff ticket using /ticket for wild claiming; if there are no staff online players may open a ticket in the DemocracyCraft main discord. Players may also request to staff that their wild regions be deleted, the player shall then be refunded 90% of the original price when deleted. *Note, players may not sell their wild plots to other players.<br />
<br />
<span id="urban-regions"></span><br />
== Urban regions ==<br />
<br />
There are three main types of plots within Redmont: <br />
# Commercial – Identified by the c- or cbd- tags. Only commercial buildings like stores and apartments are allowed on these plots.<br />
# Residential – Marked with the r- tag. Only houses with up to three visible floors can be built on residential plots.<br />
# Skyscraper – Denoted by the s- tag. Skyscraper plots can only have skyscrapers and are not meant for industrial or residential use.<br />
<br />
To find available plots in the city, look for reselling properties with the corresponding tags (e.g., c-000). Use <code>/as info reselling</code> to locate resold plots and use <code>/gps start [plot]</code> to get to that location.<span id="rental-regions"></span><br />
== Rental regions ==<br />
<br />
There are four main types of rental regions on the server: <br />
# Farm plot – Located in the farming town [[Willow]], these special farm regions can be rented by players (up to two per person). Denoted by the f- tag, they can be rented from the Willow Train Station. <br />
# Apartment – Some commercial buildings offer rentable apartments with prices based on the number of days. These real-life durations provide an affordable option for new players seeking a city residence.<br />
# Shop/market stall – Rentable stores are available in some regions, such as Vestire Mall, allowing players to sell items without purchasing an entire plot.<br />
# Shulker regions – Certain city and town locations have free or low-cost shulker regions with rental durations of 1-10 minutes. Intended for temporary use, such as accessing a shulker box or ender chest.<br />
<br />
You may also encounter other, less popular rental regions. To check information about a rental region, use <code>/as info region [rental region name]</code>.<span id="property-regulations"></span><br />
== Property regulations ==<br />
<br />
Upon purchasing or renting a property, you must adhere to specific regulations and laws. For owned plots, the Department of Construction and Transport (DCT) may issue eviction reports for building violations. Meanwhile, landlords may evict tenants who breach their rental agreements.<br />
<br />
For further details, consult the {{DCForums|Link=threads/rules-laws.5|Forums=Laws}} and the {{DCForums|Link=threads/plot-regulations.17|Forums=Plot Regulations}} threads.<br />
<br />
<span id="commands"></span><br />
<br />
== Commands ==<br />
<br />
* /as help – Shows this help page<br />
* /as rent – Rent a region or extend your current rent<br />
* /as unrent – Unrent a region<br />
* /as buy – Buy a region<br />
* /as sell – Sell a region<br />
* /as me – Check which regions you have and their expiration dates<br />
* /as info – Get info about current regions<br />
* /as info forsale – Regions currently for sale from the Government<br />
* /as info reselling – Regions currently for sale from other players<br />
* /as info region (region name) – Information about a particular region<br />
* /as addfriend – Grant someone building permissions<br />
* /as delfriend – Delete a friend from a region<br />
* /as resell – Put a region into resell mode<br />
* /as stopresell – Put a region back into sold mode<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Plots_and_regions&diff=7106Plots and regions2025-09-22T08:58:18Z<p>Goldendude15: Added how players may not sell their plots according to staff policy.</p>
<hr />
<div><span id="plots-regions"></span><br />
<br />
DemocracyCraft utilises Areashop (AS) for region management. <span id="wild-region"></span><br />
== Wild region ==<br />
<br />
Players can build freely in the wilderness, but some may desire protection for their bases. You can claim one region with a maximum of 4096 blocks for $10 per block. To claim a wild region at a cost of $10 per block, open a staff ticket using /ticket for wild claiming. Players may request their wild regions to be deleted, the player shall be refunded 90% of the original price when deleted. *Note, players may not sell their wild plots to other players.<br />
<br />
<span id="urban-regions"></span><br />
== Urban regions ==<br />
<br />
There are three main types of plots within Redmont: <br />
# Commercial – Identified by the c- or cbd- tags. Only commercial buildings like stores and apartments are allowed on these plots.<br />
# Residential – Marked with the r- tag. Only houses with up to three visible floors can be built on residential plots.<br />
# Skyscraper – Denoted by the s- tag. Skyscraper plots can only have skyscrapers and are not meant for industrial or residential use.<br />
<br />
To find available plots in the city, look for reselling properties with the corresponding tags (e.g., c-000). Use <code>/as info reselling</code> to locate resold plots and use <code>/gps start [plot]</code> to get to that location.<span id="rental-regions"></span><br />
== Rental regions ==<br />
<br />
There are four main types of rental regions on the server: <br />
# Farm plot – Located in the farming town [[Willow]], these special farm regions can be rented by players (up to two per person). Denoted by the f- tag, they can be rented from the Willow Train Station. <br />
# Apartment – Some commercial buildings offer rentable apartments with prices based on the number of days. These real-life durations provide an affordable option for new players seeking a city residence.<br />
# Shop/market stall – Rentable stores are available in some regions, such as Vestire Mall, allowing players to sell items without purchasing an entire plot.<br />
# Shulker regions – Certain city and town locations have free or low-cost shulker regions with rental durations of 1-10 minutes. Intended for temporary use, such as accessing a shulker box or ender chest.<br />
<br />
You may also encounter other, less popular rental regions. To check information about a rental region, use <code>/as info region [rental region name]</code>.<span id="property-regulations"></span><br />
== Property regulations ==<br />
<br />
Upon purchasing or renting a property, you must adhere to specific regulations and laws. For owned plots, the Department of Construction and Transport (DCT) may issue eviction reports for building violations. Meanwhile, landlords may evict tenants who breach their rental agreements.<br />
<br />
For further details, consult the {{DCForums|Link=threads/rules-laws.5|Forums=Laws}} and the {{DCForums|Link=threads/plot-regulations.17|Forums=Plot Regulations}} threads.<br />
<br />
<span id="commands"></span><br />
<br />
== Commands ==<br />
<br />
* /as help – Shows this help page<br />
* /as rent – Rent a region or extend your current rent<br />
* /as unrent – Unrent a region<br />
* /as buy – Buy a region<br />
* /as sell – Sell a region<br />
* /as me – Check which regions you have and their expiration dates<br />
* /as info – Get info about current regions<br />
* /as info forsale – Regions currently for sale from the Government<br />
* /as info reselling – Regions currently for sale from other players<br />
* /as info region (region name) – Information about a particular region<br />
* /as addfriend – Grant someone building permissions<br />
* /as delfriend – Delete a friend from a region<br />
* /as resell – Put a region into resell mode<br />
* /as stopresell – Put a region back into sold mode<br />
[[category:Features]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Goldendude15&diff=7042Goldendude152025-09-06T21:31:01Z<p>Goldendude15: Updates :D</p>
<hr />
<div>'''Goldendude15''' (joined 2023; [[30th Senate|SEN]]–[[WPR]]), also known by his first name '''Caleb''', is a former Redmontian politician who served as a senator with the [[Workers' Party of Redmont]] from the 26th of January 2025 to the 10th of July 2025.<br />
<br />
== Career ==<br />
Goldendude15 originally joined DemocracyCraft in 2023, but quit shortly thereafter. When YouTuber [[Trolligarch wave|Trolligarch released his video]] featuring DemocracyCraft, he returned and became an active player. He soon joined the Redmont Reform Party and ran for the House of Representatives in that month's election, but received no first preference votes and was eliminated.<ref>[https://www.democracycraft.net/threads/house-of-representatives-election-january-2025.24269/ "Election - House of Representatives Election - JANUARY 2025"]</ref> Soon after, he joined the Workers' Party of Redmont (WPR) on the 14th of January 2025, and in a special election for the [[29th Congress#Senate|29th Senate]], was the party's candidate and won with 22 votes, followed by [[Anaphase_Andy]] (independent) at 19 votes.<ref>[https://www.democracycraft.net/threads/senate-election-january-2025-special.24497/ "Election - Senate Election - JANUARY 2025"]</ref><br />
<br />
<br />
<br />
On the 28th of January, Goldendude15 publicly endorsed [[1950minecrafter]] in the [[February 2025 presidential election]].<ref>https://discord.com/channels/1331745864691220586/1333234542429077607/1333622752489504871</ref><br />
<br />
<br />
<br />
On the 10th March, he was reelected to the [[30th Congress#Senate|30th Congress]] with 24 votes.<ref>[https://www.democracycraft.net/threads/senate-election-march-2025.25000/ "Election - Senate Election - MARCH 2025"]</ref><br />
<br />
Goldendude15 is currently serving as a recruit in the Department of Homeland Security.<br />
<br />
== Personal life ==<br />
Goldendude is married to [[Sleepii_Sloth]], a fellow WPR politician.<br />
<br />
Goldendude15 is also one of the founders of the wild town of [[Anville]], thus he holds the town dear to his heart. <br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:2023 joins]]<br />
[[Category:2025 people]]<br />
[[Category:29th Senate]]<br />
[[Category:30th Senate]]<br />
[[Category:Doctors]]<br />
[[Category:Former Redmont Reform Party members]]<br />
[[Category:People from Anville]]<br />
[[Category:Trolligarch generation]]<br />
[[Category:Workers' Party of Redmont congresspeople]]</div>Goldendude15https://wiki.democracycraft.net/index.php?title=Driver%27s_licence&diff=3188Driver's licence2025-04-11T06:12:08Z<p>Goldendude15: Added that only a mechanic can craft fuel.</p>
<hr />
<div>[[File:Player driving a car.webp|thumb|426x426px]]<br />
Learn about the essential traffic laws, getting a vehicle, and car management.<br />
<br />
Once you pass the exam, its your qualification to keep!<br />
<br />
<div class="figure"><br />
<br />
</div><br />
<span id="laws"></span><br />
== Laws ==<br />
<br />
To be a responsible driver and follow traffic laws, here are some key rules:<br />
<br />
* Always drive on the right side of the road, and follow directional arrows if it’s a single lane.<br />
* Drive only within marked road areas to avoid careless driving fines.<br />
* Never drive under the influence to prevent penalties.<br />
* Park properly; improper parking may lead to vehicle impoundment.<br />
<br />
<span id="acquiring-a-car"></span><br />
== Acquiring a Car ==<br />
<br />
Cars are valuable, so stealing one is against the rules. Visit the Vehicle Dealership near Essendon Train Station to buy one. Mechanics can craft cars, but it’s costly. Consider buying from players or companies for a better deal.<br />
<br />
<span id="using-a-car"></span><br />
== Using a Car ==<br />
<br />
Only the owner can interact with the vehicle. Make sure you have enough space in your inventory. Here are the actions you can perform:<br />
<br />
* Shift left-click: Refuel the vehicle.<br />
* Shift right-click: Pick up the vehicle.<br />
* Right-click: Get inside the vehicle.<br />
* Right-click while in the vehicle: Open the trunk for storage.<br />
<br />
<span id="fuel"></span><br />
== Fuel ==<br />
<br />
Your vehicle needs fuel to run! Buy it from gas stations or other players! If you have the mechanic profession you can craft it yourself using 4 emeralds, 4 coal, and 1 bucket. (Only mechanics can craft fuel, if you don't have the profession make sure to head to the university to pass the exam and become one yourself!)<br />
<br />
<div class="figure"><br />
<br />
[[File:Fuel Recipe as at 2024-09-07.webp|527x527px|Image]]<br />
<br />
</div><br />
<span id="conclusion"></span><br />
<br />
<br />
== Conclusion ==<br />
<br />
Driving offers freedom, and you can impress your friends with your new car. Good luck on your Driver’s License exam!<br />
[[category:Licenses]]</div>Goldendude15