How the RUST Entity Deleteby Command Works
The RUST entity.deleteby command permanently destroys all entities created by one or more players across the entire map (bases, deployables, etc.). It’s most commonly used to clean up after cheaters or abandoned megabases, or to enforce building rules at scale. This admin command must be used with great care as it’s a global action and cannot be reversed.
Quick Reference
| Command | entity.deleteby |
| Type | Console Command |
| Default Value | N/A |
| Usable By | Admins, Moderators (Requires authlevel 2) |
Command Syntax
entity.deleteby <SteamID64>Parameters & Values
- The
<SteamID64>is a unique 17-digit numerical ID that represents a player’s Steam account. - Enter multiple <SteamID64> IDs, each separated by a space, to destroy multiple players’ entities at one time.
- While the command can also accept player names in quotes, we highly recommend avoiding this, as it can catch partial player name matches.
Usage Examples
Delete all entities by a single player:
entity.deleteby 76561198000000000Delete all entities by multiple players:
entity.deleteby 76561198000000000 76561198011111111 76561198022222222Tip: There’s a sister command,
entity.deletebytextblock, that parses a pasted block of text (output from theent authcommand) and deletes by any SteamIDs it finds.
Entity Deleteby Command Notes
Permissions & Use
- Usable by both Moderators and Admins.
- This command cannot be undone, and its effect is permanent.
- When executed, the players’ entities are destroyed in the order the SteamID64 IDs are entered. If multiple players are entered at the same time, you may experience a slight delay in the entities being destroyed.
- Warning: If you are destroying a large number of entities, expect additional server load and lag spikes. Take a snapshot or backup of your server and consider notifying your players before executing the command as a courtesy.
Finding the Right Steam IDs
- Use
ent whowhile looking at an object in-game to return the player’s SteamID64. - Use
entcount <SteamID64>to estimate the impact before you execute the command.
Practical Use Cases
1. Cheater Cleanup
When a player’s been identified as a cheater and has built bases unfairly, or spammed deployables, the entity.deleteby command lets admins wipe every illegitimate entity they placed in one command. This avoids punishing innocent players nearby while removing all traces of the cheater’s construction.
2. Abandoned Bases & Server Performance
Large, unused builds can cause lag and server bloat. If a player has quit or been banned but their structures remain, admins can target their SteamID and clear everything they authored to free up resources using this command.
3. Rule Enforcement
If your server bans building in certain zones (e.g., around monuments, roadways, or RP hubs), entity.deleteby gives admins the power to remove all structures from offenders without a map-wide wipe.
4. Group Removals
When banning or removing an entire clan from a RUST server, you can pass multiple SteamIDs in one command to delete all authored entities by those members at once. This ensures nothing is left behind.
5. Server Debugging & Testing
During testing, admins often need to reset areas quickly without restarting the server. entity.deleteby is a helpful command for clearing authored objects in seconds. This is also very useful when developing Oxide Plugins.
FAQ
It removes the entity (box, furnace, deployable, etc.) Any contained items are effectively lost with the destruction.
You can, but it’s highly recommended to use the player’s SteamID64 for reliability.
Mass entity deletions can spike the load on the server. It’s best to run this command during off-peak times and consider segmenting large jobs by ID. Use the entcount command to size the job first.
