Game Updated to Version 1.1.2g - DEMO UPDATED
[h3]DEMO UPDATE:[/h3][p]I just updated the demo. There was a problem with some of the maze areas in the Vaults of Zin, that would allow players to get "outside" of the level into a kind of dark, void area. You can read more about how this problem occurred and how it was fixed here... [/p][p]https://steamcommunity.com/app/2958790/discussions/0/666096879249241746/
and here...[/p][p][dynamiclink][/dynamiclink]So, while I fixed the problem a while ago, I believe it was still present in the free demo, so players bringing their game from the demo could still encounter the bug.[/p][h3]
Other Bugs[/h3][p]Several other bugs have been identified and fixed. One major bug has been addressed but I am not quite sure if it is fixed or not, so I will be asking for feedback from players.[/p][p][/p][h3]Nightgaunt Issues[/h3][p]There was a certain circumstance in which having a Nightgaunt take you to a dungeon could reset that dungeon's map. I believe this is resolved. I was able to reproduce the issue, and implement a fix that stops it from happening. It's possible there are other situations that could produce a similar result, but I was not able to find any.[/p][p][/p][h3]Mealstrom Issue[/h3][p]The Maelstrom would not show the correct text in the archive in roguelike mode.[/p][p][/p][h3]Betrayal Issue[/h3][p]The game will warn you if you are about to betray an alliance. I loved the idea of having the actual button change to "betray" instead of combat, but stealth can also trigger a betrayal event, so it did not make sense to change both buttons to "betray." Instead I just put a warning in the action log with a sound, giving player notice that they might be breaking an alliance. [/p][p][/p][h3]Quicksave and Quickload Temporarily Disabled - Feedback Request[/h3][p]Sorry about this. I got feedback from a player who had been using these commands often, and somehow all their game data got deleted. I never use quicksave or quickload, I just got used to using the menu, and I have never encountered this, so my suspicion is that quicksave and quickload are somehow responsible. [/p][p]Have you encountered any issues with quick-save or quickload? Do you use them a lot? Have you lost game data before? [/p][p]I think (and maybe hope) the problem may have been caused possibly by something outside of the game ... maybe a power surge or general issue with the player's computer, but it's entirely possible there is a bug I am just unaware of. [/p][p]I tried spamming quicksave and quickload, but I was unable to produce any similar errors. Maybe I am just not hard enough on my games when I test them. I know that is a thing I have. But if anyone out there wants to be really mean to the game and spam quickload/save, I would be grateful if you could provide how, when and where the game fails to save data correctly. [/p][p][/p][p][/p][p][/p][p][/p][p][/p]
and here...[/p][p][dynamiclink][/dynamiclink]So, while I fixed the problem a while ago, I believe it was still present in the free demo, so players bringing their game from the demo could still encounter the bug.[/p][h3]
Other Bugs[/h3][p]Several other bugs have been identified and fixed. One major bug has been addressed but I am not quite sure if it is fixed or not, so I will be asking for feedback from players.[/p][p][/p][h3]Nightgaunt Issues[/h3][p]There was a certain circumstance in which having a Nightgaunt take you to a dungeon could reset that dungeon's map. I believe this is resolved. I was able to reproduce the issue, and implement a fix that stops it from happening. It's possible there are other situations that could produce a similar result, but I was not able to find any.[/p][p][/p][h3]Mealstrom Issue[/h3][p]The Maelstrom would not show the correct text in the archive in roguelike mode.[/p][p][/p][h3]Betrayal Issue[/h3][p]The game will warn you if you are about to betray an alliance. I loved the idea of having the actual button change to "betray" instead of combat, but stealth can also trigger a betrayal event, so it did not make sense to change both buttons to "betray." Instead I just put a warning in the action log with a sound, giving player notice that they might be breaking an alliance. [/p][p][/p][h3]Quicksave and Quickload Temporarily Disabled - Feedback Request[/h3][p]Sorry about this. I got feedback from a player who had been using these commands often, and somehow all their game data got deleted. I never use quicksave or quickload, I just got used to using the menu, and I have never encountered this, so my suspicion is that quicksave and quickload are somehow responsible. [/p][p]Have you encountered any issues with quick-save or quickload? Do you use them a lot? Have you lost game data before? [/p][p]I think (and maybe hope) the problem may have been caused possibly by something outside of the game ... maybe a power surge or general issue with the player's computer, but it's entirely possible there is a bug I am just unaware of. [/p][p]I tried spamming quicksave and quickload, but I was unable to produce any similar errors. Maybe I am just not hard enough on my games when I test them. I know that is a thing I have. But if anyone out there wants to be really mean to the game and spam quickload/save, I would be grateful if you could provide how, when and where the game fails to save data correctly. [/p][p][/p][p][/p][p][/p][p][/p][p][/p]