Before You Report A Problem

Quick Fixes Worth Trying First

The public build is browser-first and local-first. Most issues come down to cached assets, viewport state, or a browser holding an older service-worker build.

Browser and app basics

  • refresh the page or relaunch the app after a deployment
  • rotate the device into landscape before entering the duel
  • confirm the latest assets loaded after a cache-bust update
  • restart the browser or wrapper if the full-window stage looks incomplete

Local profile and save checks

  • your display name and handle are saved only in this browser for the public launch
  • clearing site storage removes local progress, settings, and cached assets
  • the public build does not use cloud save, ranked, friends, ghost, or live leaderboards

What to send in a support request

  • device model and OS version
  • browser name and version, or native wrapper build number
  • what mode you were in when the issue happened
  • the exact steps that triggered the problem

What is intentionally offline

The public browser launch has no payments, no ads, no push notifications, no live leaderboard traffic, and no remote diagnostics. If you see those references anywhere, report them as a bug.

Support Form

Send A Browser Build Report

Use the form below to report bugs, balance issues, save problems, or visual glitches. Replies go to the email address you provide, and the inbox address itself stays private.

Support request

No file uploads are enabled. If helpful, include the duel mode, opponent, browser, or screen in the message itself.

How replies work

  • support requests are processed by Formspree and forwarded to the private Dust to Dust inbox
  • replies go to the email address you enter in the form above
  • the form only asks for your name, reply email, issue type, and a short description of what happened
  • do not send passwords, payment information, or private account credentials
  • the public build does not require billing, purchases, or live-account recovery for normal play

Quick summary: if the browser build misbehaves, use the support form and describe what happened as clearly as you can. Most fixes still come down to a hard refresh, a reopened tab, or a stale cached build.

Back To Frontier Site