How to Trigger the Detector Reliably for Testing

Why you need a repeatable trigger

A stack trace is only useful if you can reproduce it. The detector fires whenever world random access happens off the main thread, so you want an action that consistently causes that access.

Steps

1. Note what you were doing when the crash happened: exploring new chunks, generating structures, loading a world, or running a specific machine.

2. Create a fresh test world with the same seed and mod set so conditions are identical.

3. Perform the suspected action in isolation. For chunk generation issues, fly or teleport into ungenerated terrain rather than walking slowly.

4. Watch the log live by keeping latest.log open in a tailing viewer, or check it immediately after the action.

5. If nothing appears, increase the load: generate many chunks at once, run multiple world-affecting machines, or use a world with heavy structure generation.

6. Record the exact sequence that produced the trace so you can hand it to the mod author.

Tips

Off-thread access often only shows under load, because a race condition needs timing to line up. If you cannot reproduce it on demand, run the detector during normal play and keep logs from every session so you catch it when it happens.