Hm well it's very unlikely it's a new bug. Also you can do that? That would be great.
All things are possible. This one, at least, is easy. I did precisely the same thing for SetComboSolid: Old quests use a specific COMBOSDM based on the QHeader, or based on a rules bit for Build 31+.
I'll note here, that while we are running out of QR bits, which is why Saffith and Gleeok did not want to use them for these things, this will not matter in 2,54 and later, as those have a new save format; plus, I am rewriting rules in general. A lot of things will be in the editors (enemies, items, and such), or available on DMaps or Screens. Some rules will become toggles that can be set at any time by script, and some things are undecided.
The present QR bits will be locked as of 2.53 Final, whenever that is out, and ZQuest thereafter will read these as old_quest_rules. THe new system, that I plan to have in class FFScript::FFRules will be a centralised location for rules that are forwarded from old_quest_rules, that are not part of the editors, so using up the last few bits in 2.53 no longer has the weight that it would carry, if we were doing 2.50.3, 2.50.4, 2.50.5, and such.
The decision to kill the 2.50.x line with this build allows us to be able to fix things without as much bother, in future builds; and my personal policy that each new release should not produce quests that play in older versions of ZC, as 2.50.2 and 2.50.1 did, will ensure that we do not run into these issues, ever again.
It will also give users a valid reason to update. Allowing 2.50.1 and 2.50.2 quests to run in 2.50.0, for example, did not encourage upgrading, which meant that (1) quests had bugs in older players, and people were scrambling to use one version over another; (2) fixes that would have worked for some issues, could not be implemented, because they would break quests when you play them in the older players, and (3) not even the slightest new feature could be added for the item editor, enemy editor, combo editor, sprite editor, map editor, screen editor, or ZScript.
If I am going to work to support ZC for the long-term, I do not want to create an intentional developmental cul-de-sac, which is why that policy has to end. Do not expect to see 2.53.1, 2.53.2 and so forth. I want this to be the pinnacle of the 2.50.x line, so I do want to resolve as many of these issues as possible.
One main concern, is of course, Allegro, and I may need to recompile that on my own toolchain; and then, compile it for Linux and OSX... This is neither fun, nor easy, and it is why I wish that we had more staff, but hey-nonny-nonny; what can I do about that?
It would've been nice if there was some mention of this on Shardstorm >.> I've been sourcing news on updates to this software from that seemingly dead site. This topic makes me feel like I've been missing out on status updates (seeing as there's been seemingly multiple beta's since 2.50.2).
I do not have write access on Shardstorm, and that is not technically where this stuff is going now. The live changelog will be on ZeldaClassic.com, and I might pester War Lord to update it, once this is out in Gamma form.