When I loaded a custom quest in 219, the combo table didn't load (it instead kept the default). This was maintained upon quitting without saving and tryign to play the quest. It doesn't do it every time, and I haven't been able to reproduce it (although thankfully I keep a quest backup and was able to restore combo data from that).
(219) ZQuest resets combo table
Did you by any chance get a copy of the text in allegro.log?
Sadly no, and I haven't seen the bug again since. I think it may have been related to my computer (which has had a few stubborn moments lately), rather than a direct bug in ZC, especially since nobody else seems to be reporting the problem.
Woah woah woah!!! I think this same bug just occurred to me in b224.
I opened a test quest of mine to edit a few things, everything seemed ok so I saved and quit and that seemed to go fine as well. Well when I open the quest again I see that the combo table was reseted... but PERMANENTLY for this quest file. So the quest file is now ruined. No worries though, it was just a test quest, nothing important, but this is a horrible, awful, scary as hell bug... O_o
Oh god, this is going to be a bitch to track down. Did you get any kind of error message at all, either during saving or loading the corrupted quest?
DarkDragon wrote:Oh god, this is going to be a bitch to track down. Did you get any kind of error message at all, either during saving or loading the corrupted quest?
Nope. No error messages, no weird behaviour whatsoever. That's really weird eh? Now every time I try to open the file in ZQuest or ZC, all I see is a mess of combos because the combos seem to be reseted to the setup they have in the original quest...
Guess what, I may have found out what causes this bug!
When this bug occurred, I remember I added a map to the map count. I just tried it with another quest: I increased the map count by a few maps, but everything seemed to be ok after that. However, after I saved and reloaded the quest, everything was fucked up.
So I am pretty sure it's the increasing of Map Count that makes this bug happen. I hope this info helps you to locate and fix the bug.
Petoe wrote:Guess what, I may have found out what causes this bug!When this bug occurred, I remember I added a map to the map count. I just tried it with another quest: I increased the map count by a few maps, but everything seemed to be ok after that. However, after I saved and reloaded the quest, everything was fucked up.
So I am pretty sure it's the increasing of Map Count that makes this bug happen. I hope this info helps you to locate and fix the bug.
It did that in a test quest I was doing in 16c, too. Problem is.... IT DELETED ALL COMBOS AND TILES! And when I opened the tile editor.... Poof. Instant crash. So... This bug's been around since 16c!
Holy shit, that's a little serious. I'll look into it right away.
Fixed in the next build. There was a nice little bug where tiles on the new maps weren't being saved, confusing the loader, which interpreted combo data as that missing tile data instead.
Unfortunately your quests are corrupt beyond hope of recovery; the tiles simply aren't there.
DarkDragon wrote:Fixed in the next build. There was a nice little bug where tiles on the new maps weren't being saved, confusing the loader, which interpreted combo data as that missing tile data instead.
Unfortunately your quests are corrupt beyond hope of recovery; the tiles simply aren't there.
Good thing it was only a simple test quest and not a REAL quest....
Yet another reason why everyone is always reminded to make COPIES of their quests so that they don't lose anything. Nice find guys and it's great that you were able to fix it so quickly DD.
DarkDragon wrote:Holy shit, that's a little serious. I'll look into it right away.
quote of the day :laughing::rofl::googly:
If this really is fixed so fast and so easily, my hat's off to you DD! 😊