Most Essentials commands live under the !ess prefix and are typed in the global chat (or run from the server console). The player-only !stone command keeps its legacy top-level name, and a few commands also have the short form known from Torch:

The arguments of a short form need a Magnetar release newer than 2.4.3.4; 2.4.3.4 and older run only the bare forms and answer "Unknown command" to !fixship MyShip. Magnetar itself provides !save, !restart, !stop and !quit. The host suppresses recognised command lines from normal chat.

• !ess — overview of available commands.
• !ess help — list commands; !ess help <command> shows usage for one.
• !help — list every server command across all plugins.

Arguments: <required>, [optional]. Quote "multi word" values. Booleans accept true/false, yes/no, on/off, 1/0.

Permissions use Space Engineers promote levels, lowest to highest: None < Scripter < Moderator < SpaceMaster < Admin < Owner. A caller below a command's level does not see it in the overview. Commands without an explicit level require Admin.

Drive auto command sequences and the server lifecycle.

MOTD opens through the Plugin SDK mission-screen API when MagnetarMod is available; otherwise it falls back to private chat output.

Homes are stored per Steam ID in Essentials.Homes.xml under the server user-data folder. Limits and enablement are configured on the Homes tab.

The Info Commands tab defines public, top-level commands such as !rules or !discord. Each row needs a Command name and at least one response: ChatResponse sends private chat text, NotificationResponse shows a center-screen notification only to the player using the command, DialogResponse opens a mission screen (or falls back to private chat when mission screens are unavailable), and URL sends an HTTP(S) link in chat and opens it in the Steam overlay. NotificationDurationMs sets that row's notification display time in milliseconds; 0 uses the default of 5000. Set multiple response fields to use them together. Empty rows are ignored. Names are case-insensitive, and any words after the command name are ignored. Registered commands from Magnetar or other plugins take precedence, so an info command named like one of them, fixship or reload for example, never answers; !ess, !stone, and !help cannot be used as custom info names.

Toggle or remove functional blocks across all (non-projected) grids. Block type is the object-builder type without the MyObjectBuilder_ prefix (e.g. Reactor, ShipWelder); subtype is the block subtype id.

Destructive cleanup and world-maintenance commands require running the same command again within 30 seconds to confirm. Cleanup grid commands evaluate logical grid groups and skip piloted grids unless haspilot is included.

Cleanup conditions include: name <regex>, blockslessthan <count>, blocksgreaterthan <count>, pcugreaterthan <pcu>, pculessthan <pcu>, hasgridtype <large|small|ship|static>, hasownertype <npc|player|nobody>, haspower / nopower, insideplanet, playerdistancelessthan <meters> / playerdistancegreaterthan <meters>, poweredgriddistancegreaterthan <meters>, centerdistancelessthan <meters> / centerdistancegreaterthan <meters>, ownedby <player|identityId|steamId|nobody|npc|pirates>, hastype <type> / notype <type>, hastype-fast <type[,type...]> / notype-fast <type[,type...]>, hassubtype <subtype> / nosubtype <subtype>, hassubtype-fast <subtype[,subtype...]> / nosubtype-fast <subtype[,subtype...]>, and haspilot.

The Cleanup tab also has Grid Look Notifications. Add a row with cleanup condition arguments (for example, blockslessthan 20 hasownertype player) and a message such as Please repair or move {GridName}; it matches a cleanup rule. Only a player listed in the grid's BigOwners sees the HUD notice, when looking directly at that grid from their character within 500 m. Rules use the same logical-group matching and default pilot exclusion as !ess cleanup scan. The first matching row is shown. Set CleanupLookReminderMinutes to choose how often the player is reminded (1–1440 minutes, default 1). After the first notice, reminders continue while the player is online, owns the grid, remains within 500 m of its position, and its rule still matches, even after they look away. A reminder that no longer qualifies is cleared; looking at a matching grid again starts a new notice. Between reminders the plugin does not raycast or evaluate the rule for that player. At a reminder time, a different matching grid the player is looking at takes priority. Initial look checks run at most once every three seconds. Empty rows have no effect.

Voxel reset commands restore storage from the original data provider. Destructive commands require running the same command again within 30 seconds to confirm. Protection commands change the corresponding Quasar settings immediately and save them to the Essentials configuration. Use on or off to set protection.

Find, stop, delete and power-toggle entities, plus common grid administration. entities delete and grids static large require running the same command again within 30 seconds to confirm. [gridName] defaults to the grid the caller is looking at where supported. For protect, -allowDamage leaves block damage enabled and -allowEdit leaves building/removal enabled; using both is equivalent to unprotect.

<player> is a player name or identity id. * affects all players. onlyOnline limits to online players; excludeNpcs (default true) skips NPC identities. eco deposit and eco withdraw convert physical SpaceCredit items between accessible inventories on the looked-at grid group and the caller's account.

Cuts and re-pastes a grid to clear physics/clang issues. Behaviour (cooldown, confirmation window, projector handling, ejecting players) is governed by the Ship Fixer config tab; the player !ess fixship command (and !fixship) can be disabled there. Each command also has the short form without !ess.

On a Magnetar cluster a node cuts and pastes only grids it owns and simulates. A grid named (or given by id) that is on another node is found there: every node is asked, the one holding the grid answers the confirmation and does the fix, and the cooldown applies on every node. A grid that is moving between nodes at that moment is refused with "The grid is moving between servers right now. Try again in a few seconds."

Inspect ownership/authorship and transfer PCU/ownership of a grid. [gridName] defaults to the grid you are looking at. Transfers respect block limits unless a force… variant is used. Player-facing claim/sale/rename workflows require the caller to already own or have faction-share access to all owned functional blocks in the target grid group.