Events

Cooking exposes 4 synchronous Bukkit events. The owner check and coverage of each fire point cannot stand in for another

Event	Timing	Thread	Cancellable	Mutable field	Cancellation/effect
CookingStationInteractEvent	Recognized and enabled interaction on any of the seven station types, before the matching handleInteraction	Player/location owner thread	No	None	Informational; it does not block station logic, and the tracker records the recent station from it
CookingRecipeCompleteEvent	In the shared reward exit, before outputs and completion actions are delivered	Global-region owner thread; when ownership cannot be taken the event is skipped and the configured reward flow continues	Yes	dropResult	Cancelling suppresses outputs and completion actions
PlayerNutritionConsumeEvent	After a supported vanilla/MMOItems/NeigeItems food source is resolved, before nutrition and source actions apply	Player owner thread	Yes	None	Blocks EmakiCooking nutrition/actions without undoing the underlying consumption
NutritionThresholdChangeEvent	After a single/combo threshold edge changes its met state	Player owner thread	No	None	Post notification; it cannot roll back state or actions

CookingRecipeCompleteEvent.getPlayer() can be null for automatic station completions. dropResult only changes how outputs are delivered. Both notification/post events are non-cancellable, and non-owner paths do not publish events off-thread just for auditing