Use multiple interaction controllers to interact with different things at different ranges.
Want to pick up items all around you but only speak to NPCs or interact with other things when they are right in front of you? This can be done by using a multi interaction controller setup.
In this tutorial we’ll create such a setup:
- 1 interaction controller with a larger range around the player to interact with items
- 1 interaction controller in front of the player to interact with everything
This tutorial is based on the ORK 4 Unity Quickstart 3D tutorials, but can be used in any project. Just keep the size of your player in mind when creating the interaction controller prefab.
You should also have added the Interaction HUD tutorial (using separate HUDs for talk and collect interactions).
Organizer Type #
Organizer types can be assigned to interactable components. Interaction Controllers and Interaction HUDs can be limited to only use defined organizer types. E.g. we’ll add a Collect type and have the larger interaction controller for items only interact with it.
This part of the tutorial is only needed if you haven’t set up the interaction HUD for talking to NPCs and collecting items in the Interaction HUD tutorial.
If you’ve already followed the setup, you’ll already have organizer types for different interactions.
If not, open the ORK editor, navigate to System > Organizer Types and add a new type.
- Name
Set to: Collect Interaction
Save Changes #
And that’s it for the editor setup for now.
Don’t forget to save your changes by clicking on Save Settings at the bottom of the editor.
Prefab Setup #
Create an empty object in your scene. We’ll add our 2 interaction controllers as child objects of this object and make a prefab out of it.
Collect Interactions #
Add an interaction controller as a child object to the empty object using the scene hierarchy context menu (ORK Framework > Interaction Controller (3D)) or the ORK toolbar (search for: Interaction Controller 3D).
Rename the created object to Collect Interactions.
For interacting with items, we’ll use a Sphere Collider to just pick up anything around the player.
Interaction Controller #
We want to limit this interaction controller to only use the Collect Interaction organizer type, i.e. it can only interact with interactions that use the defined organizer type.
- Priority
Set to: 0
The priority of interaction controllers decides the order in which they’ll be checked for available interactions.
They’re sorted by descending priority, i.e. the highest priority value will be used first.
We’ll keep the priority at 0 for the collect interactions and prioritize other interactions. - Interact With Nearest
Enable
The interaction closest to the interaction controller will be used first. - Any Interaction
Disable
We want to limit this to only use item interactions.
Click on Add Organizer Type.
- Machine Type
Select: Collect Interaction
Box Collider #
We’ll use a Sphere Collider instead, so remove the Box Collider component.
Sphere Collider #
Add a Sphere Collider component using the component menu.
- Is Trigger
Enable - Radius
Set to: 4
Other Interactions #
Again, add a new interaction controller as a child object of the empty object.
Rename the created object to Other Interactions.
For other interactions, we want to interact with what’s right in front of the player, so we’ll stick with the default Box Collider.
Transform #
To have the box in front of the player, we need to move it forward on the Z axis.
- Position
Set to: X=0, Y=0, Z=1
The position is based on the Quickstart tutorial’s player, which has a radius of 0.7.
Interaction Controller #
This interaction controller should be able to interact with anything, so we don’t limit it.
- Priority
Set to: 1
Due to having a higher priority than the item interaction controller it’ll be used first (if it has an available interaction). - Interact With Nearest
Enable - Any Interaction
Enable
We want to interact without limitations.
Box Collider #
We’ll adjust the hight to match the player’s height of 3.
- Size
Set to: X=1.5, Y=3, Z=1
The finished interaction controller will look like this.
Create Prefab #
Create a prefab out of the root object, e.g. name it Multi Interaction Controller.
You can remove the object from the scene now.
Interaction Settings #
Next, we use the prefab we created in the interaction settings to automatically add it to the player.
Open the ORK editor and navigate to Controls > Interaction Settings.
Base Settings #
I’ll also list the general setup for using an interaction controller.
- Interaction Control
Select: Interaction Controller - Interact Key
Select: Accept
Or any input key you want to start interactions with.
Interaction Controller Settings #
We’ll automatically add the interaction controller to the player using our prefab.
- Add Automatically
Enable - IC Prefab
Select: Multi Interaction Controller
We’ll also place it at half height of our player combatant (height is 3, i.e. 1.5) to match it with the prefab’s setup. The box interaction controller (for all interactions) should be placed in front of the player covering it’s full height.
- Offset
Set to: X=0, Y=1.5, Z=0
Item Collection #
Let’s also change how items are collected – instead of showing a dialogue, we’ll just collect them immediately and use a notification to show what we collected.
Navigate to Menus > Item Collection.
Item Collection #
If you’re also basing this on the Quickstart 3D tutorials, you’ll have set up using an audio asset before collection, we’ll keep that.
In case you’re using an animation, it’d be best to disable using it (before or after collection).
Collection Dialogue #
We don’t show the collection dialogue, using inventory notifications instead.
- Show Dialogue
Disable
Tip!
You can also set up the Collection Dialogue to work similar to a notification, but you can’t make use of UI layouts or notification queues in that case.
For this, enable Auto Close in the collection dialogue’s settings.
Default Start Settings #
We’ll set up the default organizer type for new item collectors. This’ll be used by any new item collector that’s added to your scenes.
- Use Default Start Settings
Enable - Organizer Type
Select: Collect Interaction
We’ll also change the Object Turn Settings, since we immediately collect the items we don’t want to turn towards them. This should be the default setup in a new ORK project.
- Turn Starting Object
Disable
Item Drops Setup #
We’ll set up the organizer type for item collectors used by item drops.
Navigate to Inventory > Inventory Settings and change the following settings.
Drop Item Settings > Item Collector Settings > Start Settings #
- Organizer Type
Select: Collect Interaction
Again, change the Object Turn Settings.
- Turn Starting Object
Disable
UI Layout (Optional) #
We’ll set up an UI Layout that’ll be used to list multiple UI boxes (e.g. notifications) in a vertical arrangement.
Navigate to UI > UI Layouts and add a new layout.
UI Layout Settings #
- Name
Set to: Top Right Notifications - Layout Type
Select: List
List Layout Settings #
- Anchor
Select: Upper Right
Things will be listed from the upper right corner of the screen. - Padding
Set to: X=0, Y=100, Z=100, W=0
This’ll add 100 to the top and right side for listing things. - Spacing
Set to: 20 - List Fill
Select: Vertical - Fill Anchor
Select: Upper Right
Move Settings #
We’ll also animate moving things in the layout when something was removed, e.g. moving everything up if the first thing in the list was removed.
- Use Move
Enable - Time
Set to: 0.2 - Interpolation
Select: Quadratic > Quadratic In + Out
Notifications (Optional) #
Navigate to UI > Notifications, we’ll set up the general notification settings and inventory notifications.
The notification settings will show all notifications from other parts of the editor. You can also change the item notifications in the inventory settings.
Notification Settings #
We’ll start with setting up the default notification setup.
- Default Queue Mode
Select Add.
New notifications will just be added to already displaying notifications.
We’ll use the UI layout we set up to keep things organized.
Default UI Box #
Our notifications can’t be accepted or canceled and should close after 3 seconds.
- UI Box
Select: Action Info
Or any other UI box you want to use for your notifications. - Use UI Layout
Enable - UI Layout
Select: Top Right Notifications - Shared Layout
Enable
In case we use the layout somewhere else (and also as a shared layout) all content will use the same layout instance. - Can Accept
Disable - Can Cancel
Disable - Visible Time
Set to: 3
Inventory Notifications #
We’ll only use Add notifications for adding items to the player’s inventory.
So, we only have to enable showing the notifications and can even keep the default texts (I’ll list them anyway). We’ll set up the notifications for all inventory content that can be added (including AI rulesets and crafting recipes).
Item Added #
- Show Notification
Enable - Text (Message Content)
Set to: <name> (<quantity>) added
Equipment Added #
- Show Notification
Enable - Text (Message Content)
Set to: <name> (<quantity>) added
Currency Added #
- Show Notification
Enable - Text (Message Content)
Set to: <name> (<quantity>) added
AI Ruleset Added #
- Show Notification
Enable - Text (Message Content)
Set to: <name> (<quantity>) added
Crafting Notifications > Recipe Added #
- Show Notification
Enable - Text (Message Content)
Set to: <name> added
Save Changes #
And that’s it for the editor setup.
Don’t forget to save your changes by clicking on Save Settings at the bottom of the editor.
Item Collectors #
To get Item Collectors recognized by the larger interaction controller, we need to use the Collect Interaction organizer type we set up.
Start Settings #
The organizer type is set up in the Start Settings of interactable components.
- Organizer Type
Select: Collect Interaction
Object Turn Settings #
Since we simply collect the items without any dialogue or animation, we also don’t want the player to turn to the item.
- Turn Starting Object
Disable
Testing #
Test your interaction controllers on regular interactions and item collectors (using the Item machine type).
Having the regular interaction right in front of the player works as usual (the interaction being in the Other Interactions controller).
Not facing it will not allow us to interact with it (it’s still in the Collect Interactions controller). So far, this is the usual behaviour when using a single interaction controller.
However, the item collector (with Collect Interaction organizer type) is also available when not facing it and being a bit away from it.
Interacting with it now will immediately collect it and show the item notification.
Here’s the whole thing in action:
Tip: Unwanted Notifications #
When setting up Item Added and similar notifications you might get spammed with these notifications at certain times, e.g. from a combatant’s start inventory or your project’s start game schematic.
Nodes like the Add To Inventory node have an option for showing or not showing notifications.
However, you can also completely block notifications using a Block Notifications node – e.g. use one at the start of your start game schematic to block notifications and one at the end to allow notifications again to prevent any notifications from your initial game and inventory setup to show notifications.





