Game Dev Log #1
Over September I’m working on a simple text based game with some visual aspects in Unity. My first week and a bit has been spent anticipating design hurtles. I’m building it in an unfamiliar engine and as an almost complete beginner in coding. Given my very little programming experience, any coding whatsoever, like anything at all, is difficult and tiring.
That being said, the actual planning of what/how to implement my ideas in code is kind of exciting — until I have to actually implement them that is… which is what I started to do yesterday. I had ordered another monitor to make my work space more manageable and had been waiting for its arrival before I started. Yesterday it arrived and I began to go through some of the tutorials I had book marked over the last couple weeks.
I had already discounted a few of them prior to anything because as I made a list of features and thought about implementation, it became obvious many of the tutorials were for drastically different things that what I planned to do. Given that, there were only a couple tutorials worth looking at and only because they clarified some of Unity’s features and interface. Entering a new program is somewhat daunting so the hand holding there was actually quite appreciated.
After I felt a bit more comfortable with the interface, it began to become increasingly obvious that Unity can do a lot of things that I do not understand AND a lot of the things I want it to do are not obvious. Given I want to make a text based game in a physics based engine, it shouldn’t surprise me that much of what Unity can do is not what I want it to do.
After giving up on finding a tutorial that would essentially show me how to make my game, I eventually found some success just trying to make a single feature work: a button!
My plan is to essentially make a game menu that leads to other menus using GUI elements because that’s really what the back end of my game consists in: 2D pages with doodads on them that the user can interact with and which, when interacted with, change either the page you’re on or the content of the text on the page. The dialogue part, which I just very poorly described, is actually going to be the most complex, I think, but this morning I did, successfully, create my first button. Which is not a minor thing. It is a major element of my game which I successfully made a very poor version of which actually did a thing I wanted to do. It’s an ugly button and it only does one thing I want it to do (and not to the full extent I want it to do it), but it works. And so I’m pretty happy about that. Day 2 of n00b coding and I have part of one of my games features partially implemented. That, is pretty cool.