[Solved] Sun Icon Class failed to unlock

[Jareth]

After reaching the prerequisites for unlocking this class (Sunkeeper), a brief cutscene played showcasing it in action, but after that finished the game map froze with no text appearing or anything. Only thing I could do was quit to the main menu.

Sadly, upon returning to the campaign, I'm able to continue but the class is not available when choosing to make a new mercenary. Has anyone come across this before? Is there a workaround to get the class to unlock again?

[Jareth]

Used a checkpoint to try and restore it to just before it was unlocked, but seems it is indeed bugged. Fully repeatable for me when you Reach reputation level 10.

The only thing I can think of that may have caused the conflict is that one of my current mercenaries life goals also has the same class as a reward unlock, though, they're personally not close to achieving that yet.

[Lampros]

Originally posted by Jareth:

Used a checkpoint to try and restore it to just before it was unlocked, but seems it is indeed bugged. Fully repeatable for me when you Reach reputation level 10.

The only thing I can think of that may have caused the conflict is that one of my current mercenaries life goals also has the same class as a reward unlock, though, they're personally not close to achieving that yet.

Man, that sucks ♥♥♥♥. I hope I don't run into the same problem.

I am doubly worried, because I do have two characters with quests to unlock the same class (Saw).

[Jareth]

OK, found a way to get it to work. If anyone else comes across this problem, the moment you reach reputation 10, if the class doesn't immediately unlock, it will normally trigger the moment you finish doing something else, city event for example. That's where it's broken at the moment and could freeze your game then become permanently unavailable. This is what happened to myself after confirming with the checkpoint saves.

Trick is to exit to the main menu immediately when you reach reputation 10, and then resume the campaign. The class will unlock successfully the moment you load back in.

[RbdPanda]

Should probably post this in bug reports or report it to their discord

[Lampros]

Originally posted by Jareth:

OK, found a way to get it to work. If anyone else comes across this problem, the moment you reach reputation 10, if the class doesn't immediately unlock, it will normally trigger the moment you finish doing something else, city event for example. That's where it's broken at the moment and could freeze your game then become permanently unavailable. This is what happened to myself after confirming with the checkpoint saves.

Trick is to exit to the main menu immediately when you reach reputation 10, and then resume the campaign. The class will unlock successfully the moment you load back in.

Thanks much!

[Lampros]

Where are your game saves, by the way? I want a back-up before Reputation 10 reaches just in case.

[Jareth]

I followed the sticky regarding corrupted saves, it's for guildmaster, but same applies for campaign. You can find them here:

C:\Users\yourname\AppData\LocalLow\FlamingFowlStudios\Gloomhaven\GloomSaves\Campaign\yourpartyname\Checkpoints

Just then need to copy one of those one level up to replace the .dat that's in the party campaign directory.

[Lampros]

Originally posted by Jareth:

I followed the sticky regarding corrupted saves, it's for guildmaster, but same applies for campaign. You can find them here:

C:\Users\yourname\AppData\LocalLow\FlamingFowlStudios\Gloomhaven\GloomSaves\Campaign\yourpartyname\Checkpoints

Just then need to copy one of those one level up to replace the .dat that's in the party campaign directory.

Thanks!

[Silt]

I had this happen to me yesterday. After finishing a Gloomhaven town scenario I had the following happen:

One of my mercenaries completed their personal quest, so they retired and unlocked a class.

The finished scenario raised my reputation high enough to unlock the Sun class.

One of my remaining mercenaries personal quest would have unlocked the Sun class, so it was switched to opening up a quest and an item design...I guess since now the Sun class auto-unlocked.


After all of this happened, I briefly looked at the two new unlocked classes and then quit the game. When I logged back into the game later on, my one mercenary that had just retired was back in the line up and their personal quest tracker was back to where it was before the scenario that he retired after. That Gloomhaven scenario he retired after was still showing as completed. The class he unlocked when he retired was still unlocked, even though now he wasn't retired any longer. The Sun class was now missing and the mercenary that had the personal quest that would unlocked the Sun class was back to having that as his personal quest reward.

A very strange sequence of events.

What I ended up doing was first making a backup copy of the following directory:

C:\Users\yourname\AppData\LocalLow\FlamingFowlStudios\Gloomhaven\GloomSaves\Campaign\yourpartyname\

Then I copied the last scenario checkpoint save from:

C:\Users\yourname\AppData\LocalLow\FlamingFowlStudios\Gloomhaven\GloomSaves\Campaign\yourpartyname\ScenarioCheckpoints

up a folder level to:

C:\Users\yourname\AppData\LocalLow\FlamingFowlStudios\Gloomhaven\GloomSaves\Campaign\yourpartyname\

and overwriting the file that was there, which seems to be the file that is loaded when you start up the game.


Doing this when I started the game again, it loaded back to that previous check point in the scenario I finished earlier that kickstarted off all of the above. When that scenario ended, all of that same unlocks, etc happened. This time before exiting the game I did a few things that caused the game to auto-save (you can tell by the save icon in the upper right). The easiest way to do this is to change the skins of any of the default starting classes as the game auto-saves each time you do this. I did this a few times to make sure to notice the game auto-saved, then I exited the game. Going back into the game everything is now as it should be.

A super weird bug. I'm not sure if what I did with forcing auto-save to kick in a few times before exiting the game is what fixed this issue but it's fixed none the less now. Let me tell you, I was a little annoyed that after so much stuff happening post scenario it had mostly all been reset. I will make it a habit to periodically back up my entire save folder now in case something like this happens again. I'm too far along this campaign for things to get borked.