You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have the ability to set an entity visually on fire without it being actually burning
but the way visual fire works, it is not possible to disable visual fire if the entity is really burning
Describe the solution you'd like.
Internally, the visualFire field could use a nullable Boolean object and default to null and make the entity burn if true
not burn if false
and send the actual fire state when null
I understand this will cause problems with existing plugins that utilize this method, other suggestions are more than welcome
Describe alternatives you've considered.
Other
Also, I would like to suggest adding a lockFireTicks method to be able to make entities burn or not start burning as long as the ticks are locked
The text was updated successfully, but these errors were encountered:
I also just noticed that the getMaxFireTicks is absolutely misleading
it returns the immunity ticks (1 for non player entities and 20 for players)
this should probably not only be clarified in the JD but maybe even a rename would be appropriate
Is your feature request related to a problem?
Currently, we have the ability to set an entity visually on fire without it being actually burning
but the way visual fire works, it is not possible to disable visual fire if the entity is really burning
Describe the solution you'd like.
Internally, the visualFire field could use a nullable Boolean object and default to null and make the entity burn if true
not burn if false
and send the actual fire state when null
I understand this will cause problems with existing plugins that utilize this method, other suggestions are more than welcome
Describe alternatives you've considered.
Other
Also, I would like to suggest adding a
lockFireTicks
method to be able to make entities burn or not start burning as long as the ticks are lockedThe text was updated successfully, but these errors were encountered: