Using Cupboard Logs to Troubleshoot Crashes and Chunk Lag

When a heavily modded world crashes, lags during exploration, or breaks a command, vanilla Minecraft often hides the exact cause. Cupboard Mod upgrades your game's logging output so you can pinpoint the problem yourself.

Finding Detailed Crash Stacktraces

Normally, Minecraft may cut off long error messages. Cupboard forces full stacktrace details to appear during a crash.

1. Open your Minecraft instance folder and open the crash-reports directory.

2. Open the newest text file matching the time of your crash.

3. Read the full stacktrace lines under the main error heading. Look for recognizable mod names listed inside the lines of code to identify which specific mod caused the failure, then remove or reconfigure that mod.

Checking Command Errors and Chunk Loading

If an in-game command silently fails, or your game freezes briefly while generating terrain, check your live logs:

1. Open the logs folder inside your Minecraft directory.

2. Open latest.log (or debug.log if enabled in your launcher) with a text editor.

3. For broken commands: Run the failing command in chat, then scroll to the bottom of latest.log. Cupboard records command errors here, showing why a command failed to execute.

4. For exploration lag: Search the log file for chunk loading entries. Cupboard records debug logs for synchronous chunk loading, helping you see if a specific mod is forcing chunks to load on the main game thread and freezing your tick rate.