Author: Bard Swallow
In between working on other projects, like typesetting articles for Carleton’s Undergraduate Journal of Humanistic Studies and slowly filling a spreadsheet with lemma and definitions of Latin vocabulary, I’ve continued my Unity training. In this tutorial, I learned more about lighting, assets, and scripting. I also built my first game controller to manage score-keeping and UI (user interface) and added my first sound effects.
Adding the game controller created some logistical problems which, though I’m new to them in Unity, are very familiar to me as a programmer. Essentially the problem is that when different objects are separated out, their information and variables are private. Sometimes, for instance, the game controller doesn’t have a way of observing something that happened to the player object, but it needs to be able to act on that information. Setting up the objects so that they can communicate about events is essential, but it’s not always obvious in the beginning that they need to share information. Figuring out that aspect of scripting will be very important in scaling development from demo-sized games to the large Unity project for which I am training.
Use arrow keys/WASD and mouse to play my game.
