fireball docs

Troubleshooting

Common issues and solutions for Fireball

Having issues with Fireball? Find solutions to common problems below.

Account Issues

My account is pending

Accounts are approved in batches to monitor infrastructure. Your account should be approved within a few hours to a few days.

I can't sign in

  1. Make sure you're using the same Abstract wallet as your Gigaverse account
  2. Check that your wallet extension is connected properly
  3. Try refreshing the page and signing again
  4. If using Discord login, ensure your Discord is linked to your Gigaverse profile

"Limited Session" banner appears

This means your Gigaverse session has limited access. Try signing out and back in, or check that your Giga-Juice is active.

I can't switch accounts

The account switcher only shows accounts under the same wallet. If you don't see an account, make sure it's associated with the currently connected wallet.

Gameplay Issues

My runs aren't starting

Check that you have:

  • Sufficient Spark balance (or an active Scroll of Noob)
  • Active Giga-Juice effect
  • Enough energy for the selected dungeon/fishing type
  • Not reached your daily limit for that game type
  • Proper gear equipped (especially for dungeons — check durability)

A job shows as "Failed"

Hover over the failed job status to see the error message. Common causes:

  • Gear broke mid-run (enable autorepair to prevent this)
  • Session expired during the job
  • Energy depleted before all runs completed
  • Gigaverse API temporarily unavailable

Runs seem stuck

Fireball runs in the background, so the UI may not update instantly. The Jobs page auto-refreshes every 30 seconds. If a job appears stuck for an extended period, try refreshing the page.

Daily limit reached but I have energy

Each dungeon and fishing type has its own daily limit. Check the Dungeon Types or Fishing Types reference for exact limits.

Spark Issues

I ran out of Sparks

Purchase more from the Sparks page. Use the cost calculator to estimate how many you need.

Purchase failed or Sparks didn't arrive

  1. Check your wallet for the transaction — if it went through, Sparks typically process within 60 seconds
  2. Refresh the page after a minute
  3. Check the Transactions page for the purchase record
  4. If the transaction confirmed on-chain but Sparks haven't appeared, contact support on Discord

"Period limit reached"

Each account can purchase a maximum of 20,000 Sparks per 30-day rolling period. Wait for older purchases to fall outside the 30-day window.

Service Issues

Service not running

Check that you have:

  • An active Gigaverse session (check expiration in sidebar)
  • Sparks available (unless you have Scroll of Fire)
  • The service is subscribed (not just configured)

Reveal shows no results

If the service hasn't had anything to process since your last reveal, the results will be empty. For example, the Fish Seller only acts when you have fish to sell.

Notification Issues

Not receiving push notifications

  1. Check browser notification permissions — look for the lock icon in the address bar
  2. Ensure notifications are enabled in Fireball Settings
  3. Verify the specific notification types you want are toggled on
  4. On mobile, make sure Fireball is installed as a PWA

Notifications are blocked

If you previously denied notification permissions, you'll need to re-enable them in your browser:

  • Chrome: Click the lock icon → Site settings → Notifications → Allow
  • Safari: Preferences → Websites → Notifications → Allow
  • Firefox: Click the lock icon → Permissions → Notifications → Allow

Technical Issues

The page won't load

  1. Clear your browser cache
  2. Try a different browser
  3. Disable browser extensions that might interfere
  4. Check if fireball.gg is accessible

Wallet connection problems

  1. Ensure your wallet extension is up to date
  2. Try disconnecting and reconnecting your wallet
  3. Check if the wallet works on other dApps
  4. Try a different browser

Getting Help

If your issue isn't listed here:

  1. Join our Discord
  2. Post in #bug-report with as much detail as possible
  3. Include your account name, what you were trying to do, and any error messages

Our community and team are happy to help.

On this page