FroobWorld Wiki - User contributions [en]

Server guide/Staff deputy guide

2026-06-07T15:06:10Z

EvilDrBA:

[[Category:Tutorials]]

[[Server guide/Trusted guide|Trusted]] players that are interested in having more of a moderation role on the server may temporarily be granted Staff deputy status.

== Purpose and expectations ==
Unlike the trusted role, staff deputies are expected to help out with moderation of the server.

Including but not limited to following up on suspicious activity and reviewing area requests.

== Commands & permissions ==

In addition to their normal [[Server guide/Trusted guide|trusted]] commands, deputies have access to these commands:

{| class="wikitable"
|+
|-
! Command !! Description
|-
| /stafftasks || View open tickets & area requests
|-
| /warn <player> <reason> || Send warning to player. They will receive a notice in chat and a mail. Warnings are automatically added to notes
|-
| /punishmentlog /punishmenthistory <player> || View recent punishments or punishment history for a specific player
|-
| /ticket read <id> /ticket teleport <id> || Read & teleport to ticket location
|-
| /ticket addnote <id> <note> /ticket escalate <id> <note> /ticket close <id> <message> || Handle tickets
|-
| /area <review|teleport> <area> /area <approve|deny> <area> <message> || Review area request
|-
| /redefinearea <area> || Resize area (set /p1 and /p2 beforehand)
|-
| /antixray <check|enable|disable> <player> || Check/change antixray status of a player
|-
| /orestats <player> || Show ore statistics for player
|-
| /oreignore <add|remove> <player> || Stop seeing mining notifications for a player
|-
| /co inspect /co lookup || View logs for blocks & containers
|-
|}

Other abilities include:
* Accessing any <code>[Private]</code> containers/doors
* Editing permissions/flags of all areas & claimed horses

== Reviewing areas ==

There are a few things to keep in mind when checking claim requests, they do not have to be done in the same order as listed below.

To start, you will have to check <code>/stafftasks</code> and type <code>/area review area_name</code>

=== Normal review steps ===

Steps to take when reviewing an area request:
* Visualise the area (by clicking on "Visualise" in the area review)
* Check if the player trying to claim the area with a build, also made it. This can be done easily with <code>/co inspect</code> and clicking a few blocks. If the person that requested the claim is a person you trusted and know are non-nabby, you can skip this step. Or if you know/see that they are friends with the builder.
* Check for nearby claims/builds, by doing one or more of:
** <code>/area near 250</code>
** Using freecam (mod), also check underground
** Flying around
* Take a look at the build itself:
** Is there enough built in the claim?
** Is the claim size too big/too small?

If you aren't too confident with your judgement you can always ask other deputies or staff.

Exceptions: If the person requesting to claim the area isn't the one who built in it you can always ask the players or see if they are friends. (asking one of them is enough)

=== Spawn/Shopping district ===
Builds near other claims/builds at spawn usually get approved if the other important aspects are met, this is if the claim does not overlap with any other important builds or any claims.

For the shopping district, if the plot is owned by the person claiming it (and has paid for it of course), it should get approved. Even if they haven't built anything yet.

=== Special cases ===

* Area inside another area: decline it and explain how to make a subclaim in the deny message
* Town claims: make sure it's the owner of the town and if possible do it while they are online. (remind them to add the players)
* Crafting table/furnace/chest/bed, if that's everything they are trying to claim deny it and remind them of private signs.
* If they messed up claiming their plot, you can always do <code>/redefinearea</code> before approving it.

=== Example messages ===

<code>/area deny Please build more before trying to claim a big area.</code>

Something similar to this is what you will have to write most of the time, when the build is too small compared to the claim.

<code>/area deny Too close to other builds.</code>

Self explanatory, you can also add that they could talk to the owners of the other builds/claims and request again.

<code>/area deny You have already claimed this.</code>

If you see that they want to make a subclaim you can mail
or message them about how to do so. (<code>/setarea existing_areaname:new_area_name</code>)

These are some examples, you can use them or just take inspiration. (don't have to if you don't want to of course).

== Using CoreProtect ==

To be added...

=== Tips & tricks ===

Server guide/Staff deputy guide

2026-01-09T22:00:42Z

EvilDrBA:

[[Category:Tutorials]]

[[Server guide/Trusted guide|Trusted]] players that are interested in having more of a moderation role on the server may temporarily be granted Staff deputy status.

== Purpose and expectations ==
Unlike the trusted role, staff deputies are expected to help out with moderation of the server.

Including but not limited to following up on suspicious activity and reviewing area requests.

== Commands & permissions ==

In addition to their normal [[Server guide/Trusted guide|trusted]] commands, deputies have access to these commands:

{| class="wikitable"
|+
|-
! Command !! Description
|-
| /stafftasks || View open tickets & area requests
|-
| /warn <player> <reason> || Send warning to player. They will receive a notice in chat and a mail. Warnings are automatically added to notes
|-
| /punishmentlog /punishmenthistory <player> || View recent punishments or punishment history for a specific player
|-
| /ticket read <id> /ticket teleport <id> || Read & teleport to ticket location
|-
| /ticket addnote <id> <note> /ticket escalate <id> <note> /ticket close <id> <message> || Handle tickets
|-
| /area <review|teleport> <area> /area <approve|deny> <area> <message> || Review area request
|-
| /redefinearea <area> || Resize area (set /p1 and /p2 beforehand)
|-
| /antixray <check|enable|disable> <player> || Check/change antixray status of a player
|-
| /orestats <player> || Show ore statistics for player
|-
| /oreignore <add|remove> <player> || Stop seeing mining notifications for a player
|-
| /co inspect /co lookup || View logs for blocks & containers
|-
|}

Other abilities include:
* Accessing any <code>[Private]</code> containers/doors
* Editing permissions/flags of all areas & claimed horses

== Reviewing areas ==

Area requests

There are a few things to keep in mind when checking claim requests, they do not have to be done in the same order as listed on the next pages.

To start, you will have to check /stafftasks and type /area review area_name Clicking on area visualise after teleporting to the area is helpful.

First, you should check if the player trying to claim the area with a build, also made it.
This can be done easily with /co i and clicking a few blocks. If the person that requested the claim is a person you trusted and know are non-nabby, you can skip this step.
Or if you know/see that they are friends with the builder, approving it would be an option.
Secondly, if they do match (builder and area claim requester), you should check for nearby claims/builds, this can quickly be done with /area near 250 or freecam (mod), checking underground also helps. Simply flying around can also do the trick. Thirdly, take a look at the build itself, decide if the claim size is too big/too small or if there's anything else wrong with it.
If you aren't too confident with your judgement you can always ask other deputies or staff.
Exeptions:If the person requesting to claim the area isn't the one who built in it you can always ask the players or see if they are friends. (asking one of them is enough)

Spawn/Shopping district
Builds near other claims/builds at spawn usually get approved if the other important aspects are met, this is if the claim does not overlap with any other important builds or any claims. For the shopping district, if the plot is owned by the person claiming it (and has paid for it of course), it should get approved. Even if they haven't built anything yet.
If they messed up claiming their plot, you can always do /redefinearea before approving it.
Some other things you might see:

A requested subclaim, (decline it and explain how to make a subclaim in the deny message)

Town claims, make sure it's the owner of the town and if possible do it while they are online. (to remind them to add the players)Crafting table/furnace/chest/bed, if that's everything they are trying to claim deny it and remind them of private signs.
These are some examples of area deny messages:

/area deny Please build more before trying to claim a big area.
Something similar to this is what you will have to write most of the time, when the build is too small compared to the claim./area deny Too close to other builds.
Self explanatory, you can also add that they could talk to the owners of the other builds/claims and request again.

/area deny You have already claimed this.
If you see that they want to make a subclaim you can mail
or message them about how to do so. /setarea existing_areaname:new_area_name

These are some examples, you can use them or just take inspiration. (don't have to if you don't want to of course).
== Using CoreProtect ==

To be added...

=== Tips & tricks ===

Server guide/Staff deputy guide

2026-01-09T21:59:58Z

EvilDrBA:

[[Category:Tutorials]]

[[Server guide/Trusted guide|Trusted]] players that are interested in having more of a moderation role on the server may temporarily be granted Staff deputy status.

== Purpose and expectations ==
Unlike the trusted role, staff deputies are expected to help out with moderation of the server.

Including but not limited to following up on suspicious activity and reviewing area requests.

== Commands & permissions ==

In addition to their normal [[Server guide/Trusted guide|trusted]] commands, deputies have access to these commands:

{| class="wikitable"
|+
|-
! Command !! Description
|-
| /stafftasks || View open tickets & area requests
|-
| /warn <player> <reason> || Send warning to player. They will receive a notice in chat and a mail. Warnings are automatically added to notes
|-
| /punishmentlog /punishmenthistory <player> || View recent punishments or punishment history for a specific player
|-
| /ticket read <id> /ticket teleport <id> || Read & teleport to ticket location
|-
| /ticket addnote <id> <note> /ticket escalate <id> <note> /ticket close <id> <message> || Handle tickets
|-
| /area <review|teleport> <area> /area <approve|deny> <area> <message> || Review area request
|-
| /redefinearea <area> || Resize area (set /p1 and /p2 beforehand)
|-
| /antixray <check|enable|disable> <player> || Check/change antixray status of a player
|-
| /orestats <player> || Show ore statistics for player
|-
| /oreignore <add|remove> <player> || Stop seeing mining notifications for a player
|-
| /co inspect /co lookup || View logs for blocks & containers
|-
|}

Other abilities include:
* Accessing any <code>[Private]</code> containers/doors
* Editing permissions/flags of all areas & claimed horses

== Reviewing areas ==

Area requests

There are a few things to keep in mind when checking claim requests, they do not have to be done in the same order as listed on the next pages.

To start, you will have to check /stafftasks and type /area review area_name Clicking on area visualise after teleporting to the area is helpful.

First, you should check if the player trying to claim the area with a build, also made it.
This can be done easily with /co i and clicking a few blocks. If the person that requested the claim is a person you trusted and know are non-nabby, you can skip this step.
Or if you know/see that they are friends with the builder, approving it would be an option.
Secondly, if they do match (builder and area claim requester), you should check for nearby claims/builds, this can quickly be done with /area near 250 or freecam (mod), checking underground also helps. Simply flying around can also do the trick. Thirdly, take a look at the build itself, decide if the claim size is too big/too small or if there's anything else wrong with it.
If you aren't too confident with your judgement you can always ask other deputies or staff.
Exeptions:If the person requesting to claim the area isn't the one who built in it you can always ask the players or see if they are friends. (asking one of them is enough)

Spawn/Shopping district
Builds near other claims/builds at spawn usually get approved if the other important aspects are met, this is if the claim does not overlap with any other important builds or any claims. For the shopping district, if the plot is owned by the person claiming it (and has paid for it of course), it should get approved. Even if they haven't built anything yet.
If they messed up claiming their plot, you can always do /redefinearea before approving it.
Some other things you might see:

A requested subclaim, (decline it and explain how to make a subclaim in the deny message)

Town claims, make sure it's the owner of the town and if possible do it while they are online. (to remind them to add the players)Crafting table/furnace/chest/bed, if that's everything they are trying to claim deny it and remind them of private signs.
These are some examples of area deny messages:

/area deny Please build more before trying to claim a big area.
Something similar to this is what you will have to write most of the time, when the build is too small compared to the claim./area deny Too close to other builds.
Self explanatory, you can also add that they could talk to the owners of the other builds/claims and request again.

/area deny You have already claimed this.
If you see that they want to make a subclaim you can mail
or message them about how to do so. /setarea existing_areaname:new_area_name
These are some examples, you can use them or just take inspiration. (don't have to if you don't want to of course).
== Using CoreProtect ==

To be added...

=== Tips & tricks ===