Prefix invocation is not skipped by returning false about harmonyx HOT 2 CLOSED

Greetings!

As Marco already pointed out, this behaviour is intended to be fully symmetrical with how postfixes operate.

We've had a plan on exposing the __skipOriginal boolean to prefixes and postfixes instead so that prefixes themselves can decide whether skip their execution or not.

Seeing as this is closely related to that feature, I'll reopen this issue and close it again once bool __skipOriginal parameter support is in.

Related, I've made #8 which I plan on addressing this week so that all possible differences from original Harmony is known.

from harmonyx.

This is the expected behavior in new versions. Prefix patches preventing other prefix patchers from running have been found to be very error prone and nondeterministic in more complex setups. This combination caused seemingly random crashes in plugins that did not expect their prefix patches to not run and was very difficult to diagnose and fix (different users could have the patches ordered differently because of different plugin load orders, so for some users it worked fine while it broke for others). It is also not reasonable to expect a plugin authors to know all other plugins that patch a particular method, therefore the decision was to make this change.

If you need to prevent a certain plugin's prefix patch from running the recommended way is to patch the patch itself.

from harmonyx.