How the RUST Entity Delete By Text Block Command Works
The entity.deletebytextblock command parses a specially formatted text block you provide as a parameter, for SteamIDs, then permanently deletes all entities created by players whose IDs were identified. This is particularly useful when copying results from commands like ent auth, where multiple player IDs are listed together. It works as a batch-processing version of entity.deleteby, saving admins time when removing builds from groups, cheaters, or abandoned clans.
Quick Reference
| Command | entity.deletebytextblock |
| Type | Console Command |
| Default Value | N/A |
| Usable By | Admins, Moderators (Requires authlevel 2) |
Command Syntax
entity.deletebytextblock <textblock><textblock>: A block of text containing one or more SteamID64 values. Quotes must surround the block. This command’s parameter must start with ” and close with “ and the player IDs must be at the start of each line.- The command scans the block, extracts valid SteamIDs, and deletes all entities created by them.
Warning: This is a global action across the entire map. Once entities are deleted, there is no undo.
Parameters & Values
- The
<SteamID64>is a unique 17-digit numerical ID that represents a player’s Steam account. - Enter multiple <SteamID64> IDs, each separated on a new line, to destroy multiple players’ entities at one time.
Usage Examples
Delete from an ent auth output
entity.deletebytextblock "
76561198000000001 John Doe
76561198000000002 Billy Bob
76561198000000003 SarahBigBlocks
76561198000000004 Rocketman
76561198000000005 Michelle
"If your input doesn’t conform to the above syntax, you will receive an error message that reads: “Invalid arguments, provide a text block surrounded by ” and listing player id’s at the start of each line“
Entity Delete By Text Block Command Notes
Permissions & Use
- Usable by both Moderators and Admins.
- This command cannot be undone, and its effect is permanent.
- It can be run from the server console, in-game console, or RCON.
- 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.
- Long text blocks may perform better through RCON due to console input limits.
Finding the Right Steam IDs
- Use
console.clearto clear your console of text. - Then, to get a list of Steam IDs and player names, use
ent authon a Tool Cupboard in-game. - Now use
console.copyto copy the output of the previous command and format it appropriately.
Practical Use Cases
1. Cheater Cleanup
When multiple players have been identified as cheaters and have built bases unfairly, or spammed deployables, the entity.deletebytextblock 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 Steam ID 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.deletebytextblock gives admins the power to remove all structures from multiple offenders quickly 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.
FAQ
The Steam ID must be first on each new line; everything else after that doesn’t matter.
No. This command does not work with player names.
Yes, but your server performance will suffer. It’s best to run large batch jobs during off-peak hours.


