Skip to main content

Troubleshooting

Common issues and quick fixes for first-time setup and live session flow.

Login and Account​

Problem: I cannot log in​

Try:

  1. verify email/password
  2. refresh once and retry
  3. use password reset if needed

If issue persists, check your auth provider configuration and environment values.

Sessions​

Problem: Session does not appear as live​

Try:

  1. open Sessions tab and confirm status is active/live
  2. reload once after starting the session
  3. confirm you are in the expected campaign

Problem: Player cannot join with code​

Try:

  1. copy a fresh session code
  2. verify session is still active
  3. confirm player is logged into the correct environment

Maps and Tokens​

Problem: Map will not load​

Try:

  1. re-open the map from the Maps tab
  2. verify the map image exists and was uploaded successfully
  3. confirm campaign/map relationships are valid

Problem: Token not visible to player​

Try:

  1. check token visibility state (visible, hidden, fog)
  2. confirm player is in the same live session/map context
  3. reload player view once

Problem: Grid looks wrong​

Try:

  1. verify grid size value
  2. adjust grid X/Y offsets
  3. re-open map after saving grid settings

Initiative​

Problem: Initiative appears out of sync​

Try:

  1. switch tabs and return
  2. reload the affected client
  3. confirm session context is the same for all users

Encounter Presets​

Problem: Preset does not appear in apply modal​

Try:

  1. verify map and room context match where it was saved
  2. verify encounter key context if one was used
  3. confirm the preset has saved token rows

Subscription and Access​

Problem: Feature appears locked unexpectedly​

Try:

  1. refresh profile/account state
  2. verify plan status
  3. if using tester access, confirm is_tester is enabled for that user

Testing and Local E2E​

Problem: Playwright UI exits immediately​

Try:

  1. start the static server first on expected port
  2. run e2e tests directly if UI mode does not stay open in your shell context

Example server start:

npx --yes serve . -p 64021

Still stuck?​

Capture:

  1. what you clicked
  2. what you expected
  3. what happened instead
  4. any visible console or error output

Then route it through your support workflow for triage.