[kazotaruumc72]

Summary

Adds PlayerDialogClickEvent (fr.maxlego08.menu.api.event.events), called when a player clicks a custom-click button of a dialog, before the actions of the button run.

• getPlayer()
• getDialogName(): file name of the dialog without .yml (same value as DialogInventory#getFileName)
• getButtonName(): last segment of the button's configuration path: button1 for multi-actions.button1, yes / no for a confirmation dialog, notice, exit-button, ...
• Cancellable: cancelling it prevents the actions of the button from running.

Use case: plugins reacting to dialog buttons without adding actions to every dialog file, e.g. a DIALOG_CLICK quest type in zQuests (Maxlego08/zQuests PR to follow).

Implementation

• ZCustomClickDialogActionLoader passes the dialog name (from the file) and the button key (from the path) to ZCustomClickDialogAction.
• ZCustomClickDialogAction calls the event at the start of its click callback. The previous constructor is kept and does not call the event.
• Changelog entry added under New Features.

Note: canvas click values also go through ZCustomClickDialogActionLoader; for them the button name is the last segment of the click path.

Test plan

• ./gradlew :API:compileJava :Hooks:Paper:compileJava passes
• In-game check on a multi_action and a confirmation dialog

🤖 Generated with Claude Code