-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Check full-face adjacency, loaded chunks, and that the network has exactly one Core. If the Core reports the network scan limit, shorten or split the route.
Run /auto_storage recover_core before placing another token. It reissues only your latest owned and unclaimed recovery.
Existing types remain stored, but a new exact identity cannot enter. Add or upgrade Storage Units, or remove an unneeded variant.
Install the matching station. If the preview remains neutral, the recipe may be dynamic, random, incomplete, external-machine based, or otherwise outside the atomic contract.
A complete craft must fit together with every container remainder. Clear Player or Core space, or switch Craft Output. A failed capacity check consumes nothing.
- Select a compatible Transform card and verify the input's runtime value.
- Keep a bound Remote Core and its route loaded in the same dimension.
- Install Fusion only if connected casing is desired; it is not needed for function.
0.3.0 has a new technical identity and does not migrate old worlds or data. Remove the old jar, keep only one Auto Storage version, and start a new world.
Still stuck? Open an issue with the Auto Storage version, NeoForge version, mod list, reproduction steps, and relevant logs: https://github.com/swear01/Auto_Storage/issues.