The menu dynamically reorders options based on player behavior. If a user consistently selects diplomatic responses, the EZ2C system surfaces similar choices more prominently—not by hiding others, but by placing the most probable choices closer to the default selection or cursor home position.
To understand why the EZ2C Dialogue Menu outperforms legacy systems, you must break it down into five core components:
In open-world RPGs, players expect deep conversations. Using an EZ2C Dialogue Menu, a developer can create a barkeep NPC with the following logic: EZ2C Dialogue Menu
Because the menu is EZ2C, the game designer—not the programmer—can tweak the gold cost or add new rumor dialogue without rebuilding the project.
Supported action types:
| Action | Effect |
|--------|--------|
| giveItem("potion") | Add to inventory |
| addGold(50) | Modify currency |
| setFlag("talkedToKing", true) | Change game state |
| playSound("click") | Audio feedback |
| startQuest("find_wizard") | Quest system trigger |
Example node with action:
"line": "Take this map.",
"actions": ["giveItem(map)", "setFlag(hasMap, true)"],
"choices": ["text": "Thanks", "nextNode": null]
The magical number for working memory. More than five choices, and the user experiences choice paralysis. Use sub-menus for deeper branches.