Events which are triggered by things that don't relate to an actual brick are always hacky and tend to be fail-binned by Badspot.
Maybe, just maybe, there's a reason for this. Such an event has only two options to work at all.
- It can run through every brick on the server, every time it's ever called.
- It can keep a cache of bricks, which is prone to breaking and which no one else can share because their input will be on different bricks.
Running through every brick on the server every time anyone jumps is an idea so horrible that thinking about making such an add-on is actually giving me a migraine.
Caching all bricks that have the event isn't much better, because if I make a system I don't want it to be exclusive to my own mod.
Regardless, a brick fifty miles away shouldn't have onPlayerJump trigger because I needed to hop over a wall, and I sure as hell don't want to be hit by a kill event
every time I jump.
Having the event trigger on every brick that has it, everywhere on the server, is stupid.