You know, before I responded to you, I re-read all those topics. Every bleeping post. I also spent several hours identifying things in the source, to allow adding a patch for this, to the agenda. Then you came back, libelled me in your posts, ranted some more, and pretty much disgusted me.
You know what I did? I decided that it wasn't worth my time to care. There's a lot of stuff that i want to do with improving ZC, and a lot of requests to process. I'm not going to waste my time on something requested by a user who goes out of his way to insult me, drag me in the dirt, and who seemingly can't grasp the simple concept of being polite.
So, you pretty much talked yourself out of me bothering to add this fix.
You want to know why no-one else is responding to you? It's because you are treating the people who might give your request any of their time like trash, including me. It's entirely possible that Saffith did change it, and started to add a rule, and then you irritated him so much, that he also said 'the 'ell with it'.
Read me, and understand: I'm done with this.
No-one else has requested this to be changed, at all. If you want to add more artificial difficulty, add a few lines of zscript to your global active script to make your shooters fire even if Link isn't next to them; or make randomly firing eweapons spawn. What you want is so easily patched, and there are so many other issues on the stack, that it's a stupidly low priority. Screaming at us isn't going to get us to sympathise with you.
If you don't like 2.50.2, here's another thing you can do: Go add ZVersion.zh to your quests, and cause them to refuse to run on 2.50.2, as, you know, you can always scream at the players and force them to use 2.50.0/1, which if your game design relies on bugs, and artificial difficulty based on those bugs, might be your best option. It simply isn't feasible to allow for every possible weird bug as a quest rule. Right now we have dozens of people who complained about the bitmap positioning issue, including me, and that doesn't have a QR either, yet. If we have yet to address that complaint, why in the flidd would we be addressing this one?
I fixed the bitmap problem externally, with a header. Most users were satisfied with that as a solution, as making a QR just to fix bitmap positions was deemed unimportant, and wasteful of our remaining bits.
We're trying to do things, that would not require more QRs, and to be fair, I'm planning to make it possible (at least for some rules) that QRs can be set/changed/read by script, and entirely change how they're stored so that we don't run out of space, and so that we can handle issues like this one, but like I said, your attitude is completely out of line.
I'm not going to waste more time on this if you simply keep ranting about it. There's a flipping feature request board for this over on AGN, both in general, and for 2.x future releases. Filing it there (politely) would have meant that someone would probably get it into the next version, but this...this is just insanity. When you decide to stop tearing everyone up over your (singular) grievance, come on back and file a polite feature request.
This is the last you'll hear on the topic, pretty much from everyone, until then.
