SplitPixl

I'm thinking about the implementation of the `energyChange` event, it makes sense to leave `energyChange` implied in the cases of `noteCut`, `noteMissed`, and `bombCut`. But for the `obstacleEnter` event I...

Also, maybe keep the current behavior of energy when `noFail` is enabled, and fix my documentation to reflect it's behavior? Both of these really come down to personal preference on...

Looking at [CheckHeadInObstacle](https://github.com/opl-/beatsaber-http-status/blob/3ee2d095fb2e9d6ed0fd12b2358045a45cb0482e/BeatSaberHTTPStatus/Plugin.cs#L410), maybe there could be like a `obstacleEnergyChange` event? It might need to be ratelimited to not spam the client.

When I can test the new code on master, I'll merge it in to here and see if I can make a ratelimited `obstacleEnergyChange` event.

I'm thinking that the `obstacleEnergyChange` event would probably be better as it's own PR.

Hey, is there anything else that needs to happen before this PR can be merged?

Hey, is there anything else that needs to happen before this PR can be merged?

Is there anything else that needs to happen before this PR can be merged?

Is there anything else that needs to happen before this PR can be merged?

Is there anything else that needs to happen before this PR can be merged?