The Best Resource for Minecraft
The Best Resource for Minecraft

Crash Utilities Mod Wiki

Crash Utilities is a comprehensive server administration mod designed to help operators diagnose crashes, manage entity lag, monitor system memory, and remotely manage player inventories and positions.

7 sections · 889 words

Overview#

Crash Utilities is an essential toolkit for Minecraft server administrators, specifically designed to handle common maintenance tasks and emergency troubleshooting. The mod provides a suite of commands to retrieve logs, identify lag-inducing chunks, manage ground items, and assist players who are stuck or offline.

Unlike content-heavy mods, Crash Utilities focuses entirely on backend management and performance optimization. It does not add new blocks, items, or mobs to the game world, ensuring it remains lightweight while providing powerful diagnostic capabilities. It is particularly useful for modded servers where entity counts or tile entity complexities can lead to performance degradation.

Command Reference#

The primary interface for the mod is the /cu command. Most commands support tab-completion for player names, dimensions, and entity types.

Command Subcommand Arguments Description
/cu log N/A Provides options to upload or copy the latest.log and the most recent crash report.
/cu callItemClear N/A Manually triggers the ground item cleanup routine if enabled in config.
/cu entities list [dimension] Lists all loaded entities in the specified dimension (or current) sorted by count.
/cu entities find <type> [dimension] Lists chunks containing the specified entity type, sorted by count.
/cu tileentities list [dimension] Lists all loaded tile entities (TEs) sorted by count.
/cu tileentities find <type> [dimension] Lists all loaded TEs of a specific type with coordinates.
/cu memoryCheck [number] Displays a history of RAM usage over time.
/cu unstuck <player> Teleports a player to the Overworld spawn point. Works on offline players.
/cu tp <player> [dimension] <x> <y> <z> Cross-dimensional teleportation for online and offline players.
/cu inventory read <player> Displays the contents of a player's inventory, including Curios.
/cu inventory remove <player> [type] <slot> Deletes an item from a specific inventory slot.

Entity and Tile Entity Management#

One of the most powerful features of Crash Utilities is the ability to pinpoint sources of lag caused by excessive entities or complex tile entities (like machines or chests).

Entity Tracking

Using /cu entities list, administrators can see which entity types are most prevalent. Clicking on an entry in the chat output will automatically suggest the /cu entities find <type> command. This second command provides a list of chunks where those entities are located. Clicking the coordinates in the list will teleport the administrator directly to the chunk to investigate or clear the entities.

Tile Entity Tracking

Similar to entity tracking, the /cu tileentities (or /cu te) commands allow admins to find blocks that may be causing tick lag. This is especially useful for identifying "lag machines" or malfunctioning automated farms. The output provides direct teleport links to the specific coordinates of the tile entities.

Player and Inventory Management#

Crash Utilities allows administrators to interact with players even when they are not currently logged into the server.

Remote Inventory Access

The /cu inventory read <player> command generates a clickable list of every item in a player's possession. This includes:

  • Main Inventory: All 36 standard slots.
  • Armor Slots: Helmet, Chestplate, Leggings, and Boots.
  • Offhand: The item held in the offhand.
  • Curios: Full support for the Curios API, allowing admins to see rings, necklaces, and other accessory slots.

If an item is identified as problematic (e.g., a corrupted item causing crashes), the admin can click the item in the chat log to generate a /cu inventory remove command to delete it safely.

Unstuck and Teleportation

The /cu unstuck command is a fail-safe for players trapped in corrupted chunks or death loops. By sending them to the Overworld spawn, it resets their position safely. The /cu tp command extends standard teleportation by allowing admins to move players across dimensions without the need for the player to be online, which is critical for fixing character-data issues.

Automated Maintenance#

The mod includes an automated system to prevent server lag caused by too many items dropped on the ground (e.g., from a broken chest or an overflowing farm).

Ground Item Clearing

This feature is disabled by default and must be enabled in the server configuration. When active, the mod performs the following steps:

  1. Check: Every X minutes, it counts the total number of items on the ground across all loaded chunks.
  2. Threshold: If the count exceeds the configured limit, the cleanup process begins.
  3. Warning: The mod sends warnings to all players in chat at set intervals (e.g., 60 seconds before, 30 seconds before).
  4. Removal: All item entities on the ground are deleted to restore server performance.

Administrators can force this check at any time using /cu callItemClear.

Performance Monitoring#

The /cu memoryCheck command provides a snapshot of the server's RAM usage. It tracks the allocated, used, and free memory over a period defined in the configuration. This is vital for identifying memory leaks or determining if the server requires more dedicated RAM to handle the current modpack load.

Configuration#

The mod's behavior is controlled via the crashutilities-server.toml file located in the server's config folder.

Config Option Default Value Description
enableItemClear false Whether the automated item clearing system is active.
itemClearThreshold 2000 The number of items required to trigger a cleanup.
itemClearInterval 10 How often (in minutes) the mod checks the item count.
itemClearWarnings [60, 30, 10] Seconds before cleanup to broadcast warnings to players.
memoryCheckInterval 60 How often (in seconds) to record memory usage for the history log.
maxMemoryLogs 60 The maximum number of memory snapshots to keep in history.