PDA

View Full Version : 2.53.0: Old Version Bug: Wizzrobes Appear in Walls



Nightmare
08-27-2017, 08:36 AM
https://www.youtube.com/watch?v=ABqBF0ZlQCo

Playing old quests that came before the enemy editor in 2.53, Wizzrobes (especially Scatterrobes) appear in walls in dungeons. This is definitely incorrect behavior.

-James

Saffith
08-27-2017, 02:50 PM
It's a bug that existed in old versions and has been deliberately maintained. If I remember correctly, there was an old quest that was actually unbeatable in 2.50 RCs 2-4 because Wizzrobes needed to appear in walls to hit a switch.

Nightmare
08-27-2017, 04:15 PM
It's a bug that existed in old versions and has been deliberately maintained. If I remember correctly, there was an old quest that was actually unbeatable in 2.50 RCs 2-4 because Wizzrobes needed to appear in walls to hit a switch.

2.50 had the enemy editor. 1.90, 1.92 B 183, and 2.10 did not. (this only applies to when there was no enemy editor)

-James

Saffith
08-27-2017, 06:17 PM
I mean to say that the bug was fixed with no backward compatibility in RC2 (maybe RC3? It's messy around there), and it was added to the enemy editor and enabled in old quests in RC5. Wizzrobes do appear on walls in 2.10. I don't know for sure whether they do in older versions.

Tamamo
08-27-2017, 08:13 PM
They sure in hell aren't suppose to, if people are abusing bug exploit then it's there own damn fault. It should of never been changed back.
It broke the nes compatibility with numerous old nes style quest for what, a handful of freaking quest that are using a bug to hit a switch.
Yeah not on my watch Saffith.
I'll be fixing this tomorrow.

tl;dr

Order of priorities is this and always will be...

1. NES Consistency
2. ZC Backwards Compatibility
3. New Features
4. Someone's GB when someone actually gives a damn

Gleeok
08-27-2017, 10:16 PM
I've never seen Wizzrobes appear in walls in 2.10 or the NES. It's just really ugly to allow this at all. Do you remember what revision this was changed in?

This may also related to the Gleeok heads that pass through walls which can (and does in at least one quest) breaks old quests.

Tamamo
08-27-2017, 10:56 PM
I agree, all fliers should be updated to prevent this from happening.
It's not related though, it is a separate issue however. That fliers ignore dungeon borders and shouldn't.

Gleeok
08-28-2017, 01:20 AM
"Fixed" the wizzrobe bug in the loosest sense of the word. Whatever quest that exists that requires that behavior is not yet supported in 2.50.4 and requires another fix.
Fixed the offset collision again also.
The flier bug is still in the air (pun intended) however. :P

ZoriaRPG
08-28-2017, 09:38 AM
"Fixed" the wizzrobe bug in the loosest sense of the word. Whatever quest that exists that requires that behavior is not yet supported in 2.50.4 and requires another fix.
Fixed the offset collision again also.
The flier bug is still in the air (pun intended) however. :P

Let me know when you are going to push this, or send me a proof of it please, so that I may see what you changed. I would specify the QHeader for 2.10.x for this, or whatever guys version was used in 2.10.0->2.10.2, and make that an exception. If people want to open a 2.10 quest and re-save it in 2.50, then they can have the fixed pattern. No reason to break quests that are years-old, in the process.

Most of the 2.10 questmakers are no longer around, to correct design flaws that rely on behaviour that was perceived (at the time) to be proper.

I do remember quests in 2.10 that had enemies in walls as triggers, inside dungeon rooms. Sorry. People did this.

Someone should check if 1.92.x Wizzrobe behaviour was such, that they could spawn in walls, too. I think that spawning in walls became a problem around the time that fire or bat Wizzrobes were added. If any of you have a system that can run 1.92, please let me know; as otherwise I will need to fire up an emulator to check this.

Tamamo
08-28-2017, 12:32 PM
It would of begun whenever no flying enemy combos were introduced which i do believe was weather 1.92 or 2.10 can't remember which

Gleeok
09-05-2017, 08:34 PM
Figured it out. The 2.10 compatibility fix by Saffith was good; it's actually two other issues, possibly the same bug, possibly different. Tricky little buggers, these ones.