immersive-dialogue: a0fe42fe540b4fbc2ece8dbd53c345640237f97c..5d7c70897e5b97d0ca0e5c0f505c031f4b4619be

Internal use only: Reviewer details Maintainer details

I have a feeling Runelit hub checks failed due to the user of menuActions, if so here's a bit more information on how and why I use client.menuAction(..):

A left‑click on that panel is forwarded to the game's own continue / option‑select action via client.menuAction(..., MenuAction.WIDGET_CONTINUE, ...), targeting the native dialogue widgets (ChatLeft/ChatRight.CONTINUE, Chatmenu.OPTIONS) by their component IDs.

This affects only non‑combat conversation UI; it grants no information, efficiency, or capability the player doesn't already have, only the convenience of clicking where the dialogue is shown.

The client.menuAction(..) call results in the same server interaction the native click it mirrors would normally cause so no extra or different packets are sent to the server, and nothing is sent unless the user clicks.

See DialogueWidgetController.java#L441 for "continue to click" usage.

See DialogueMouseListener.java#L166 for "select options" usage.

Feature in action:

yeah, use of client.menuAction is not allowed for this

i understand this usage may seem benign but it's a question of accidentally tripping jagex's macro detection, which programmatic server interactions outside of the vanilla jagex client code paths will do. we cannot host features that might get users banned

yeah, use of client.menuAction is not allowed for this

i understand this usage may seem benign but it's a question of accidentally tripping jagex's macro detection, which programmatic server interactions outside of the vanilla jagex client code paths will do. we cannot host features that might get users banned

Allright, totally understand! Was worth a try.

• Removed: menuActions that supported click actions all together
• Rewrote README
• Added support for System message dialogues in the custom dialogue box