Go to savedata -> achievements and change the date of "lastChallenge" is the best solutionġ. Phaser.js:38021 Phaser CE v2.11.1 | Pixi.js | WebGL | WebAudio ♥♥♥ĭungeon-generator.js:264 Uncaught DungeonGenerator.getLevelFeatures() TheSewers:5Ĭan I run another command through the console window to fix this?Įdit 1: (which is actually after 2 but I put before to keep shorter), Steam API has been initalized successfully! Seems I can't delete the files to restart the daily challenge, guess I'll miss today's daily challenge :(īrowse discussions some more and saw f10 then click console to get the logs: I don't think it's possible to start a game in the sewers 4, how would that happen? For me this is located at:Ĭ:\Users\Justin\AppData\Local\RogueFableIII\User Data\Default\SaveData\įor me this occur recently when trying to start a new challenge and I probably mess it up by force quitting after waiting too long? Anyways, at start page I get "Continue Game" and when I hover over it, bottom right reads:
Did you just update the game? Note, that the game may not update until you actually play so even though an update may be a few weeks old, your comp may have just updated.įor now, the solution, as explained in the popup file is just to go and delete the offending file. Are you on BOTH PC and Mac? Maybe this is the issue with cloud sync? Related to the above: did steam do its little song and dance before launching about syncing files? It sort of looks like an update. Do you play on multiple PCs? Apparently some google searches inform me that steam cloud sync occasionally mangles files.
Some things I can think of off the top of my head that might be relevant: So please reply to this thread if you experience this issue with as much information as you can about what occurred prior to this.
That being said, I'd like to track this one down (never actually seen it myself). I've now added a popup window that at least explains whats wrong and points towards the save directory so players can manually delete the offending save and continue playing. Previously the game would just fail to load (hang at 99%) and the console log would mention something about 'unable to parse token'. There appears to be a very rare but very bad bug that results in one or more of the games save files becoming corrupted.
0 kommentar(er)
