User:DRY411S: Difference between revisions
m (Creating user page for new user.) |
No edit summary |
||
Line 1: | Line 1: | ||
An old grey bloke who likes fiddling about with computers. | An old grey bloke who likes fiddling about with computers. | ||
== Multiplayer Admin Features == | |||
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file. | |||
Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed) | |||
=== Console Commands for player management === | |||
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text. | |||
;/admins | |||
:Prints a list of game admins | |||
;/ban <player> <reason> | |||
:Bans the specified player. The <reason> is stored where? | |||
;/banlist <add/remove/get/clear> | |||
:add - is the same as /ban <player> <reason> | |||
:remove - is the same as /unban <player> | |||
:get - prints a list of banned players | |||
:clear - unbans all banned players | |||
;/bans | |||
:prints a list of banned players (is the same as /banlist get) | |||
;/delete-blueprint-library <player> | |||
:deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed | |||
;/demote <player> | |||
:Demotes the player from being an admin | |||
;/kick <player> <reason> | |||
:Forcibly disconnects the player from the server ''but does not ban them'' The <reason> is stored where? | |||
;/open <player> | |||
:Opens another player's inventory | |||
;/permissions | |||
:Opens the permissions GUI. See this link | |||
;/promote <player> | |||
:Promotes the player to admin | |||
;/purge <player> | |||
:Clears all the messages by this user from the chat log | |||
;/swap-players <player1> <player2> | |||
:If player2 is empty, swaps your character with the given players character | |||
:If player2 is not empty, swaps the two player characters | |||
;/unban <player> | |||
:Unbans the specified player | |||
;/whitelist <add/remove/get/clear> <player> | |||
:If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this. | |||
:add - Adds the player to a whitelist | |||
:remove - Removes the player from the whitelist | |||
:get - prints the whitelist | |||
:clear - empties the whitelist. Any player can join the game. | |||
=== Console Commands for server and game management === | |||
/config | |||
/measured-command | |||
/perf-avg-frames | |||
/server-save | |||
/silent-command | |||
/toggle-heavy-mode | |||
=== The Permissions System === | |||
stub |
Revision as of 09:26, 25 February 2018
An old grey bloke who likes fiddling about with computers.
Multiplayer Admin Features
Every multiplayer game has at least one Admin user. When a multiplayer game is started from the game's GUI, this is the person who created the multiplayer game. On a headless server, the game can start with several Admins by editing the <server-settings.json> (link needed) file.
Admin users have several abilities that regular users do not. Most of these are invoked through console commands (link to console commands). Others are invoked through the Permissions GUI (link needed)
Console Commands for player management
Where <player> is used, you should type the name of a player. Anywhere else where the < and > braces are used, you may type any text.
- /admins
- Prints a list of game admins
- /ban <player> <reason>
- Bans the specified player. The <reason> is stored where?
- /banlist <add/remove/get/clear>
- add - is the same as /ban <player> <reason>
- remove - is the same as /unban <player>
- get - prints a list of banned players
- clear - unbans all banned players
- /bans
- prints a list of banned players (is the same as /banlist get)
- /delete-blueprint-library <player>
- deletes the blueprint library storage for the player (if offline) from the save file. If instead of <player>, you type "everybody confirm" (without the quotation marks) the blueprint libraries of every offline player will be removed
- /demote <player>
- Demotes the player from being an admin
- /kick <player> <reason>
- Forcibly disconnects the player from the server but does not ban them The <reason> is stored where?
- /open <player>
- Opens another player's inventory
- /permissions
- Opens the permissions GUI. See this link
- /promote <player>
- Promotes the player to admin
- /purge <player>
- Clears all the messages by this user from the chat log
- /swap-players <player1> <player2>
- If player2 is empty, swaps your character with the given players character
- If player2 is not empty, swaps the two player characters
- /unban <player>
- Unbans the specified player
- /whitelist <add/remove/get/clear> <player>
- If the whitelist is not empty, only players in the whitelist can join the game. On headless servers, a pre-defined whitelist can be added to <server-settings-json> check this.
- add - Adds the player to a whitelist
- remove - Removes the player from the whitelist
- get - prints the whitelist
- clear - empties the whitelist. Any player can join the game.
Console Commands for server and game management
/config /measured-command /perf-avg-frames /server-save /silent-command /toggle-heavy-mode
The Permissions System
stub