Mod Administrativo Original

The following are user commands and are available to all players:


Command: /chat {entries}
Shows the chat's history. By default it shows the last 100 entries.


Command: /date
Displays the current date.


Command: /head
Displays your heading.


Command: /head {on|off}
Turn {on} to continue displaying your heading, updating once a second.


Command: /hello
A simple Hello World test.


Command: /help {name}
Displays help on the specified command {name}.


Command: /motd
Displays the message of the day.


Command: /pos
Displays your position.


Command: /pos {on|off}
Turn {on} to continue displaying your position, updating once a second.


Command: /savetoolbar or /savecockpit
In multiplayer, will save the toolbar in the current cockpit. This will allow it to persist without the need to build from a blueprint.
Note: You must be inside of the cockpit (or remote cube), and you must own the cockpit (or not be owned at all).


Command: /settings
Will display all current game settings.


Command: /range
Sets a GPS coordinate on the targeted item under the player crosshairs, showing the range.
Only items in visible range can be targeted, and the item is not identified.


Command: /status
Displays the current players and steam Ids.


Command: /time
Displays the current time.


Note: Individual commands can be disabled by your game Server Administrator on a Dedicated Server and thus may not be available to all players.
See the Permissions page for details on how to do this.

****

The following are Admin only commands for asteroid management:


Command: /listasteroids {filter}
List in-game asteroids. Optional {filter} to refine your search by name.


Command: /listplanets {filter}
List in-game planets. Optional {filter} to refine your search by name.


Command: /deleteplanet {filter} or /delplanet {filter}
Deletes the targeted planet.
Optional filter to delete the specified planet by hotlist <#> or name.


Command: /rotateroid {name} {yaw} {pitch} {roll}
Rotates the specified Asteroid {name} about {yaw} {pitch} {roll}.
Examples:
/rotateroid baseasteroid1 -90 180 0


Command: /createroid {X} {Y} {Z} {Size} {Name}
Creates an empty Asteroid space at location {X,Y,Z} of cubic {Size}. The size must be multiple of 64.
This empty Voxel space is so that you may fill it using the Voxel Hands.


Command: /createroidsphere {Name} {X} {Y} {Z} {Parts} {Material} {Diameter}
This command is used to generate a sphere asteroid at the exact center of the specified co-ordinates, with multiple layers.
This command is limited to offline only, as it is too processor intensive to run in a multiplayer game.
Multiple layers are achieved with additional {Material} and {Diameter} parameters.
/createroidsphere {Name} {X} {Y} {Z} {Parts} {Material1} {Diameter1} {Material2} {Diameter2} {Material3} {Diameter3} ....
{Name} ~ the base name of the asteroid file. A number will be added if it already exists.
{X} {Y} {Z} ~ the center coordinate of where to place the asteroid.
{Parts} ~ specify to break the sphere down into smaller chunks. Either 1-}whole sphere, 2-}hemispheres, 4 or 8 parts.
{Material} ~ the material of the layer. An empty layer can be specified with the word 'none'.
{Diameter} ~ the diameter of the layer.
... ~ Additional material and diameters can be specified for additional layers.
Examples:
/createroidsphere sphere_solid_stone 1000 1000 1000 1 Stone_01 100
/createroidsphere sphere_hollow_stone 2000 2000 2000 8 Stone_01 200 none 180
/createroidsphere sphere_3_tricky_layers 3000 3000 3000 2 Stone_01 200 none 180 Stone_01 160 none 140 Stone_01 120 none 100
/createroidsphere sphere_layers 8000 8000 8000 2 Stone_01 200 Iron_01 180 Nickel_01 100 Cobalt_01 90 Magnesium_01 80 Silicon_01 70
Note: The larger and more complex the asteroid, the longer it will take to generate. More than 2000m can as much as an hour on some computers.
The flat faces on the inside of the multi part asteroids will seem to become invisible at a distance.
If you need Sphere asteroids on a dedicated server, then a tool like SEToolbox is required to copy them across from your single player world.


Command: /roidfill {name} {material}
Fill the specified Asteroid {name} with the {material}, replacing all other materials. ie, /roidfill baseasteroid1 gold_01


Command: /roidreplace {name} {material1} {material2}
In Asteroid {name} will replace {material1} with {material2}. ie, /roidreplace baseasteroid1 stone_01 gold_01


Command: /listvoxels {filter}
List stock voxels that can be placed. Optional {filter} to refine your search by name.


Command: /addvoxel {X} {Y} {Z} {Name}
Add stock voxel asteroid {Name} at location {X,Y,Z}.


Command: /scanore ['clear'] {range}
Looks for ore within {range} in all nearby asteroids and tags them with GPS. Optional word 'clear' to remove gps.
Examples:
/scanore 2000
/scanore clear 3000

****

The following are Admin only commands for faction management:


Command: /fp {#}
Promotes the specified {#} player one level within their faction.


Command: /fd {#}
Demotes the specified {#} player one level within their faction.


Command: /fj {faction} {#|B}
The specified {#} player or {B} bot joins {faction}.
Examples: /fj MAF #8
/fj awesome B12
/fj MAF The Masked Bandit


Command: /fk {#|B}
Kicks the specified {#} player or {B} bot from their faction.
Examples: /fk #2
/fk B12


Command: /fr {faction}
The specified {faction} is removed. All players are also removed from the faction.


Command: /fa {faction}
The specified {faction} will accept all proposed peace treaties.

****

The following are Admin only commands for inventory management:


Command: /countobjects
Counts number of in game floating objects and bodies.


Command: /collectobjects {range}
Teleports any floating objects in {range} of the player to the player's location.
This is good for collecting any loose ore, debris or components floating around.
If you have many floating objects, they will be teleported progressively to prevent them from stacking into the same space, to prevent them from getting stuck and from overwhelming a collector.


Command: /pullobjects {range} {speed}
Draws any floating objects and bodies in {range} to the player at specified {speed}. A negative speed will push objects away. A zero speed will stop objects.


Command: /drop {type name|name} {amount}
Drop a specified item (ore, ingot, or item), {name}, {amount}.
Partial names are acceptable as long as they are unique.
Other languages work if set before loading world.
Examples:
/drop ore gold 98.12
/drop steel plate 25
/drop 200mm 10


Command: /invadd {type name|name} {amount}
Adds a specified item to your inventory (ore, ingot, or item), {name}, {amount}.
Partial names are acceptable as long as they are unique.
Other languages work if set before loading world.
Examples:
/invadd ore gold 98.12
/invadd steel plate 25
/invadd 200mm 10


Command: /invins {type name|name} {amount}
Adds a specified item to the targeted player, backpack, cube in your crosshairs (ore, ingot, or item), {name}, {amount}.
Partial names are acceptable as long as they are unique.
Other languages work if set before loading world.
Examples:
/invinsert ore gold 98.12
/invins steel plate 25
/invinsert ice 100000
/invins radio 120
/invins 200mm 250


Command: /invclear {#}
All inventory of the specified {#} player will be deleted.
This is good for either dumping your own inventory because you are creating a scenario and don't want to drop it in space, or you have a player on a server who is trolling other players with weapons, grinders. You can delete all their inventory without having to hurt the player more directly.
This can be used in conjunction with the /status command to provide a hotlist number for the specifc player.
Examples:
/invclear Screaming Angels
/status
/invclear #3

***

The following are Admin only commands for miscellaneous management:


Command: /id
Identifies the name of the object the player cross-hairs are over, and provides basic details including mass, center mass position, cubes, etc.
This includes ships, asteroids, and planets.


Command: /detail
Provides more detailed information than /id on the object the player is looking at, which can take longer to provide.
Currently more detail is only supplied with asteroids.


Command: /invisible {on|off}
Turns invisible mode on or off for you only. Other players will still see your shadow, chest thrusters, and held weapons. Automated weapons will still target you.


Command: /god {on|off}
Turns god mode on or off.


Command: /bomb
Throws a warhead in the direction you face.


Command: /meteor
Throws a meteor in the direction the player faces.


Command: /save {server/local} [customSaveName]
Saves the active game on the server or to the local computer. This is useful if you need to make a backup of your dedicated server.
Optionally you can save the world as [customSaveName]. Please note that the world might not appear in the 'Load World' screen if saved locally.
Examples:
/save l
/save s
/save server backup


Command: /stopall {range}
Stops all motion of everything in the specified {range}.
A default range of 100m will be used if a value is not specified.


Command: /suntrack
Displays the track of a moving sun by creating 20 GPS coordinates. Each coordinate is placed at 1/20 of the time it takes for the sun to orbit, and includes the time information.
Additional GPS coordinates are placed from the observation point, and along the axis of rotation to indicate exactly along where a sun rotates.
Note, that the calculation that Keen uses for the sun creates an elliptical orbit, not a circular orbit. As a result you will see the GPS coordinates bunch up on two sides, and space out on adjacent sides. The sun's movement will slow and speed up during these parts of its orbital movement.
Examples:
/suntrack - will create the default 20 points.
/suntrack 4 - will create with 4 points at the cardinal directions.
/suntrack clear - will clear the points that have been created.

***


The following are Admin only commands for movement/position management:


Command: /back
Teleports you back to your previous location.


Command: /jump {Distance} or /j
Jump player or piloted ship +{Distance} forward or -{Distance} Backward. (A simpler version of /to).
Think of it as a personal FTL drive!


Command: /setvector {X} {Y} {Z}
Set player or piloted ship flying on the specified vector {X Y Z}


Command: /speed {#}
Set player or piloted ship flying forward at the specified {#} speed m/s. All other vectors are reset. Spin is not reset.


Command: /flyto {X} {Y} {Z} {Velocity}
Sends player or piloted ship flying to position {X Y Z} at speed {Velocity}


Command: /to {X} {Y} {Z}
Teleport Offset a player or piloted ship, thus moving them by the specified values {X Y Z}.
-X = Left
+X = Right
-Y = Down
+Y = Up
-Z = Forward
+Z = Backward


Command: /tps {#}
Teleport player to the specified ship {#}. (does not teleport ship to ship)
This is a same as using /tp S{#}


Command: /tpp {#}
Teleport you to the specified player {#}.
This is a same as using /tp C{#}


Command: /tpfav {name}
Teleport player or piloted ship to the previously saved location named {name}.


Command: /tpsave {name}
Saves the current position under the {name} for later teleporting to with command /tpfav. All position information is saved on the Client computer.


Command: /tpdel {name}
Delete the previously saved location named {name}.


Command: /tplist {filter}
List the current favorite save points. Optional {filter} to refine your search name.


Command: /tp ...
Teleport is a generic command which accepts multiple types of inputs which will teleport a player or piloted ship safely:

/tp {X} {Y} {Z}
Teleports you to the specified coordinate {X Y Z}.
Example: /tp -49483.15 439873.24 30.5

/tp {GPS}
Teleports you to a GPS coordinate. A GPS coordinate can be pasted directly from your clipboard memory into the chat field.
Example: /tp GPS:Screaming Angels #1:3.75:-3.75:-11.25:

/tp ID
Teleports you to the Last item identified with /id.
Example: /tp id

/tp S{#}
Teleports you to the Ship hotlist number generated by /listships.
Example: /tp S76
This is a same as using /tps {#}

/tp C{#}
Teleports you to the player Character hotlist number generated by /status.
Example: /tp C18
This is a same as using /tpp {#}

/tp P{#}
Teleports you to the Planet hotlist number generated by /listplanets.
Example: /tp P6

/tp A{#}
Teleports you to the Asteroid hotlist number generated by /listasteroids.
Example: /tp A453

/tp {name}
Teleports you to a named ship, player, planet, asteroid, gps coordinate.
Examples: /tp "Screaming Angels"
or /tp "Large Ship 4890"
or /tp "Screaming Angels #1"

/tp C{#} C{#}
Teleports the specific player character hotlist number to another specified player character hotlist number.
Example: /tp C8 C4

/tp C{#} S{#}
Teleports the specific player character hotlist number to the specified ship hotlist number.
Example: /tp C4 S145

/tp C{#} {X} {Y} {Z}
Teleports the specific player character hotlist number to specified coordinate {X Y Z}.
Example: /tp C7 -49483.15 439873.24 30.5

/tp C{#} {GPS}
Teleports the specific player character hotlist number to specified GPS coordinate. A GPS coordinate can be pasted directly from your clipboard memory into the chat field.
Example: /tp C2 GPS:Screaming Angels #1:3.75:-3.75:-11.25:

/tp C{#} {name}
Teleports the specific player character hotlist number to the named ship, player, planet, asteroid, gps coordinate.
Example: /tp C2 "Patrol Craft"
or /tp C8 "Screaming Angels #4"
or /tp C1 BaseAsteroid

/tp S{#} C{#}
Teleports the specific ship hotlist number to the specified player character hotlist number.
Example: /tp C4 S145

/tp S{#} S{#}
Teleports the specific ship hotlist number to another specified ship hotlist number.
Example: /tp S85 S145

/tp S{#} {X} {Y} {Z}
Teleports the specific ship hotlist number to specified coordinate {X Y Z}.
Example: /tp S47 -49483.15 439873.24 30.5

/tp S{#} {GPS}
Teleports the specific ship hotlist number to specified GPS coordinate. A GPS coordinate can be pasted directly from your clipboard memory into the chat field.
Example: /tp S47 GPS:Screaming Angels #1:3.75:-3.75:-11.25:

/tp S{#} {name}
Teleports the specific ship hotlist number to the named ship, player, planet, asteroid, gps coordinate.
Example: /tp S2 "Patrol Craft"
or /tp S8 "Screaming Angels #4"
or /tp S1 BaseAsteroid

/tp {name1} {name2}
Teleports a named player or ship to another named ship, player, planet, asteroid, gps coordinate.
Example: /tp Miner1 "Patrol Craft"
or /tp Sp[a]cemarine "Screaming Angels"
or /tp "Mine Layer" BaseAsteroid



Command: /tpx ...
This works the same as /tp ..., except it performs no safety checks. You or the specified item will be teleported to the exact location specified.


Warning:

Teleporting of stations attached via landing gear may cause issues.

Notes:

All of these commands include attached rotors, pistons, connectors, and landing gear when teleporting a ship.
It's a good idea to leave your Inertia Dampeners off, as it will try to match your velocity with the target object, so you don't smack into one another if you or the target is already moving.
/tp will not teleport an anything outside of a World of restricted size. Use /tpx instead.



****



The following are Admin only commands for player management, and are used in conjunction with the /status command:


Command: /eject {#}
The specified {#} player is removed from control of any ship. This includes Remote Control and cockpits, thus ejecting them into space.


Command: /slay {#}
Kills the specified {#} player. Instant death in Survival mode. Cannot slay pilots.


Command: /smite {#}
Drops meteor on the specified {#} player. Instant death in Survival mode. Cockpits do protect a little, but can become collateral damage.


Player griefing

We are aware that some players online are able to circumvent normal protections in a non modded game like kick and ban, as well as been able to copy and paste ships in a survival game when they shouldn't. To try and address this, we have created the following commands in our mod to circumvent the changes these griefers have made to their game code. These should only be used in extreme circumstances. Currently they are enabled for both dedicated servers and hosted listen servers.

Command: /forcekick {#}
Forces the specified player {#} to disconnect. Only use this if normal kick does not work.


Command: /forceban {#}
Forces the specified player {#} to disconnect and bans him. Only use this if normal ban does not work.


Command: /pardon {name}
Pardons the specified player {name} if he has been forcebanned.


****


The following are Admin only commands for session management:


Command: /CopyPaste {on|off} <private>
Turns Copy Paste mode on or off for all players. Add the word "private" for you only.
This works on Single player, as well as Multiplayer.
Requires Game Mode to be changed to Creative first for it to work.
Note:
On a Listen Server Hosted game, if the "Private" setting is used in Multiplayer anyone connecting after making a change will also inherit them.
Examples:
/copypaste off
/copypaste on
/copypaste off private
/copypaste on private


Command: /Creative {on|off} <private>
Turns creative mode on or off for all players. Add the word "private" for you only.
This works on Single player, as well as Multiplayer.
Note that the game mode listed in the game Lobby screen where players see your server to join it, this will not change.
Notes:
On a Listen Server Hosted game, if the "Private" setting is used in Multiplayer anyone connecting after making a change will also inherit them.
On a dedicated server with the "Private" setting on, you can:

drop single blocks at any range, however they will only have 1% construction even though they appear 100% to you.
remove any block instantly as per normal.
drop a line or grid of blocks, these will be 100% constructed unlike single blocks.
allows you to have copypaste.
Examples:
/creative off
/creative on
/creative off private
/creative on private


Command: /Spectator {on|off} <private>
Turns Spectator mode on or off for all players. Add the word "private" for you only.
This works on Single player, as well as Multiplayer.
Note:
On a Listen Server Hosted game, if the "Private" setting is used in Multiplayer anyone connecting after making a change will also inherit them.
Examples:
/spectator off
/spectator on private


Command: /Weapons {on|off} <private>
Turns Weapons on or off for all players. Add the word \"private\" for you only.
This works on Single player, as well as Multiplayer.
Notes:
On a Listen Server Hosted game, if the "Private" setting is used in Multiplayer anyone connecting after making a change will also inherit them.
Weapons settings work strangely if only turned on for 1 player, and it is not advised to use this at all.
Examples:
/weapons off
/weapons on private


Command: /cyberhounds {on|off} or /cyberhound {on|off} or /hounds {on|off} or /hound {on|off}
Turns Cyber Hounds on or off for all players.
This works on Single player, as well as Multiplayer.
Examples:
/hounds off


Command: /spiders {on|off} or /spider {on|off}
Turns Spiders on or off for all players.
This works on Single player, as well as Multiplayer.
Examples:
/spiders off


Final Notes:
It will say "Server Creative On" if you set a session command globally or "Creative On" when set privately.

When you switch a session command on or off for the server, other Admins will see a notification of the change. Regular players will not.


****



The following are Admin only commands for ship management:


Command: /listprefabs {filter}
List ships in the Prefabs.
Optional {filter} to refine your search by name.


Command: /addprefab {#}
Add the specified {#} prefab. Spawns the specified prefab ship directly in front of player.


Command: /addwireframe {#}
Add the specified {#} prefab as an un-built ship. Spawns the specified a ship 2m directly in front of player.


Command: /adddrone {#} or /addpirate {#}
Add the specified {#} prefab as a pirate owned and controlled ship. Spawns the specified a ship 2m directly in front of player. If the prefab is configured with a programmable block and timer, these will run any logic.
example: /adddrone assailant_mk.1


Command: /cuberenumber <name>
Renumbers the custom names of terminal blocks. Use '*' for wildcards.


Command: /cuberename <name>
Renames and renumbers the custom names of terminal blocks back to their original. Use '*' for wildcards.


Command: /deleteship {#}
Deletes the specified {#} ship, or the ship in the player crosshairs.
Examples:
/deleteship Largeship 1234
/deleteship
/deleteship #23


Command: /destructable On|Off {#} or /destruct On|Off {#}
Set the specified {#} ship as destructible or indestructible, or the ship targeted in the player crosshairs. Ship will be removed and regenerated to apply the setting.
Examples:
/destruct On #1234
/destruct off
/destruct off largeship 4867


Command: /pasteprefab {#}
Pastes the specified {#} prefab from clipboard (Works only in Creative mode, ignores disabled Copy/Paste.)


Command: /listships {filter}
List in-game ships/stations.
Optional {filter} to refine your search by ship name or antenna/beacon name.


Command: /elistships {filter}
List in-game ships/stations, position and distance.
Optional {filter} to refine your search by ship name or antenna/beacon name.


Command: /stop {#}
Stops the specified {#} ship. Turns on dampeners, and initiates thrusters. Unpowered ships will also stop. Includes attached rotors and pistons!
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /off {#}
Turns off all reactor and battery power in the specified {#} ship.
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /on {#}
Turns on all reactor and battery power in the specified {#} ship.
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /claim {#}
Claims ownership of the {#} specified ship. All own-able blocks are transferred to you.
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /revoke {#}
Removes ownership of all cubes in specified {#} ship.
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /share{#}
Share ownership of the <#> specified ship to All, without removing the original owner.
Works on a specific {#} ship, or the targeted ship in the player crosshairs.


Command: /scaledown {#}
Converts a large ship into a small ship, also converts all cubes to small.
Cubes that do not have a match will be removed.
Note, this is still in progress and some cubes do not have a correct rotation. Subgrids are not supported as yet (wheels, rotors, pistons).


Command: /scaleup {#}
Converts a small ship into a large ship, also converts all cubes to large.
Cubes that do not have a match will be removed.
Note, this is still in progress and some cubes do not have a correct rotation.
Subgrids are not supported as yet (wheels, rotors, pistons).


Command: /switch [power] [prod] [prog] [proj] [sens] [spot] [timer] [weapon] on/off
Turns globally on/off the selected systems, including of any of following; Power, Production, Programmable Block, Projector, Sensor, Spot lights, Timer, Weapons.
Examples:
/switch project off
/switch progr timer off
/switch weap off


****

On the first start your server will create two files. One is a config file (it's named like 'Config_{worldId}.cfg') the other contains your message of the day (usually named like 'Motd_{suffix}.txt). Simply type any text in the motd file, save it and it will appear in a mission screen when you join the server. But keep in mind that you need to restart the server once you edited the file to make the changes appear ingame. We'll add a command for dealing with anything related to the motd later. If the file doesn't contain any text, the motd is disabled thus no mission screen will appear.

File locations
Configuration files will be stored in the following locations.

Single player and privately hosted games: %AppData%\SpaceEngineers\Storage\316190120.sbm_midspace.adminscripts

Dedicated Server: %AppData%\SpaceEngineersDedicated\Storage\316190120.sbm_midspace.adminscripts

Dedicated Server service are stored under name of the Service instance: C:\ProgramData\SpaceEngineersDedicated{ServiceName}\Storage\316190120.sbm_midspace.adminscripts

Configuration:
The other file contains the server configuration. The file is XML based, for learning how to use XML please visit [Apenas Administradores podem visualizar links] The server configuration contains several settings and we might add some more later. Currently it contains the following:

'WorldLocation'
This is not a setting at all. It just let you know to which world this cfg is connected so that you don't have to search which one has the id the file name contains.

'MotdFileSuffix'
This setting refers to the suffix of your motd file. By changing it you can set several worlds to one motd file or each world to another one. If you change it and no file with this suffix can be found, a new empty motd file will be created. By default it is the name of the world.

'MotdHeadLine'
With this setting you can set a title to your message of the day. It will appear as the objective of the mission screen the motd is displayed in. Don't use too many characters here otherwise they might appear outside the mission screen. About 30 characters should be fine in most cases.

'MotdShowInChat'
If this is set to true, the motd will appear as a chat message instead of a mission screen. Keep in mind that the head line will not appear in chat.

'LogPrivateMessages'
This setting determines if private messages are logged or not. By default the logging is enabled.

'ForceBannedPlayers'
The information about forcebanned players is stored here. I do not recommend making changes here.

'AdminLevel'
This setting sets the level for admins. By default it is 100.

'EnableLog'
This setting determines if debug information is logged. Usually you don't need to as the information is not relevant for you. By default the logging is disabled

'NoGrindIndestructible'
This setting determines if ships that are set as indestructible can be grinded or not. By default the grinding is allowed.
Example: /config ngi true

Motd variables:
There are some variables you can use in the text of the motd that will be initialized when the server starts. Currently the following are available:

%SERVER_NAME% - will be replaced by the server's name.
%SERVER_PORT% - will be replaced by the server's port.
%WORLD_NAME% - will be replaced by the loaded world's name.
%USER_NAME% - will be replaced by the user's own name.
If you have ideas for further variables please let us know.



***



Players and commands have certain levels. A level is a positive number from 0 to 4,294,967,295. A player can not use a command that has a higher level than his own level. The default administrator level can be set in the config and is set to 100 by default. Normal users have a default level of 0. The default level for admin commands is also set to 100 but the default value can not be changed. The user commands have the level 0.

Moreover custom groups can be created that have a level and members. All members will have the level of the group. If a player is member of several groups he will get the level of the group with the highest level. Furthermore the player himself has a level that must be activated by setting "useplayerlevel" to true, otherwise the group level or, if the player is not member of any group, the default level will be used.

Through the setlevel, individual commands can also be disabled and removed from access from either your general players, or all players including admins.
Additionally you can extend the rights of a specific player for a specific command, i.e. the player will always have access to the command regardless of any levels. The contrary, restrictions of certain commands, is also available.


This command is used for organizing the permissions ingame.
Syntax: /perm <domain> <action> [<subject> [<parameter>]]
Domains: command, player, group
Each domain has specific actions.

Actions:

For 'command'
setlevel
Sets the needed level for a command to the specified level.
Example: /perm command setlevel help 100

To remove access to all players use the word none.
Example: /perm command setlevel motd none

list
Creates a hotlist containing all commands and provides information about the needed level of the commands. Use a keyword to refine your search
Example: /perm command list roid

For 'player'
setlevel
Sets the level of a player to the specified value. Remind that you have to set useplayerlevel to true otherwise using this won't make any difference.
Example: /perm player setlevel MyPlayerName 150

extend
Grants the specified player to use the specified command regardless of his level. When a player has extended rights use 'restrict' to restore normal permissions. When a player has restricted rights you can use this command to restore normal permissions.
Example: /perm player extend MyPlayerName tp
-> If the player had normal access to the command, he will be able to use it from now regardless of his level. If the player had restricted access to the command he will have normal access from now.

restrict
Prevents the specified player from using the specified command regardless of his level. When a player has restricted rights use 'extend' to restore normal permissions. When a player has extended rights you can use this command to restore normal permissions.
Example: /perm player restrict MyPlayerName tp
-> If the player had normal access to the command, he won't be able to use it any longer regardless of his level. If the player had extended access to the command he will have normal access from now.

useplayerlevel
If set to true the level of the player will be used. By default it is false.
Example: /perm player useplayerlevel MyPlayerName true

list
Creates a hotlist containing all players and provides information about them. Use a keyword to refine your search Example: /perm player list

For 'group'
setlevel
Sets the level of a group to the specified value.
Example: /perm group setlevel mygroup 150

setname
Sets the name of a group to the specified value.
Example: /perm group setname mygroup mynewgroupname

add
Adds the specified player to the specified group.
Example: /perm group add mygroup MyPlayerName

remove
Removes the specified player from the specified group.
Example: /perm group remove mygroup MyPlayerName

create
Creates a new group with a specified name and a specified level
Example: /perm group create mygroup 150

delete
Deletes the specified group.
Example: /perm group delete mygroup

list
Creates a hotlist containing all groups and provides information about them. Use a keyword to refine your search
Example: /perm group list
Examples:

To permanently elevate a particular player to full Admin

You will need to use the following commands, to first find the player you wish to elevate (they may have complex name or spaces in their name), and then set their permission level, following by instructing the system to use that number otherwise they will only inherit permissions from their group or default level.
/perm player list
The player you may choose in this example is #3.
/perm player setlevel #3 100
/perm player useplayerlevel #3 true

To remove commands from access by regular players

Utilize the /perm command setlevel command, to raise the required access for a command to 100 so that only Admins can use them.
/perm command setlevel chat 100
/perm command setlevel date 100
/perm command setlevel head 100
/perm command setlevel hello 100
/perm command setlevel motd 100
/perm command setlevel pos 100
/perm command setlevel status 100
/perm command setlevel settings 100
/perm command setlevel time 100
/perm command setlevel version 100

To remove them from Admin access also, use the word none instead of the level.
Example: /perm command setlevel motd none


***************************************



This command is used for private communication. Beware that it can be logged on the server. It can only be used in multiplayer.
If you can't type a name, e.g. because it contains symbols, use '/status' to create a player hotlist. There are several enhancements in this command to make private communication easier. Here is a list of all commands and their functions:


Command: /msg {player} {message}
Aliases: /tell, @
To use an alias just replace the command name with the alias. /tell {player} Hello and @ {player} Hello is the same as /msg {player} Hello
Function: Sends the specified {player} a private {message}.


Command: @@ {message}
Function: Sends a {message} to your 'whisperpartner'.


Command: @@@ {player} <message>
Function: Sets the specified {player} to your 'whisperpartner' and optionally sends him a private <message>.


Command: @@@@ <message>
Function: Sets your 'whisperpartner' to the last player who whispered to you and optionally sends him a private <message>.


Command: @@@@@ {message}
Function: Sends a private {message} to the last player who whispered to you.


Command: @?
Function: Shows you the name of your whisperpartner.




****************************


NOTE: This feature is considered as work in progress. We won't be responsible for any damage that might occur even if your ship is inside a protection area.

Introduction: Protection Areas
Protection areas are our "anti grief solution". If a ship/station is inside a protection area, only players who own at least one block of that ship/station are allowed to modify it. This means that you can grind block of a ship only if you own one block of that ship already. Ships that are owned by nobody can be modified by anyone. The same rule applies for adding blocks.

If a block is not fully built yet, someone finishes it and he does not have the right to modify the grid, the ownership will be transferred to the owner of the most blocks on the ship. Unfortunately we cannot know for what reason the ownership changes which leads to the fact that inside protection areas you cannot transfer the ownership of a block to a player who does not already own a block on that ship.

Furthermore a ship that is inside a protection area cannot be damaged in any way but grinding.

If you find any bugs concerning the logic of protection areas or if you have other requests, please let us know.

Planned Features:

More messages: Improve the feedback in certain cases e.g. if a player is not allowed to grid a block
Won't fix (things we cannot do at the moment):

Disable coloring
Attention:
Ships can still be pushed out of the areas or be hijacked e.g. by attaching them to landing gears and pulling them out of the area. Be sure that you always attach your ship to an entity that cannot be moved. Also be careful with connectors.

Command: /protectionarea
This command is used to administrate protection areas. They can be added, removed and listed. Inside of protection areas grids cannot be damaged and only be modified by players who own one or more blocks on the ship.

/protectionarea add <name> <x> <y> <z> <size> <shape>

Creates a protection area at the given coordinates with the given size and shape. The name is a unique identifier, so choose it wisely!
Example: /pa add Safezone 0 0 0 5000 sphere
-> Creates a sphere with the radius 5000 at the position X: 0, Y: 0, Z: 0. Inside the sphere nothing can be destroyed.

Shapes:

cube, cubic
sphere, spherical
/protectionarea remove <name>
Removes the protection area with the given name.
Example: /pa remove Safezone
-> Removes the protection area named Safezone if it exists.

/protectionarea list
Lists all protection areas.

/protectionarea config <setting> <value>
Sets the specified setting to the given value.
Example: /pa cfg invert true

Settings:

invert
Inverts the protection so that everything is protected but objects inside protection areas.
enable
Enables or disables the whole protection.
Alias: /pa
We know that '/protectionarea' is a bit long. Just use '/pa' instead and be happy!


****


The following commands create numbered hotlists, so they can be reused repeatedly in an associated command.

/status, /listbots, /listprefabs and /listships

The hotlist persists for the entire session, until you reissue the same command that will replace the hostlist, or the item in the hotlist is no longer available.

Examples:

/status -> /slay #5

/listprefabs red -> /addprefab #3

/listprefabs red -> /pasteprefab #4

/listships large -> /claim #5

/listships large -> /revoke #1

/listbots -> /fj myfactionname B2







FINAL