This entry is late due to the fact that I kind of already did it? This week I had to complete what my Profs liked to call a "Vertical Slice"- where I take on aspect of the project and complete it to the end. In my case, the Vertical Slice was my AI. The following is the write up i did on it. Cheers :)
As a Game Designer, I was unsure at first as to what would count for my vertical slice. Would going over a single game mechanic be too little? Would drawing all the sprites be too much? For a good two or three days I was at a lost and couldn’t exactly pinpoint what I wanted to call my vertical slice. In the end, it took a friend looking over my shoulder to tell me “Just do that.” And so, I did.
For my Vertical Slice, I decided to finish creating the AI for my game…as in, all of it: what it does in a duel, on the game board, what cards to pick and when to use them, the whole 9-yards.
The following is detailed documentation on my workflow and any problems that came up:
I started by thinking about what I needed it to do. Looking up games like Hearthstone, Smash bros, and the like made me realize that a simple list of what to do and not do wasn’t going to be enough. And so…I hijacked the white-boards in the lab.
The hardest part about planning out behaviour trees like this is boiling down everything into very simple, yes or no questions. I was joking while doing the but the statement I made-I think- I still agree with. “Computers are ridiculously…. Dumb.”
Once everything was out for the world to see, I combed through every branch, thinking of any way an infinite loop or dumb result could occur and rewriting the trees several times, before I was finally happy with what I had. Then It was time to translate that into code (Or blueprints in this case):
And so I finished with this, Enjoy :)