// Gameplay
Dialogs
Create branching NPC conversations with state-gated answers and server actions.
OxideCarbon
Sign-in required to configure. Install the exported file manually on your server.
Published
// PRODUCT
What the plugin does
- 01Branching questions and answers per dialogue
- 02Gate answers with Player Event States and update progression
- 03Run trusted response actions or open a dialogue through the plugin API
- 04Native candidate 1.1.0: five layouts with per-dialogue selection
- 05Native candidate 1.1.0: paginated answers and dialogs.show for connected players
In beta 1.1.0
- Beta 1.1.0: the same layouts rendered through PimpMyCUI
ON PIMPMYRUST
PimpMyCUI beta 1.1.0 configuration
Import this version’s JSON, edit the settings, and export the finished file.
Keep the exported file: the site does not save your work.
Screenshots
// BEFORE YOU START
Requirements and dependencies.
- Rust server running Oxide or Carbon
- Player Event States is required for dialogue state checks and updates
- An NPC provider emitting OnUseNPC with an NPC UserIDString; HumanNPC is the documented example
- Beta 1.1.0: PimpMyCUI is required by the PimpMyCUI beta archive
// IMPORTANT BOUNDARIES
Before you install
- The Hub configures interface settings, not the dialogue data trees. Back up your dialogue files and test trusted commands before use.
- NPC Overlay is optional and independent; proximity labels do not create dialogue trees or player states.
- The gallery shows offline CUI previews. Test the layout, long replies and integrations in game before using a candidate on your live server.
- Choose a layout in the configurator. Editing and applying a custom Dialogs layout directly through CUI Editor is not available yet.