Troubleshooting

Gameplay is unavailable

Check the host message under Lua → Existing scripts and Action status on the Spawner/Unlocks page. An unsupported game build disables gameplay hooks. Use the current Scooby release for your game version; UI access alone does not mean the gameplay host is ready.

Spawning or item grants fail

Start an active run with a living player, refresh the content list and check whether another batch is busy. Item stack/challenge restrictions and powerup limits can refuse an action. Unlocking requires a loaded writable progression save.

Language updates fail

The embedded languages remain available without a download. If a download or integrity check fails, keep the current catalogs and try again later. Edited files are deliberately preserved; rename the edited locale JSON if you want to restore the distributed version.

Lua script errors

Read Lua → Console, check the API docs and use the bundled examples. Player/run snapshots can be nil outside a run or after a stale sample, so test for a value before reading fields.

Hotkeys or values do not take effect

Check the activation mode and parent feature, and finish text editing before testing a hotkey. A second timer, XP, level or gold lock can take priority. Saved configs can restore a previous value or binding.

For account and connection issues, use General help. Include the game version, host message and affected feature when reporting a problem.