I hit another roadblock, now with Bolt. While I got the flow to 'work' (as in the transitions were mapped correctly to each button, in other words, the flow graph was running without error), I was stuck in finding a way to show the transition between one gameObject to another (that had its own background image, text, buttons). I was warned previously that Bolt was an advanced and hard to master tool, and I soon realized that when couldn't find many tutorials on my problem, as most tutorials I found dealt with more higher-level concepts that involved manipulating 3d objects. As much as I wanted to learn the product I bought, I had to come to the reality that time was not on my side (as the project is due this week) and that I should work with an easier alternative. I was fortunate that a friend of mine who is also an amateur game developer gave me their copy of Playmaker for me to run on my Unity Project. Within an hour I had learned the fundamentals of Playmaker which included a tutorial on learning how to create state machines that encompassed transitions between button pressing and activating GameObject. PlayMaker's UI is not as sleek (and quick with shortcuts) like Bolt, in the end, I managed to create a state machine that encompassed both days (into a scene just labeled as 'Game'). I still used Inky (the software that created the Ink files) as a way to read the Ink scripts that Genevieve wrote, as the script format was easier to read alongside the technical annotations on it that helped me refer to which choice related to which paragraph.
Comments