disable-physics doesn't work for all events

[Sproki]

Hey!
I am actively using the BuilderUtilities plugin in version 1.17. I noticed that the gravity of the blocks "Anvil, Water" and probably others is sometimes not 100% off.
For example:
You place an Anvil that floats and next to it another one then both Anvils fall down.

[TehBrian]

Hmm, odd! I'll look into this when I next get the chance :)

[TehBrian]

After testing this out, it seems that this issue is simply a limitation of Bukkit. Even when cancelling all BlockPhysicsEvents — which is the only physics-related event that we have access to via the API — some physics-related behavior still occurs, just like what you were saying. In the documentation for BlockPhysicsEvent:

Plugins should also note that where possible this event may only called for the "root" block of physics updates in order to limit event spam.

It doesn't seem like there's anything that I can do about this, sorry :( For now, I'll remove disable-physics and add smaller options that do work, like disabling redstone.

I'll leave this issue open, though, because someone else might have a good idea on how to fix this.

[TehBrian]

After tinkering around with this issue some more, I've discovered that trying to disable physics of any kind is inherently buggy. Because of the limitation I mentioned in the previous comment, Bukkit doesn't give plugin developers full control over physics, including trying to disable redstone.

I took a look at the original plugin and tested its physics-disabling features, and they have the same issues discussed here. Although that plugin has additional config values such as disable-redstone and disable-gravity, these function just as poorly because, at their core, all that these features are doing is cancelling BlockPhysicsEvent.

Honestly, I would just recommend not using this feature for the time being.

[TehBrian]

heya, i can't remember, did we ever end up figuring out how to solve this better than the current functionality?