Unable to Progress due to saves

Issue #126 resolved
Former user created an issue

I noticed where you had game Saves as Trivial, but honestly, it's game breaking. I enjoyed many of the Earlier Dungeon Depth's versions. But due to this, it's become a chore to play. As a professional Quality Analyst at Microsoft, I'll give you everything I know about the bug.

Bug #1 (Minor): Changing Portrait due to saving.

Repro Steps: 1. Created a new character and get into gameplay. 2. Gain items and save. 3. Continue to save and watch skin darkens on the portrait. Observed Behavior: Every time a save file is saved over the skin color of the player character changes. Unsure if linked to save/load issues.

Expected Results: Unless this is by design I would expect for the portraits to remain the same as the character was originally made, not changing color.

Bug #2(Unable to load Saves): 1. Get into Gameplay and progress through the game. 2. Save Often as you gain items. 3. Typically, by the third floor Save and Return to the title screen. 4. Observe behavior.

Observed Behavior: Save Files will stop working either by not infinite loading screen, or with an error message forcing the user to start over.

Expected Results: It is Expected that when a user saves they are able to continue their game without losing all game progress.

Note: If you need help I'll be willing to give you a hand to attempt to prevent further breaks, but this bug makes the game almost unplayable.

Comments (3)

  1. V H. U repo owner

    I have the bug with the saves marked as trivial because I figured out what was causing the saves past floor three to fail, and it is more or less resolved as of the last build of the master branch of this repository. I had missed that the floor layouts aren't tracked past floor 4, and that caused a index-out-of-bounds exception that causes loading to fail.

    I did not know about the first bug though, thank you for reporting it. I am currently working on debugging what I have thus far so as to post a patch within the week.

  2. Log in to comment