11. Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
Repositories page says unreachable / Could not read repo.json from this URL. | The URL does not point at the folder holding repo.json, or the host is down. | Copy the exact URL from your community, open …/repo.json in a browser, then Reload details. |
nimby inspect fails with an HTTP error | Same, or the server rejects the request. | Test the URL; re-add the repository; use --user/--pass on nimby repo add if it needs a login. |
… exists and is not managed by Nimby; pass --force to replace it | The @mod folder came from another client or was made by hand. | Confirm it is the same mod, then nimby install --mods "@mod" --force, or move the folder away. |
| Linking fails on exFAT or a network share | Those file systems cannot host the hardlinks and junctions Nimby uses. | Set link mode copy (nimby config set --link-mode copy, or nimby install --mode copy). Slower and it uses full disk space, but it works. |
A mod reports drifted after a Steam update | The Workshop item behind the link changed. | nimby repair, or reinstall that mod. |
| Hashing is slow, the disk never idles | Antivirus scans every file Nimby reads. | Keep the hash cache and add the workspace root, the store and the app folder as folder exclusions in Windows Security. |
command line would be … characters (limit 8191) | Too many mods or a deep workspace path. | Shorten the workspace root, split repositories, install fewer mods. |
| I cancelled by mistake — is progress lost? | No: cancel stops after the current file and keeps verified data. | Run Install again; the log shows what was kept. |
| I need logs | The GUI shows the last 300 lines only. | Use the log panel, or run the command with --progress text / --progress json; nimby doctor prints environment facts. |
| Launch is refused with "Arma 3 is already running" | A previous arma3_x64.exe is still alive. | Close the game and launch again. |
| Everything is misconfigured | — | Close Nimby and delete data\config.json (portable) or %APPDATA%\Nimby\config.json. Defaults come back; installed mods are untouched. |
Deleting hashcache.json beside the configuration file is always safe; it is rebuilt as files are hashed again.