Turn any Widget Blueprint into an interface players use in the world. They aim at a button, your widget lights it up, and they click it by firing, with E, or with the native interact button on mobile and controller. There is no UI mode and no cursor, so gameplay never stops. The kit handles the interaction; your widget keeps its own look and shows hover, clicks and states itself.

Features

• Works with your own widgets: drag any Widget Blueprint into the level, add one component, and its buttons become clickable. You don't need to rebuild it or change its design.
• Six element types: buttons, on/off toggles, choices (radio groups), tabs that switch screens, sliders (hold fire to drag, click to jump), and steppers (− / +).
• Your widget, your look: the kit draws nothing over your widget. For each state (hover, click, on or selected, slider value, disabled) it writes a Verse field of your WBP, and your WBP shows it: a widget to show, or an animation. Sliders also get their fill length, ready for a SizeBox. The editor names every field and animation and tells you which bindings and View Binding conditions to add.
• Shared or per-player states: a door panel everyone shares, or a settings menu where each player has their own toggles, choices, sliders and screen. Per-player copies of the widget are handled for you, so each player sees their own states.
• Every input: fire, the E key and the native interact prompt on mobile and controller, with a screen-centre dot that grows over clickable elements.
• Actions in Verse, ready to fill: the editor also writes your logic file, with one branch per element. Replace each Print with your code. There are no device lists to wire.
• A clean Verse API: ClickedEvent, ChangedEvent, HoveredEvent, SubscribeClicked, SetOn, SetValue, SetScreen, SetEnabled, SetPrompt, IsOn, GetValue, with per-player variants.
• No-code option: if you don't write Verse, an element can trigger devices instead (OnClick, WhenOn, WhenOff), and clicks can play an audio player for the player who clicked.
• 4 ready-made examples: a settings panel, a shop with tabs and per-player gold, a code keypad that opens a door, and a radio with a vertical volume slider. Place them as they are, or copy them to start your own.
• Free online editor: paste your widget (Ctrl+C in the WBP Hierarchy): it finds its buttons and its size. Adjust the boxes, test the interactions while watching the fields your WBP will receive, then download the two Verse files.
• Debug tools: in-game hitboxes and click coordinates, to check every rectangle.

Setup

1. Close UEFN, copy the WorldUIKit folder into your project's Content folder, open the project and build Verse code.
2. Drag your Widget Blueprint into the level. Set its scale (10 is a good start) and turn it to face the players.
3. Select it and add the interactive_widget_component component in the Details panel.
4. Describe its clickable elements, in one of two ways:
   • Editor: open https://store.simnjs.fr/tools/world-ui. In your WBP, select the root in the Hierarchy, press Ctrl+C and paste it there. Check the boxes it finds, then download both files: <your_wbp>_layout.verse and <your_wbp>_logic.verse. Save them in your project's Content folder, next to WorldUIKit (not inside it, so updates never overwrite them). Build Verse, then add the <your_wbp>_layout and <your_wbp>_logic components next to interactive_widget_component.
   • Details panel: fill the Elements list of interactive_widget_component (name, type, rectangle in widget units). The elements are clickable, but the widget shows no state.
5. In your WBP, create the Verse fields the editor lists (BuyHover, MusicOn, VolumeFill…) and bind them: the Render Opacity of a highlight, a View Binding condition for an animation, the Width Override of a SizeBox for a slider fill.
6. Write the actions in <your_wbp>_logic.verse: replace each Print with your code. When you change the zones later, download the layout file again. The logic file is yours: the editor never rewrites it.
7. Launch a session, aim, click.

Without code: in the editor, tick Devices (no code) on an element (or use the Elements list). It gets lists of trigger devices to wire in the Details panel: OnClick for every element, plus WhenOn and WhenOff for toggles, choices and tabs.

To try it first, drag one of the examples of WorldUIKit/Widgets into the level and add interactive_widget_component and its two components:

Each example shows its own hover, clicks and states from its fields: open its WBP to see how they are bound.

Elements

Every click also sends ClickedEvent. Rectangles are in widget units, from the top-left corner of the widget, exactly as in the WBP Designer.

WBP fields

All are floats, except Text (message) and Screen (int). Verse cannot start a WBP animation: a View Binding condition on the float field does it (== 1 plays it, == 0 plays it in reverse).

Verse

The generated <your_wbp>_logic.verse is a starting point like this one:

1using { /Verse.org/SceneGraph }2using { WorldUIKit }3 4shop_logic := class<final_super>(component):5    var Subscriptions:[]interactive_subscription = array{}6 7    OnBeginSimulation<override>():void =8        if (Kit := Entity.GetComponent[interactive_widget_component]):9            set Subscriptions = array{Kit.SubscribeClicked(OnClicked), Kit.SubscribeChanged(OnChanged)}10 11    OnEndSimulation<override>():void =12        for (Subscription : Subscriptions):13            Subscription.Cancel()14 15    OnClicked(Event:interactive_event):void =16        case (Event.Element):17            "Buy" =>18                Volume := Event.Widget.GetValue("Volume", ?Player := option{Event.Player})19                Print("Buy clicked, volume {Volume}")20            _ => {}21 22    OnChanged(Event:interactive_event):void =23        case (Event.Element):24            "Music" => if (Event.On?) then Print("Music on") else Print("Music off")25            _ => {}

• States := PerPlayer: each player has their own state. Pass ?Player := option{P} to read or change it.
• SetEnabled, SetPrompt: for everyone. A disabled element can be aimed at but not clicked.

Good to know

• There is no dependency: the helper code is included under WorldUIKit/WorldUIKitLib.
• Several widgets in one island share one aim ray per player.
• In-world widgets are lit in linear space, so a colour or an alpha looks stronger in the Designer than in game. Check them in a session.
• If the boxes are offset in game, turn on ShowHitboxes (Advanced category). CmPerUnit (0.0263) is the size of a widget unit at scale 1.

0.1.0 - 2026-10-16

• First release: any Widget Blueprint used in the world (aim, fire, E or interact button), buttons, toggles, choices, tabs with screens, sliders and steppers, shared or per-player states, WBP fields for your own visuals, 4 ready-made examples, free online editor and AI agent skill