590 replies to this topic

[King Harkinian]

There's a small, but annoying problem that's very prominent in First/Second quest. In dungeons, when you go down the square stairs to the item rooms, the music starts over. Same thing with leaving that room. I don't believe this happened in the NES version.

[Xenix]

If you exit an area and come out of a stair warp, the stair warp on the destination screen can't be entered again until you exit the screen and come back.

[Mero]

I don't believe this happened in the NES version.

Yes it did, in fact there's a quest rule in nes fixes that corrects the problem.

[Mero]

Are unbeatable enemies suppose to count as enemies as far as how many enemies where left on screen when Link reenters it the next time? Because they do, and I rather see a fix implemented to make it so this doesn't happen, as it's quite tacky unless your going for a true NES quest.

Edited by blackbishop89, 02 May 2012 - 07:28 PM.

[Gleeok]

Because that would break many older quests. Changing stuff like that at this point would literally degrade ZC back to beta status and have to be tested all over again. Nobody wants to do that I'm sure.

[Eurysilas]

The time for implementing features is over. Some still don't seem to realize this.

[Mero]

Because that would break many older quests. Changing stuff like that at this point would literally degrade ZC back to beta status and have to be tested all over again. Nobody wants to do that I'm sure.

Would making it a quest rule that's off for older quest work then.

@Eurysilas. It's actually a bug from the original nes version if you ask me since it functions the exact same way. So no I'm not asking for a new feature, I even edited my post to prove that, just to have something fixed that should of been fixed a long freaking time ago.

Edited by blackbishop89, 02 May 2012 - 07:42 PM.

[Russ]

But it's not exactly a bug. And regardless, it's not a bugfix in the standard sense; it's changing the way ZC has been coded to work. That's a pretty big new feature to add. And we're on a release candidate. As in as soon as we squash the remaining critical bugs, we're releasing it. As in no new features added.

[Eurysilas]

Russ gets it.

Blackbishop, do you not realize how completely f***ing evil and unholy the state of the Zelda Classic codebase is? Literally, fixing your one piddling matter could cause the thing to have a months-long seizure of bugginess. The code base is so bad that 3.0 would almost certainly need to be a rewrite (I have my own opinion on the likelihood of that happening in my lifetime, but I digress).

Also, not sure if you're aware, but even the bugs from the original Zelda 1 are to be preserved by default policy. Why do you think all fixes relating to such things are optional?

Correct me if I'm wrong, devs.

[Mero]

And enemies where hard coded to flash when hit and they added a quest rule to make them flicker to complement 8 bit mode. And did you not see that I asked a quest rule to be used rather then a forced change. But we're going a bit off topic so let's stop shall we.

[LinktheMaster]

And enemies where hard coded to flash when hit and they added a quest rule to make them flicker to complement 8 bit mode. And did you not see that I asked a quest rule to be used rather then a forced change. But we're going a bit off topic so let's stop shall we.

Sorry, but do you know how ZC's code operates? Do you know what features are easy to implement and what others aren't? Since I know the answer is "no", I'll go ahead and move on with my point.

ZC's code is a mess. Tons of things are hacked in, barely working, and horribly inefficient. I've heard that from several ZC developers. It's what happens when 10+ various developers have been working on a program for 10+ years. Because of that, the code of ZC is very... iffy, I guess is a good way of putting it. Feature A may sound more complex than feature B, but because of their implementations, feature B very well may be more difficult to add, if not impossible. You really don't know how everything is implemented. For example, something I could see is that item spawning after enemy deaths, door openings after enemy deaths, secrets activations after enemy deaths, etc. might honestly be all coded entirely separately. So implementing the feature you request could actually involve updating tons of different parts of ZC rather than just one small section of code. With all those different parts, it could easy to slip up and mess something up that would add new bugs.

Again, you have no idea how ZC is coded. I don't either. I could be completely wrong, and there may be even more details that could complicate things that I'm not even thinking of. But I still don't know. But if Gleeok or Saffith tell me that something is too complicated to put into ZC right now I believe them. They know a hell of a lot more about it than you and I, and I'm surely not going to badger them for two other posts afterwards trying to weasel my way into getting a feature I want implemented added to ZC, especially not one that's can be worked around with scripting.

Sorry if this seems rude, but it's behavior like this that make coders (including myself) absolutely frustrated at people, sometimes dropping projects.

[ShadowTiger]

BUG: So has anyone ever tried to save and import a subscreen (.zss) file? ZQuest doesn't seem to recognize it as a compatible valid filetype, despite it being in the same folder as ZQuest's executable. (Everything is all in the same folder.)

BUG: Also, if you delete a subscreen from the custom subscreens list (Quest -> Misc Data -> Subscreens) and delete a subscreen if you have two subscreens, therefore only having one active and one passive subscreen, making every other Dmap that uses that second active subscreen now move to that first subscreen, when you're on that Dmap that uses the deleted subscreen, despite it reading that it uses the remaining valid subscreen, when you hit enter/start to pull down the subscreen, it's just all black and invalid before it even starts to scroll. Not good. Also the passive subscreen appears / finishes on top, rather than on bottom.

[Moosh]

Ok, so I've noticed that if you step of a combo that's been changed to a direct warp with a script (may have to be on the frame after it's changed, IDK) it warps you to the screen you're currently on. Might wanna get that checked out...

And, yes, I did set it to warp to another screen. I even tested and changed the tile below Link and it worked just fine.

Edited by Moosh, 05 May 2012 - 11:57 PM.

[Saffith]

Any word on whether zq_win_proc_fix=0 fixes crashes?

By the way, I noticed the map function not working (hitting space to show everywhere you've been). Is that an issue with game version or is that something that can be fixed?

I'm not entirely sure....Saffith?

Are you certain it was enabled in the first place? I tried in the Lost Isle build, and it didn't work there, either.

I'm curious: is there a reason that the OS X build eschews being able to right-click at all? Apple hasn't shipped any single-button mice for ten years now.

Allegro's doing, presumably. I don't see anything in ZC's code to explain it.

[MoscowModder]

I once had a crash in RC3 that went away after I added either the zq or zc version of that fix - one of them was already set.