auto-hide interaction icons not working with Global Variables.
Hello,
First of all, thank you for this tools. It makes possible for people like me who want to make an adventure games with zero code knowledge.
So I'd like to inquire about "auto-hide interaction icons" for a 2D game scene. In my game, there's a backpack object named 'backPack' in the scene. At the beginning of the game, I want this backpack to only have the 'look at' interaction. However, after interacting with a certain NPC in the game, when clicking on the backpack again, I want new interactions to appear such as 'examine' and 'use'.
What I've done so far is I created a "global variable" called 'moneyTalk',type boolean , value = False. The backpack has three types of interactions: 'use', 'examine', and 'look at'.
The 'look at' interaction triggers player dialogue speech. As for 'examine' and 'use', they have "global Variables : Check: moneyTalk Equal To True. All Interaction work like I expect.
What I haven't been able to do is to hide the interaction icons for 'examine' and 'use' at the beginning of the game. How can I achieve this? In this case, I've chosen the interaction method as 'Choose Hotspot Then Interaction' and Check Auto-hide interaction icons based on Hotspot
Thank you
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
Welcome to the community, @pjUnzip.
Global Variables shouldn't need to be involved for the running of certain Interactions: you can use the Hotspot: Change interaction Action to enable/disable a Hotspot's specific Interactions at runtime.
Thanks, use "Hotspot: Change interaction" It's all work now.
But Im not sure I do the right things because my NPC is in another scene. So I need to use "Variable Check" in 'OnStart' like this in the image below.
or there is another better way to do this, please let me know.
Thank You
If it's based on a condition in another scene, then yes - you'll need to run the on/off logic when the scene Hotspot starts.
To keep things more tidy, however, you can unset this Cutscene from the Scene Manager's "On start" field, and instead attach the ActionList starter component to your Hotspot, and configure it to run that same Cutscene when the scene begins. Effectively, it'll be the same thing - but it'll mean that your Hotspot's logic is compartmentalised.
Got it,Thank you for your assistance