I'm working on porting my game "The Abandoned Planet" to console:
https://store.steampowered.com/app/2014470/The_Abandoned_Planet/
I'm working with a porting team to do this. In fact, one of them, Ewoud, reached out about an input issue:
But on to my question here -- the main custom aspect to my game is how to navigate from area to area. Chris developed a script called MiniLocation that I use to do this. This script was discussed here:
https://adventurecreator.org/forum/discussion/13234/menus-being-stored-in-dontdestroyonload#latest
Since we are porting to console, we are reworking the input to work entirely with a gamepad. I had the idea to eliminate the cursor completely from the game!!! This is my idea:
I'm currently using the custom script here to flash an icon over all enabled hotspots:
https://adventure-creator.fandom.com/wiki/Hold_input_to_flash_Hotspots
That script just flashes that icon over all available hotspots, but I would want that icon to appear over the selected hotspot only. But maybe that's not the road to go down. Maybe using the interaction icons in the Cursor menu is the right way to go -- although I'm trying to eliminate the cursor since it can be cumbersome with a gamepad analogue stick.
Anyways, any guidance here would certainly be appreciated. What would be the best road to go down for something like this? - Jeremy
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
This can be done with the use of a custom interaction system. The Manual chapter of the same name has details.
The behaviour you're going for, however, sounds quite similar to the included CustomInteractionSystemExample script - which involves clicking on-screen buttons to cycle through the various Hotspots in the scene. I'd recommend trying it out in AC's 3D Demo scene in a fresh project.
Having each MiniLocation store its own Hotspots would be the first step: if you have your Hotspots all be children of a shared MiniLocation parent, however, you can automate their assignment. Something like this, added to the existing script:
You'd then need a custom script that reads input to cycle through the available Hotspots manually. Something like this, adapted from the example script:
OK. This is a great start. Thank you so much Chris! I'll be working with the porting team to get this working. Thanks again. - Jeremy