Modding guide

How to add a multi-use (radial) menu entry

10 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

The multi-use wheel is the radial menu a player opens by holding E on something: Open Inventory, Demolish, Set Pin Code. This page adds your own entry to a structure, a creature or an item's container. Then it makes the entry do something on the server. The first entry takes me about half an hour. Most of the time goes into testing it as a client.

  • You'll make: a wheel entry for the right players that runs on the server
  • Time: about half an hour for the first entry
  • Level: beginner to intermediate
  • You'll need: a child of the structure or creature, or a buff for vanilla actors

How an entry works

Three events on the actor do all the work. They come from the base class every structure, creature and buff shares.

  • BP Get Multi Use Entries builds the list. It runs on the client, many times a second while the player looks.
  • BP Try Multi Use does the work. It runs on the server, once, when the player picks an entry.
  • BP Client Do Multi Use handles visuals and screens. It runs on the picking player's client after Try returns true, or straight away for client-only entries.

The server builds the list too, and it has to match. When the player picks an entry, the server runs Get Multi Use Entries itself, once, to check that the entry really exists. Try Multi Use fires only if the server's list has it. So the client and the server must build the same list from conditions both can see. Hide an entry behind something only the client knows, like a widget, a local setting or a variable that doesn't replicate, and the client shows it while the server never finds it. Nothing errors; Try just never runs. Entries marked Client Side Only are the exception, because they skip the server.

Each entry is a small struct made with Make Multi Use Entry. Three fields matter most: the text, a use index that identifies it, and a priority that sets its place on the wheel.

The process

  1. Pick the actor that owns the entry. Your own structure or creature gets it directly. For vanilla actors and for items, a buff carries it.

    Show me how
    You want it on Put the events on
    your structure a child of the closest vanilla structure (How to make a custom structure)
    your creature a child of the vanilla creature (How to make a custom creature)
    every vanilla creature, or only tames a buff on the creature, added as a default buff (How to make a buff)
    the player's own wheel a buff on the player (How to make UI, step 4)
    an item the container's inventory buttons (step 7), or a buff on the player that checks what they hold

    Seed items also have Get Planted As Crop Multiuse Entries and Planted As Crop Try Multi Use, for entries on the crop plot they're planted in.

  2. Turn on the switches. Two switches on the actor gate the events. Without them, your graph never runs.

    Show me how
    Switch Default Needed for
    Enable Multi Use on for structures and creatures, off for buffs any wheel at all
    Blueprint Multi Use Entries off your Get Multi Use Entries override
    Buff Handle Instigator Multi Use Entries off a buff adding entries to the creature it's on
    Allow Multi Use Entries From Self off a buff adding entries to its own player's wheel
    Use Consolidated Multi Use Wheel off a buff's entries in their own sub-wheel, with the buff's icon

    Vanilla agrees: of 336 official classes that override these events, 273 tick Blueprint Multi Use Entries on themselves. The Campfire, Cooking Pot and Rex all do.

  3. Add your entry in Get Multi Use Entries. Call the parent first, add your entry to the array, and return it.

    Show me how
    • Override BP Get Multi Use Entries. Right-click the function entry → Add Call to Parent Function. That keeps vanilla's entries, like Open Inventory.
    • Add a Make Multi Use Entry to the array the parent returns. Plug that same array into the Return Node. Returning a different variable, or nothing, shows nothing.
    • Use String: the text on the wheel.
    • Use Index: pick a large, odd number, like 482917. Vanilla uses small ones: the Rex keeps its roar on 2000, and in my video I found 70 for picking up small creatures and 600 for doors. Round numbers like 10,000 clash with other mods.
    • Priority: higher or lower than its neighbors moves it around the wheel. My video gives its back button −10,000 so it sits near the top left.
    • Icon: a texture for the wheel slot.
    • Keep this function light. It runs every frame the player looks at the actor.
  4. Show it only to the right players. Build the conditions into Get Multi Use Entries. Its For PC input is the player who's looking. Use only conditions the server can check as well, or the server's copy of the list won't have your entry (How an entry works).

    Show me how

    Cast For PC to Shooter Player Controller, then branch before the Add:

    Show it to Check
    anyone who could open it Allow Structure Access on the structure. It covers team, lock and pin.
    the tribe only the controller's Targeting Team equals the actor's
    a tribe rank Allow Tribe Group Permission on the controller, for example STRUCTUREACTIVATE, with the actor as On Object
    tribe admins Is Tribe Admin on the controller
    the buff's owner only the buff's owner controller equals For PC
    • Base conditions on replicated values. The client builds this list from its own copy of the actor.
    • Modders report the server also builds the list when an entry is picked. If the server's list lacks your entry, Try never runs. I haven't confirmed this in the code.
    • The client can be modified, so hiding an entry isn't security. Check again in step 5.
  5. Do the work in Try Multi Use, on the server. Match the use index, check again, act, and return.

    Show me how
    • Override BP Try Multi Use. Switch on Int on Use Index, with a pin for your index.
    • On your pin: repeat the step 4 checks, then do the work. Give items, change replicated variables, spawn actors.
    • For server-admin entries, check Is Player Allowed To Cheat here. It lives on the game mode, which only the server has.
    • Return true to also run Client Do Multi Use on the player's machine. Return false when only the server should act.
    • On Default, call the parent and return its value. Otherwise vanilla entries stop working.
    • Never call a Run on Server event from here. You're already on the server. A Run on Server event on a structure or wild creature from the client never arrives, because the client doesn't own it (Works in PIE, not on a server).
  6. Put client-only work in Client Do Multi Use. Sounds, animations and screens go here. Tick Client Side Only on entries that need nothing from the server.

    Show me how
    • Override BP Client Do Multi Use. Switch on Client Use Index the same way.
    • Client Side Only skips Try entirely. Use it for an entry that opens UI or changes the wheel.
    • Never create a widget in Try: the server has no screen. How to make UI covers opening a menu from here, passing the structure in, and sending the player's choice back to the server.
    • Close any open inventory first, so two screens don't fight for focus. My video does this before its widget.
  7. Add the extras you need. The same struct does hold-to-use, secondary keys, inventory buttons and sub-wheels.

    Show me how
    • Hold to use: set Entry Activation Timer and Default Entry Activation Timer to the seconds to hold.
    • Secondary key (F on keyboard): tick Is Secondary Use. Add Hide From UI to keep it off the wheel.
    • Inventory buttons: tick Hide From UI, then Display On Inventory UI, …UI Secondary or …UI Tertiary for buttons 1 to 3. Buttons 4 to 6 use Additional Buttons Index 0, 1 and 2. Six is the limit. This is how an item gets actions: the container shows buttons for what's selected.
    • Sub-wheels: give child entries a Wheel Category, such as 20. The opening entry is Client Side Only with Persist Wheel On Activation. In Client Do, call Set Multi Use Wheel Category on the controller with
      1. Add a back entry that sets 0.
    • While riding: BP Get Riding Multi Use Entries, with its switch Use BP Get Riding Multi Use Entries.
    • Removing vanilla entries: BP Filter Multi Use Entries, with Use BP Filter Multi Use Entries. The Fishtank does this.
  8. Test it as a client, then on a server. A listen host runs everything, so a solo test hides most mistakes.

    Show me how

    In PIE, set the net mode to Play As Client with two players. Check the entry shows for the right player only, and that its effect reaches the other one. Then repeat on a local dedicated server (Testing your mod). If a change doesn't show in PIE, restart it: PIE caches the Mod Data Asset.

How the pieces connect

This Calls or reads That
Get Multi Use Entries For PC, replicated state the list the player sees
The player's pick the use index Try Multi Use on the server
Try Multi Use returns true Client Do Multi Use on that player's machine
Client Do Multi Use Create Widget your screen (How to make UI)

The use index is the thread through all four.

The settings that matter

What you want Field on the entry
The text and its place Use String, Priority, Icon
Its identity Use Index
No server round trip Client Side Only
A button instead of a wheel slot Hide From UI plus Display On Inventory UI
Grouping Wheel Category, Persist Wheel On Activation

The struct has about 35 fields. The rest are niche: colors, sounds, custom drawing.

Common mistakes

My entry doesn't show

Blueprint Multi Use Entries is off, or Enable Multi Use on a buff. Or the array you added to isn't the one you return. Check Hide From UI and Wheel Category too, then restart PIE in case the Mod Data Asset was cached.

Vanilla's entries disappeared

You skipped the parent call in Get Multi Use Entries, or on Try's Default pin (steps 3 and 5).

It shows for everyone

There's no condition on For PC. Add one (step 4), and check it again in Try.

It fires on the client only; Try Multi Use never runs

Client Side Only is ticked, which skips the server. Otherwise the server's list and the client's don't match. The server rebuilds the list before Try runs, and your entry isn't in its copy because a condition uses data the server sees differently: a client-only variable, a widget, a value that doesn't replicate. Print the list's length on both machines (step 4, How an entry works).

Client Do Multi Use never fires

Try returned false. Return true on your index, or tick Client Side Only if it needs nothing from the server.

It works in single player but not on a server

Single player is server and client at once, so everything runs. You likely did server work in Client Do. Or you called a Run on Server event the client doesn't own (Works in PIE, not on a server).

Disable Use doesn't gray my entry out

Modders report that since mid-2026 a disabled entry looks clickable. It just does nothing. Hide it instead, or change its text.

Another mod's entry replaced mine

You share a use index. Pick a less obvious number, or tick Use Consolidated Multi Use Wheel on a buff.

Check it worked

  1. The entry appears only for the players your conditions allow.
  2. Picking it as a client changes something on the server that the second player sees.
  3. Vanilla entries still work.
  4. Screens open only for the player who picked.
  5. All of this holds on a local dedicated server.

Watch

Go deeper

Sources

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

the DevKit's own classes, the community Discord and my multi-use video (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab