Regular readers will know that I’m a fan of The Mission Business and their works (previously ZED.TO and Visitations). One of the Business members, Trevor, gave a talk at TEDxOCADU and it’s now online:
From the video description:
Trevor Haldenby is the imaginative thinker who focuses emerging technologies on exciting ideas.
He has worked as interactive producer and design consultant on a diverse array of digital projects: including the popular virtual world Habbo Hotel, and Earth Rangers’ Bring Back The Wild campaign.
Trevor’s own creative projects have won acclaim and redrawn borders in digital storytelling; including Painting The Myth: The Mystery of Tom Thomson and ZED.TO, an apocalyptic and futuristic transmedia adventure. These projects have been recognized with a 2012 Digi Award for Cross-Platform Fiction, Gold at the National Post Design Exchange Awards, and Best in Show at the Toronto Fringe Festival and World Future Society. Trevor is currently completing a Master’s of Design in Strategic Foresight & Innovation at OCAD University, and is co-founder of experience design collective The Mission Business.
Last weekend myself and a great team of game designers set out to make a game which uses basic EEG readings as a mechanic. The main source of inspiration of the game idea came from Doctor Who’s weeping angels. The gist of the angels is that if you look at them, they will get you when you look away. Don’t even blink.
Here’s what I sent out to the team prior to the jam so that we’ll all be on the same page:
So in sum, here’s the basics of the game:
Single player (1st person perspective)
Escape a procedurally generated room. Over and over again; like Groundhog Day but meant to scare.
Gameplay: Player starts with the camera locked on the statue then they have to navigate to the doorway to escape the statue without physically blinking. If the player blinks then the statue teleports to right in front of them, they are granted only three blinks. Too much blinking = death.
Art: all we need is furniture and a statue. I think dim lighting will allow us to get away with lame textures and stuff.
After that email one of the team members suggested we make the game playable without monitoring physical blinks, so we’d have a version everyone can play and a “hardcore” version. The core mechanics then should be similar in concept to how Slender Man games function.
In short, we didn’t finish the game but we did make something playable. We blinked.
Here’s what happened:
First some context, TOJam is a fantastic annual game jam held in Toronto and it gets bigger and better every year. The event has hundreds of people all descend on George Brown College to make games starting on Friday and having something playable by Sunday evening.
We wanted to use an entry-level EEG device the MindWave because I have previously seen it used for other games built on Unity. It was more complicated than anticipated to use the MindWave with Unity. We spent a good chunk of the first day trying to get the device to work.
This is after some time spent on Thursday trying by myself to connect Unity and MindWave. The image below shows that the device is connected, the connection software (ThinkGear) knows it there, but the application claims the device is not there. I didn’t know if I should’ve directed my anger at MindWave or Bluetooth. Overall, this was frustrating and I was hoping that the talented programers would know where I went wrong.
After some struggle we figured out how to connect the MindWave and rewarded with this screen (enlarge to see what the MindWave records):
Fantastic! Now we can really make this game interesting.:)
Then we discovered that the blink mechanic we wanted to use in the game was actually hard to read with the MindWave. They have a blink detection system but it’s not clear and requires some educated guessing. A lot of this effort could have been avoided if the company behind MindWave released some Unity project files and demos (they have one but the download link was broken).
Even though we successfully had Unity and the MindWave talking to one another we decided to put it aside because of Bluetooth chaos. It was time to make the rest of the game.
For the atmospehre of the game we originally envisioned something that seemed OK, but then got creepy like a museum after opening hours. When looking for reference pictures, I chanced across a great series of photos from the decaying Prince Edward Hotel in Brandon Manitoba (of all places) and it looked perfect.
Saturday saw the game go from primarily creepy to something more typically found in the horror genre: the abandoned building. It wasn’t a big change and was decided upon before most of the modelling was started.
Getting the room to procedural generate wasn’t too complicated and we got that working. As the code was being written we had a statue constructed and then built all the furniture that will be placed around the room. Things were going smoothly. We had all the pieces of the game being built separately and by the end of Saturday it looked like all we had to do was put the pieces together.
It looked like we’d even have time to get the blink working. Even if couldn’t get blink functioning we had other mind-reading functions we could incorporate.
Here’s an early screenshot from the game:
It’s so dark and gloomy to make the game hard without the MindWave.
It’s worth mentioning that we had off-site support for our audio and the fellow behind it made some insanely freighting sounds. The audio was done on time and, oddly, was the last thing we added to the game (just because it’s so easy).
The final day
After a late start, we got all the code from six separate computers on to one. We didn’t use Dropbox at the behest of the organizers, but in retrospect we should have broken that rule. Then we ensured that all the pieces would fit together.
I know it says 8:04, the Windows build was first.
This last days was the most hectic as it now relied mainly on the back of one of the programmers. We got the most important parts of the game working and some of the room elements working as well. We didn’t bother putting in all the assets we created as with what little time we had left we opted for function over form.
With that in mind, we decided not to incorporate the physical blink detection at all. It came down to a functioning game or a game that would probably break during the evening play sessions. One programmer went so far as to figure out some more of the MindWave but, due to too much going on, we didn’t incorporate it.
We figured we can easily add in the rest of the assets afterwards.
Around us other teams were play testing and celebrating their complete games. We, on the other hand, didn’t even have a chance to play test. TOJam game-building ends at 8pm and at 7:50 we tried our first complete build…and it worked!
This was particularly exciting for me as it was the first time at TOJam that I was part of a playable game by the end of the weekend. Of course, other games there were far better than ours, I was still pleased.
We will continue to work on the game to make it more playable and a better experience. By better I mean scarier. With luck, this will be playable for the TOJam Arcade for everyone to play.
Some stuff is obvious from what we ran out of time for:
More assets for the room and for the player to bump into.
Audio to accompany all the objects that move.
More early rooms to train the player before they get to the procedureally-generated rooms.
From play testing at the jam I noticed we need:
A way to end the madness as both “win” and “fail” states are the same – you end up in a new room. This was always intended but we never gave the player a stop button.
Better training levels to cue the player as to what’s going on.
The exit needs to be more visible.
We need a better way for the player to figure out where the statue initially is.
A BIG thank you to all of team Oh My Glob!
And thanks to all the wonderful people who made TOJam happen from the organizers to the sponsors to the volunteers! Without all their combined efforts we never would’ve had this game this far along.
In retrospect, I don’t know why I felt the need to write all this down. Thanks for reading!
Many years ago I decided that I will never work with Excel because the program is awful and is associated with incredibly boring things like accounting and scheduling. However, all that changed once I got into game design. Using spreadsheet software is an integral part to game design so it’s inevitable that one will have to use Excel, Google Docs, Numbers, or Open Office.
For people like me who harbour a disdain for spreadsheets some guides on how they are used in game design have been made. Over at Ruby Cow Games there is a two part series on how they have used spreadsheets for game balancing and probability in one of their card games. Part one explores the initial cards and their distribution. Part two explores how they used formulas to visualize data for balance issues and model potential gameplay.
Gamasutra has an article on how spreadsheets are used in game design which provides a good introduction to core features. So if you’re hesitant to get into the world of spreadsheets like I was, don’t fret: it’s not all boring numbers.
You can make playable games in Excel
Arena.Xlsm is a RPG made entirely in an Excel file. You will need to enable macros to play the game. The best part of the game is that it is made by an accountant, so they aren’t boring The image above is the game in action.
Games in Microsoft Excel aren’t new, which means that there are a lot of games you can play at work right now. Over at Techno JOurney they have a list of games in Excel you can download.
Sadly, I’m not going to GDC this year so to make up for it, I scoured the vault to find presentations I previously enjoyed as well as new ones (to me). I thought I’d share some of my favourite talks for other people who, like me, are missing out on this year’s fun.
The GDC Vault has a nearly every presentation and panel from previous GDC events. There is a ton of content within it which is really good and you should go through it to find stuff directly related to you. Below, are links to some choice GDC presentations from 2011 & 2012.
All the links are to free content in the vault (some presentations that have only slides below may have video for paid accounts).