Troubleshooting

The bot says "On Cooldown" and won't fight

This mirrors the game's own cooldowns (arena fights, dungeon free fight, etc.) — it's not a bug. The Next free fight / cooldown timer shown in the app comes directly from the game server.

A module isn't running even though I enabled it

1. Check Settings → Core and confirm the module's toggle is actually on for the character you're looking at — settings are per-character.
2. Hit Save & Apply rather than just Save, so the change takes effect immediately instead of on the next natural cycle.
3. Check the Logs tab for warnings related to that module — resource shortages (e.g. not enough mushrooms or beer) will block a module from running even when it's enabled.

The app won't log in

• Double-check your S&F credentials work by logging in through the game's own website or client first.
• If your account uses SSO (Google/Discord/Apple login on the game side), make sure you're using the login method the app supports for your server.
• Check the Logs tab for the specific error returned by the game server.

The arena isn't fighting at all

Minimum win chance applies only to fights you pay a mushroom for. It has never blocked a free fight, so changing it will not explain a completely idle arena.

Check both toggles. Arena fighting and scrapbook hunting share one free fight and are one module. With both Auto Arena and Auto Scrapbook off, nothing happens.

On versions before 2.10 this was a real fault: two modules with two copies of the rules that disagreed, and the strict copy could veto every target. The log said so all along — "none of the 47 players above us cleared the 55% win-chance minimum". Updating fixes it.

The Arena Manager (Idle Game) does nothing

The game unlocks it at level 105. Below that there is nothing for the module to do. From 2.12 the log says which of the two it is rather than staying quiet.

The Tower or dungeons never fight

They share one daily fight. Before 2.11 the Tower sent the floor you had already beaten instead of the one you were entering, so the server refused it — and because the Tower usually wins the comparison, the fight was spent on nothing. A refused Tower now steps aside for an hour so the dungeons get the attempt.

My saved accounts disappeared

Fixed in 2.12, and it was two separate faults. Clicking a saved account replaced the character list instead of adding to it, so accounts you had already logged in vanished from the screen while their bots kept running in the background. And the account file was emptied before being rewritten, so closing the app or installing an update in that moment left it blank.

The file is now written alongside the old one and swapped into place in a single step, and a copy of the previous list is kept. A damaged file is reported in the log and recovered from that copy instead of quietly looking exactly like never having had any accounts.

Accounts lost on an older version cannot be recovered — they have to be added once more.

The log is flooded with the same lines

Turn on quiet logging in Settings → System. Refusals that are part of normal play do not need a line every cycle. On versions before 2.12, also update: refused actions were re-sent every few seconds rather than being set aside.

Still stuck?

Use the Send Report button in the app's Logs tab — include your platform (Windows/macOS/Linux), the app version, and what you see in the Logs tab.