-
Notifications
You must be signed in to change notification settings - Fork 4
Commands
/party create <name>
/party add <party> <name>
/party remove <party> <name>
/party rank <party> <name> <manager|member>
/party leave <party>
/party info <party>
Administration:
/partymanage add <party> <name>
/partymanage remove <party> <name>
/partymanage rank <party> <name> <manager|member>
/claim [<party>]
/unclaim
-
/own
— view owner of the plot that you are in
Administration:
/claimmanage claim [<party>]
/claimmanage unclaim
/invite <name>
/ban <name> <reason...>
/pardon <name> <reason...>
/motd
/broadcast <message...>
/broadcast -t alert <message...>
/cr
/su
/gm <gamemode>
/heal [-a <amount>] [<target>]
/feed [-a <amount>] [<target>]
/god [<target>]
/ungod [<target>]
/mod
-
/done
— leave mod mode
/to <player>
/bring <player>, <player>, <player>, ...
Offline players are supported. To specify use of an offline player, prefix the name with $
and specify the entire length of the name.
The *
wildcard is supported for /bring
to select all players.
/viewinv <target>
Offline players are supported. To specify use of an offline player, prefix the name with $
and specify the entire length of the name.
- The first row of the displayed inventory constitutes the hotbar.
- The next three rows constitutes the main inventory.
- The first four slots of the 5th row are the armor slots.
- Baubles and other inventories are not yet supported.
- Putting anything outside those aforementioned slots will cause the loss of that item.
The player that owns the inventory that you are viewing can log on or off while you are viewing the inventory and changes that you make will still persist (and changes from the player will appear in your view too). If the player is online, your item transfers are immediately apparent. On the other hand, if the player is offline, your changes will only be saved once you've closed the inventory. If the player logs on while you are making changes, the changes will be applied at that moment (to the player directly and not directly to the player data file).
There is one case where your changes may be lost: if the player has died and not yet respawned, your changes will be wiped when the player respawns. You will notice the player's inventory empty when the player dies.
/bt search <parameters...>
/bt near
/bt page <page>
/bt rollback <parameters...>
/bt replay <parameters...>
-
/bt details <parameters...>
(may also specify a record # from a previous search) -
/bt items <parameters...>
(may also specify a record # from a previous search) -
/bt teleport <parameters...>
(may also specify a record # from a previous search)
Parameters can be specified as either p:value
or param value
(i.e. world 0 p:sk89q
). Player names must be printed in full.
-
world
,w
-
user
,player
,p
-
before
,b
-
since
,time
,t
-
area
,radius
,r
-
action
,a
-
-action
,-a
It is currently not possible to negate all the parameters yet.
block-break
block-place
block-explode
item-pickup
item-drop
bucket-fill
entity-damage
chat
command
player-death
-
/plume reload
— reloads config and data
-
/restart <timeout>
or/shutdown <timeout>
To abort, use abort
for the timeout.
-
/setspawn
— sets the world's spawn -
/spawn <player>
— teleports the given player to the spawn of the world the given player is in, not the spawn of the main world or the world that the command's user is in