13 replies to this topic

[ywkls]

Okay, this happened to me in version 2.5.1, using the Dance of Remembrance (Hybrid) tileset. Of course, something similar happened in a different quest; in a different tileset in 2.5.1; but I don't know if the two are related.

 

So, I load my saved game after correcting the latest errors that I'd found. No sooner has my game loaded than all of my hearts are drained and I am warped back onto the screen. Then, a mysterious force (no better way to describe it) starts moving Link down. He responds to button presses, but can't really go anywhere and keeps sliding along until he hits a solid object.

 

I tried killing Link to see if he'd revive with full health, but that didn't seem to change things. The only other thing I can think of doing is healing him somehow. But, what gets me is that there's no reason he should be doing this in the first place!

 

In my other game, Link just lost all but 3 hearts after I loaded my game when I was close to the end. I can only conclude that my saved files were somehow corrupted in both cases.

 

Since I couldn't get past this in any way I could determine, I was forced to start over. Hopefully, it won't show up again before I finish the game.

 

I know mine isn't script-related, since the scripts were running fine before this and once I loaded a new game, everything worked like it should. Since script-related bugs are some of the most common, I think it would be interesting to hear about some of those too.

 

So, any other strange bugs that have been encountered? And any ideas on what caused this one or others like it?

[Eddy]

I don't think I've ever came across a ZC bug like that.

 

I actually don't think I've ever came across many major ZC bugs besides scripts crashing a quest because it was being played on the wrong version, but then again, that's kinda my fault for never reading the descriptions of quests which tell you what version to play a quest on

[Parsnip]

The weirdest bug I have ever encountered has been fixed, but on Windows 8 computers (I hate Windows 8 aghhhh!!!) ZQuest 2.5 wouldn't let you use the Items button. 

[Theryan]

That one time Ben possessed my quest and killed me to death irl. That was scary.

[SpacemanDan]

This. I can probably use ZC for the next century and never experience such a strange oddity as this one. While a script kicked it into motion, the very strange parts were not caused by the script itself.

[Valientlink]

Weirdest would have to be getting a clock and going to the next screen, but still having the clock. This has happened to one other person I know and it's extremely random/rare. It's happened to me in 2.5rc4 and 2.10.

 

There was also this weird bug with zq not being able to go to screen 83 when I first downloaded it. It would crash my entire computer, using the same computer now it doesn't have this problem.

Edited by Valientlink, 28 September 2015 - 11:46 PM.

[Kite]

There was a time where ZQuest thought I had a Japanese keyboard layout instead of a US keyboard layout despite all of my OS settings pointing to it being a standard US keyboard and there not being a Japanese keyboard layout selectable on my system from what I could tell. There are not many differences with basic ASDF keys since I could type full sentences with mostly correct punctuation, but it was impossible for me to type string control codes since the \ key wouldn't work. I managed to get around it by making an autohotkey script to bind \ to the keycode ZQuest thought \ was supposed to be. Thankfully this is fixed in 2.50.

Edited by Nick, 29 September 2015 - 12:22 AM.

[nicklegends]

This. I can probably use ZC for the next century and never experience such a strange oddity as this one. While a script kicked it into motion, the very strange parts were not caused by the script itself.

That was awesome.

It's since been fixed, but there used to be a bug in ZQuest where you could scroll past the very last combo in the combo selector. Most of these combos appeared as black, but you were allowed to edit them and place them on the screen. As you did this, random parts of memory seemed to get corrupted... Some aspects of the program treated the placed combos as any other, but other parts of the program treated the combos as if their number wrapped around to the beginning of the combo list (as if overflowing a 16-bit unsigned integer). It was weird because I was able to edit parts of memory I had no access being in. Who knows what else it screwed up in my quest.

[Magi_Hero]

Weirdest bug was when DC was streaming Isle of Rebirth and ZC had a seizure.

[MarinaraSauce]

This one time I loaded up a quest called "DayDay", and I think it corrupted ZC.

[Joelmacool]

This one time I loaded up a quest called "DayDay", and I think it corrupted ZC.

It happened to me as well, its a strange bug... 

But a weirder bug is that when ever I made a good detailed screen, loaded back up my quest and went to the screen... all the tiles mixed up. Weird huh? Must explain DayDay.

[Shane]

  

 

HELP

[Anarchy_Balsac]

  

 

HELP

 

Am I the only one who thinks that;s awsome?

[Lüt]

The dungeon-passageway warp-return-B reset.

 

I'm so glad I had a delay in my quest progress, otherwise I wouldn't have found this problem.

 

I put a passageway from a back room to an entry room in a multi-entrance dungeon. Since the entry already used warp return A, I set the passageway to use B. Then, when I went to the next level and went into the item cellars to get the items, I kept appearing at the same spot in the middle-left of the screen when I left the item cellars - and not where I put the warp return. I couldn't figure it out - until I exited a cellar in a room that had multiple warp gates, and I ended up on a ledge in the position of my warp return B. Turns out, if you set a passageway to use warp return B, all item cellars get their default warp return reset to B rather than A - so since I didn't have warp return B's in those rooms, I kept appearing in the default spot. It only reset to warp return A when I went into another passageway set to use warp return A. It also resets when you save a game, or use Farore's Wind. But I'm the kind who always saves, so I didn't realize what was happening until I did a final run without saving for long periods of time.

 

So, I swapped the passageway and entryway's warp returns, and all's good

 

Kind of strange though. This was in 2.50. I should try 2.50.1 or whatever's the latest version, and see if I can recreate it. If so, maybe it's unknown and I should submit a bug report on the official forums.