Just completed my run on new game +++ and got many missions completed but not the Try Hard With A Vengeance one. Maybe it's because there were around 5 missions completed at one time, overflowing the rewards. I've included pictures of the not completed mission and my stats so that my claim can be verified. I did sustain a hit during my new game +++ run but I believe one of my items saved me despite it me being a one shot at that point of new game +. All my hearts disappeared as well when I took the hit, but I'm not sure if that's normal I have never made it that far before. I was playing on a meta quest 3 but using steam vr from my pc if it helps.
#Completing Try Hard With A Vengeance did not register
5 messages · Page 1 of 1 (latest)
Edit- Just figured out that the reason I didn't get thrice baked beans is because I did not have the mission for it unlocked yet, which is hugely painful after playing 70 hours of the game prior to the new update. The newest update added missions where you have to unlock the previous missions (mostly consisting of things I've already done many times in previous updates) to unlock new ones. Since try hard with a vengeance was not unlocked yet for me at the time of beating my new game +++ run, I got my 50 blood but not my thrice baked beans 🙁 This will likely not happen to many more people, I unfortunately completed my new game +++ run during my first delve with the new update so I had no missions completed yet. My stats still show that I technically have completed the requirements for the mission, but before unlocking it. Would it be possible to introduce a patch that could award the challenge to people in my position, since the stats are hard proof of completion? I can't help but feel utterly robbed by the new mission mechanic after I have played so much of the game working toward one of its hardest challenges.
Hey. Thank you for the report and sorry about the issues!
Prior to starting the NG+ 3 run did you have 3 or more won runs? If so, even if you're coming from an older version the game should have given you all the quests as you played. Once you unlock a quest in a run you can immediately unlock any other quests, you don't need to go to the home base to claim it first. So it seems you ran into some kind of bug.
Would you be able to give us your save file so we could look deeper into the problem? You can send it in here or in a DM to me as it may potentially contain your account ID and username.
- On Steam you can find the save game folder by holding
windows key + Rand pasting this in there:%appdata%/../LocalLow/ErThu/Ancient_Dungeon. In there you will see Slot_0, Slot_1 and Slot_2. In those folders you can find your save files. The slots start at zero instead of 1, so if in the game you're using slot 1 that would be slot 0 in the folder. - On Quest the path is
Android/data/de.erthu.ancientdungeonfull, you should be able to get there by connecting the headset to a PC. In there you will see Slot_0, Slot_1 and Slot_2. In those folders you can find your save files. The slots start at zero instead of 1, so if in the game you're using slot 1 that would be slot 0 in the folder.
Also:
I did sustain a hit during my new game +++ run but I believe one of my items saved me despite it me being a one shot at that point of new game +. All my hearts disappeared as well when I took the hit, but I'm not sure if that's normal I have never made it that far before.
This is normal. The healthbar is disabled once you enter NG+ 3 as health becomes irrelevant at this point. Getting hit shouldn't cause any issues for the quests though 🙂
Hey Thom, thanks for the quick response! I have sent you my most recent save files. I did have more than 3 won runs prior to completing my NG+3 run, but I worry that things broke because I managed to complete the run on my first try with the new update. Thanks for the help 👍
Thanks for sending your save file and the extra info! Can I ask on what platform you play? (Steam, through the Rift app/store, Quest?).
Your save game seems fine to me, you have all the requirements that were needed for the achievements so there's definitely some weird bug that happened.