LiquidBounce/net.ccbluex.liquidbounce.utils.kotlin/EventPriorityConvention

EventPriorityConvention

Properties

const val CRITICAL_MODIFICATION: Short = 500

Priority for critical modifications that need to happen early in the event chain, after input preparation but before model state processing

FINAL_DECISION

const val FINAL_DECISION: Short

Used when the event handler should be able to object anything that happened previously

FIRST_PRIORITY

const val FIRST_PRIORITY: Short = 1000

The event should be called first.

MODEL_STATE

const val MODEL_STATE: Short

At the stage of modeling what the player is actually going to do after other events added their suggestions

OBJECTION_AGAINST_EVERYTHING

const val OBJECTION_AGAINST_EVERYTHING: Short

Used when the event handler should be able to object anything that happened previously

READ_FINAL_STATE

const val READ_FINAL_STATE: Short

The event should be called last. It should not only be used for events that want to read the final state of the event

SAFETY_FEATURE

const val SAFETY_FEATURE: Short

Should be the one of the last functionalities that run, because the player safety depends on it. Can be objected though by handlers with OBJECTION_AGAINST_EVERYTHING priority