Sword Triggers Are Not Continuous

[CSD]

It doesn't. That room in question does have sword triggers in a tiered secret but I was randomly supposed to guess to use arrows on it; I thought it might have been a broken continuous sword trigger.

This glitch is a weird inconsistency, especially when the Strike trigger is involved. And also it is very strange that the sword trigger will not activate screen secrets when used in a situation that would normally be continuous. I would call both of these things a bug, regardless of whether it ends up being a version inconsistency, but if it's consistent then I guess there's not much point in mucking around with it.

By coincidence, it was Peteo that reported the bug where slash combos were no longer continuous, in 2008. Nobody seems to know what the behaviour was prior to that inconsistency being introduced, but I guess there are a lot of ways we could have ended up here. Perhaps the same bug was introduced with sword triggers and it was not noticed and corrected. Perhaps the change to fix the slash combos introduced a new bug. Perhaps there always used to be a difference in the way that sword triggers and slash combos worked and an old change unified the code between the two and introduced the version inconsistency, but if that's the case, why do sword triggers work different from other triggers? Just throwing out some random speculation... Nobody seems to know.

[ZoriaRPG]

It doesn't. That room in question does have sword triggers in a tiered secret but I was randomly supposed to guess to use arrows on it; I thought it might have been a broken continuous sword trigger.

This glitch is a weird inconsistency, especially when the Strike trigger is involved. And also it is very strange that the sword trigger will not activate screen secrets when used in a situation that would normally be continuous. I would call both of these things a bug, regardless of whether it ends up being a version inconsistency, but if it's consistent then I guess there's not much point in mucking around with it.

By coincidence, it was Peteo that reported the bug where slash combos were no longer continuous, in 2008. Nobody seems to know what the behaviour was prior to that inconsistency being introduced, but I guess there are a lot of ways we could have ended up here. Perhaps the same bug was introduced with sword triggers and it was not noticed and corrected. Perhaps the change to fix the slash combos introduced a new bug. Perhaps there always used to be a difference in the way that sword triggers and slash combos worked and an old change unified the code between the two and introduced the version inconsistency, but if that's the case, why do sword triggers work different from other triggers? Just throwing out some random speculation... Nobody seems to know.

@_L_ and @jman2050 might remember what was going on at that time. 2008 is that grey period in which I lost hope of 2.5 ever being finished, and went poof for a few years.

I do not have snapshots of the source throughout the 2.5 beta cycle, so I have no way to go back and look at how it used to work.