Forum Discussion
Adventure game advice - would love your thoughts
Hi Gurus!
I'm building a kind of board game/adventure game for entering and safely navigating through a prison, where an avatar character follows a path (set of slides).
I have 4 avatars, but each has a different path. I am envisioning that choosing the avatar will take you to a board with the correct number of steps. However, there are a lot of common slides for each avatar as well.
In your opinion, would it be better to duplicate the common slides in each path (would make it neater, but the file larger), or to jump back and forth to the common slides and back to their individual paths (could be a navigation nightmare)?
Any thoughts on this?
Thanks in advance!
Hi Victoria. Would you feel comfortable utilizing a combination of variables and state change triggers to adjust the properties of each slide? That way, you won’t need to create multiple paths - just one that “updates” according to the avatar chosen initially.
I agree with Daniel. I will use variables to have different avatars navigate the same common slides for different paths. From a maintain view, if there are adjustments you don't need to duplicate again and again. And of course the file will be smaller then.
Try not to duplicate, it duplicates the changes you make during review. Use variables to track and control navigation.
The approach to states and variables in Daniel's example seems like it could be a perfect solution for this adventure game!
On a related note, something that might make setting up the right branching even easier is a new Storyline 360 feature we just released today: conditional triggers with alternative actions. Here's a bit more info if you're interested.Ooow exciting! I will have to ask my company for an update!! (our updates are controlled by IT unfortunately)
Oops! I did begin playing around with a version which (I hoped) would take advantage of master slides...but I abandoned it pretty quickly. Must have forgotten to bring that initial content back from the master slide. Sorry for the confusion.
Attached is the version I thought I sent over originally.
No worries. I will be using your code! Thank you so much for the help and inspiration, Daniel!! :-)
Thank you, Daniel, Joanne and Phil! Ok, that settles it. No duplication, just variables it seems. I am assuming what it looks like is if Avatar1 is selected. then jump to slide 16, if Avatar2 is selected, jump to slide 17 and so forth?
Exactly. I was playing around with this concept not too long ago and it seems to work well, especially if you take advantage of embedding content into states. In the attached example, I have a single avatar that acts as a "shell" for all the other characters.
Wow! That is fantastic, Daniel. It looks very straightforward going forward, but I'd really have to think about the PREV. I didn't even think about programming that way!
Thanks for the file; it will be really useful for me.
I appreciate that very much :-)
OK, update on its way! I can't wait, @Bianca Woods!
I've totally been there with companies that make all updates get approved by IT. It can really drag things out sometimes. I'm glad this time around went super smoothly for you!
Thank you. :-)
