As per the conversation in DMs, AnimateTickEvent, EntityWalkEvent and AnimateFluidTickEvent allow you to make changes to the behavior defined in the respective methods in Block and Fluid. Cancelling these prevents the original method from being called, so you could, for example, replace the particle the enchantment tables give off.
The dispenser helper methods in BlockUtil are just there because I found out that it was really tedious to write statements to find the block or entities in front of the dispenser in the predicate lambda for registerAlternativeDispenseBehavior. It may be the wrong class to put it in and the javadocs definitely need reviewing, I wasn't sure how to space out @param and @return properly.
As per the conversation in DMs,
AnimateTickEvent
,EntityWalkEvent
andAnimateFluidTickEvent
allow you to make changes to the behavior defined in the respective methods inBlock
andFluid
. Cancelling these prevents the original method from being called, so you could, for example, replace the particle the enchantment tables give off.The dispenser helper methods in
BlockUtil
are just there because I found out that it was really tedious to write statements to find the block or entities in front of the dispenser in the predicate lambda forregisterAlternativeDispenseBehavior
. It may be the wrong class to put it in and the javadocs definitely need reviewing, I wasn't sure how to space out @param and @return properly.