Breeding Farm Debug Codes -v0.6.1- -updated- -
Breeding Farm Debug Codes — Guide (v0.6.1)
7. Best practices for devs
- Validate all external inputs (mods, saves) before applying.
- Fail gracefully with transitional migration warnings (not hard crashes).
- Emit friendly recovery commands in ERROR to aid fix (e.g., "run save.migrate").
- Add telemetry markers for repeated BF-9xx codes to prioritize fixes.
The Risks of Using Debug Codes
While the 0.6.1 update made debug codes easier to use, be aware of the following:
- Cloud saves: Steam cloud may revert your debug-unlocked save. Back up your files locally.
- Multiplayer ban: If you are playing the co-op "Shared Farm" mode, debug codes are disabled. Forcing them via DLL injection will result in a permanent lobby ban.
- Soft-locks: Using
debug.time.add_daysduring a festival can break event triggers. Save first.
BF-901 — Critical init failure: config corrupted
- Cause: Corrupted config or missing essential file.
- Fix: Replace config with default
config/default.json; if persists, reinstall.