#Troubleshooting

#The pack is not offered

Confirm renderer.resource-pack.enabled and send-on-join are true.
Confirm external-url is public HTTP or HTTPS, or enable the built-in host.
Open the URL in a browser from another device.
Restart after changing host settings.

#Enhanced mode still looks legacy

The renderer is chosen when the session starts. Wait for the successful pack status, run /bcade stop, then reopen the game. Check that renderer.mode is not LEGACY.

#Borders or symbols look wrong

Confirm whether the affected player accepted the pack. Legacy uses vanilla fonts and is intentionally simpler. For enhanced mode, clear the client's server resource-pack cache and reconnect so the current atlas is downloaded.

#WASD moves the player or does not control the game

Check for movement, anticheat or lobby plugins cancelling events before Blockcade. Test /bcade input left. On a current Paper version, check startup compatibility information with /bcade info.

#Resource pack host works locally but not remotely

Do not use 127.0.0.1 as public-host for remote players. Configure the public hostname or IP, forward the port and allow it through the firewall. For production, an HTTPS CDN or web server is preferred.

#`NoClassDefFoundError` during development

Stop and restart the test server. Do not rebuild or replace an archive that the active server loaded directly. The included Gradle runServer task copies the plugin into its run directory to avoid this problem.

#Old displays remain in the world

Run /bcade cleanup. Startup and shutdown also remove orphaned Blockcade-tagged displays in loaded chunks.

#Configuration warnings

The warning includes the file, key, invalid value and fallback. Correct the key and restart when it belongs to hosting, storage or async rendering. Avoid /reload from Bukkit or third-party reload plugins.