NgDinhNha · DEVLOG AbyssalBits — When My Emulator Ran An Old Build I had fixed the bug in the code, but the emulator kept showing the broken version. The fresh build and install matched the current source. The build I was looking at was not the one I thought I was running. View on Google Play English Tiếng Việt 日本語 English What happened when my emulator ran an old build AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened when the emulator showed an old build. The source was current and the game was old After a round of cleanup, I launched the game on an Android emulator and it showed an old version label on the loading screen, along with older UI that I had already fixed. I opened the source and the newer implementation was right there. Nothing in the code explained what I was seeing. Why it matters...
NgDinhNha · DEVLOG AbyssalBits — When Quest Progress Followed The Wrong Hero A fresh hero could start with another hero's quests, and the first dungeon would not open. Behind it sat one piece of state that outlived the character it belonged to. View on Google Play English Tiếng Việt 日本語 English What happened when quest progress followed the wrong hero AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened when quest progress followed the wrong hero. A new hero with someone else's quests When you create a fresh character or start a new Ascension run, the game writes an empty quest list into the new save. The quest manager, however, is a process-global singleton. It lives as long as the app is running, so it still held the quests of whichever hero was loaded before. When the player reached town, the game only see...