-
Notifications
You must be signed in to change notification settings - Fork 0
troubleshooting
solutions to common issues, from auto-roll not working to save transfers and music problems.
cause: almost certainly your browser throttling or sleeping the tab.
browsers like microsoft edge and opera gx aggressively sleep inactive tabs to save resources. when the tab is asleep, rolls don't fire.
fix: look for and disable the following settings in your browser:
- "battery saver" or "energy saver" mode
- "sleep tabs" or "tab sleeping"
- "resource saving" mode
- "cpu/ram limiter"
alternatively, stay on the tab while it rolls, or switch to a browser that doesn't aggressively throttle tabs (chrome and firefox are generally more reliable for this).
cause: you missed a day or week. the streak resets if you don't claim within the window. this is working as intended, not a bug.
cause: you've hit the 100mb custom music limit.
fix: remove existing custom tracks to free up space before uploading new ones. the limit applies to the total size of all your uploaded music combined.
first check: make sure "mute music" is unchecked in settings. if it's checked, uncheck it.
if it's already unchecked: this is likely a browser restriction. some browsers block audio until the user interacts with the page.
- try a different browser - chrome and firefox tend to handle audio best
- make sure you've clicked somewhere on the page at least once before expecting music to play
cause: a known browser quirk where the custom music state gets out of sync on load.
fix:
- go to settings
- check "mute music" and save
- uncheck "mute music" and save again
this toggle cycle usually fixes it.
try the built-in transfer first. if it fails, use the manual console method:
open the browser console (press f12 → click console, or right-click → inspect → console).
some browsers block pasting into the console by default. type this first and press enter:
allow pasting
you may not see any response - that's normal.
⚠️ security warning: never paste code from strangers into your browser console. the code below only touches game localstorage keys. always read code before running it.
now paste this and press enter:
copy(json.stringify(
object.fromentries(
['rarityinventory','totalrolls',
'achievementsunlocked','anomalies',
'anomaliesused','shoppoints',
'shopupgrades','soldoutrarities',
'playerpotions','activepotions',
'wishingwell','luckbooststate',
'totalplaytime','daily_lastclaim',
'daily_streak','weekly_lastclaim',
'weekly_streak','gauntletdata',
'notifications','mutationsunlocked',
'mutationhistory','_beacon_v2',
'usersettings','starmapdata',
'runesdata','runeblocks','runegift',
'runeupgrades','mutationtrust',
'mutationtrustowned','mutationtrustactive']
.filter(k => localstorage.getitem(k) !== null)
.map(k => [k, localstorage.getitem(k)])
)
));your save data is now copied to your clipboard.
open its console, type allow pasting, then paste the following - replacing paste_here with the data you just copied:
object.entries(
json.parse(`paste_here`)
).foreach(([k,v]) => localstorage.setitem(k,v));
location.reload();the page will reload and your save should be restored.
report it in:
- discord: #bugs channel at discord.gg/mTDw8jJYqX
- nerimity: nerimity.com/i/K0zUp
- github issues: github.com/auth1ery/auths-RNG
- email: hello@authsrng.xyz
if you cleared localstorage without saving your cloudbackupuid:
unfortunately, there is no recovery option. the backup system has no accounts and therefore no password reset or identity recovery. your cloud data is permanently inaccessible without the uuid.
to prevent this in the future: after enabling cloud backups, copy your backup key from settings and store it somewhere outside the browser (a notes app, a text file, etc.).
- when in doubt, try chrome or firefox - they have the most consistent behavior with the game and the game is tested on these browsers!
- the nightly build (nightly.authsrng.xyz) may have bugs by design - don't use it for your main save
- if something seems broken but worked before, a browser update or extension may be interfering - try disabling extensions or using a private/incognito window