§4. Help

4.1. Troubleshooting

Something not working? Start with /tracel status (if it works at all), then find the symptom below.

Symptom	What to do
/tracel or a command is missing	It's a permission, not a bug. Check with /tracel help as console
Lookup shows nothing, but it happened	t: too narrow, s: is around you not the thing, the kind is off in [logging], history was purged, or it was a natural change (#world / #all)
Rollback: no scope given	Rollbacks need both t: and s:
Rollback: the world kept changing under it	Stop whatever keeps moving things (piston, water, hopper), rerun
Rollback: cannot touch...	Make the chest / entity reachable again, rerun
Another job is running... Wait for it to finish	One export / import / purge / migration at a time. Wait, or #stop it
Lookup failed	Smaller time range or scope; check the server log
Upload failed on export	The server cannot reach the paste server — firewall, or change [paste]
The server cannot write to the export folder*	Give the server user write access to plugins/Tracel/database/exports
The disk is full	Free space, or purge
State: degraded, behind by...	Disk is slow, or the server is flooded. Check disk; consider sync / capture-ring-slots in [advanced]
Forward-compatibility in status	Your server is newer than what Tracel was tested on. It should work; report weirdness
Config change did nothing	Restart. Options Tracel cannot read are reported in the console and fall back to defaults

4.2. Reporting a bug

Open an issue on GitHub or ask on Discord. Please include:

1. The output of /tracel status
2. The exact command you ran
3. What you expected, what happened
4. The relevant part of the server log
5. Tracel's version and your server's

Caution

If the problem is dangerous — history that can be altered, erased or forged, a rollback that destroys data, a way around permissions — do not post it publicly: not in an issue, not on Discord. Report it privately through GitHub Security Advisories. Such bugs should never exist, but things happen.