Truck sketch

I did up a new Truck design sketch. I think I'm getting closer to capturing the character of Truck. Seriously, this an anthropomorphic garbage truck who's sole purpose is to alternatively smash and gather things in his world, to make a larger and larger garbage pile. I'm really just designing him as a character because I find it entertaining.

I compressed about 45 minutes of sketching down to 3 for the video. Much longer than that and some of the slower bits really get pretty boring to watch.

I have never recorded myself sketching. It's weirdly intimidating. Most of that self conscious feeling I use to have when someone would watch me draw or paint has faded with practice and time. Now, if someone comes to peek over my shoulder while I'm drawing, or modelling, I don't really worry about what they think of my doodles. I'm usually much more concerned that they will just get bored. Recording myself sketching, I'm just worried that the screen capture will break or the computer will crash. It felt like I was drawing to beat the clock. After a few minutes I sort of relaxed into it a bit, but this is definately a new process, and it will take me a while to get comfortable. Modelling with the screen capture running will be... interesting.

screen capture

I finally got my screen capture software to work properly.
Here is a quick test I did to make sure I could capture any concept work.

I sped it up quite a bit, because nothing is more dull than watching someone draw a poor sketch for a long time.
I'll be trying to capture any concept and modelling I do. The sketches will likely be better, but I'll still try to keep the videos short.

Is there anything that anyone would be particularly interested in seeing a video of? Would commentary be good?

Also, fresh builds are always going up. Go test it out. There is some sound now and the truck is much harder to flip.

Experiments

I'll spare you the usual novella. I tend to just pound on the keyboard, orangutan style, until my hands get sore, but I'm a bit tired so here's a small one.

I posted up my development list for TurboGarbageTruck. It's not really a design doc. It's really just a list of things that I want to add or test out. I expect that I will grow the list fairly steadily and then drastically hack it down when it grows too unwieldy.

In the latest builds I've been conducting some experiments. I created an infinite terrain setup. Essentially if you drive out the north side of the environment you will come back in the south side. You can drive in one direction forever... or until the physics break and the truck falls through the world. This is just stage one of a larger experiment with continuous environments. So far so good.

The truck flips over way too easily. Working on it.
Also, currently there is no limit to the speed that the truck can reach. You can break the sound barrier in that mofo. Still not sure if that is good or bad.

TurboGarbageTruck

My newest game experiment is up.

It's TurboGarbageTruck... a name and concept stolen entirely from my son. So... not really my idea.

I have a theory that feedback on a game (or quite probably any other media) can't be gathered too early. I suppose it isn't much of a theory, and it really isn't my theory either, since every major developer employs, or keeps employed, dedicated testing staff. Feedback is what these people do. It's all they do. It's less of a theory and more of an imperative. And again, not my idea.

I've talked about "open kimono" development before. I've also seen this referred to as "open door" or "transparent" development. The basic idea is that you let your potential players in on the development of your game as much as possible, while you are making it. Demos, tests, concepts, design documents... they are all on the table. I posted up builds of my last project while I was working on it, but I really didn't commit to open development. I think I know why very few developers even attempt it.

It's scary as shit.

There is that old chestnut "you never get a second chance to make a first impression". So I could go ahead and post up all my dev builds, any concept art, any design docs, knowing that the first version of any or all of those things will probably be garbage. Going by the first impression rule, that would sour anyone who saw it on all future versions of the game. The damage would have been done with the first broken play test. A trend toward development secrecy almost goes without saying, if this first impression rule has any merit. It does and it doesn't.

Minecraft.
Kickstarter.

Everyone brings up Minecraft. Constantly. For good reason. It's a goddamn phenomenon. When it was first released, no one would have guessed that it would be a phenomenon. No one. Because it sorta sucked. Mojang didn't catch lightning in a bottle. They built steam slowly, one beta version at a time. Only thing is, slowly in internet time is anything longer than six months. To those not acquainted with internet time, this is pretty much the same as instant. Had they toiled in secrecy for that same amount of time and released the current version of Minecraft whole hog, to an unsuspecting internet, I suspect it would be met, initially, with a collective meh.

Minecraft isn't some strange exception to the rule either. Kickstarter is a funding and business model pretty much built around showing your work. Offering updates and "making of" style information to the people who will fund your project is pretty much a requirement. I doubt that there are any successful projects on Kickstarter that say "Fund my project. It's a super great idea that I can't tell you about."

I only chose these two examples because they are current and relevant to indie game development. There is a long history of "patrons of the arts" which is short for "I will pay you to let me look over your shoulder while you work". That's exactly where the first impression rule breaks down. If you are meeting someone face to face and you know that they will be judging you, as a person, by all means, bring your A game. When it comes to "things" the rule no longer holds up. In fact the exact opposite is true. Everyone likes to watch things being built. Skyscrapers, houses, cars, paintings, movies, and yes games. As long as you don't have to do the work yourself, watching it get done is fascinating. I've lost count of the amount of people who stood around to watch me apply decals to their car. Where things that people are building are concerned, it would probably be more accurate to say that the final impression is what matters. If the final work resonates, any problems during the making are forgiven. People have died while making movies. Died! Making movies! Successful ones. As a first impression, I can't think of much worse.

So transparent development shouldn't really be all that scary. I understand the need to withhold some details. Plot twists, puzzle solutions, easter eggs, etc. Most players have such an aversion to anything that would spoil their fun, and rightly so, that they would likely cry foul if you released that stuff anyway. Any other development details really don't need any protection. In fact, I think a lot of the best big budget titles could benefit from transparent development. Patrons of the arts love to look over the shoulder of their heroes at work.

I'm starting TurboGarbageTruck in the most transparent way I can think of. I'll let you play it. I'll be adding a method for you to play all the previous builds and experiments too. As I get to scanning them I'll be posting up concept art and maybe even design docs (though this game sort of speaks for itself). I'll definitely be posting up my road maps and upcoming features. Please feel free to ask me if you want to know more about anything I'm working on, or if you just want to call me out on anything I'm doing that you think is bullshit. I'm good with that.

Update: When I wrote this I hadn't read the Game Developer article where John Graham of Wolfire Games pretty much breaks down how and why open development works. If you're looking for an example they seem to be the current masters.

old and new

reboot

Okay, I’ve been working on the same project for ages. In multiple languages, and a couple different frameworks. My plan from the outset was to create something small so that I could learn the tools and languages I would need to create my own games. Not clickity click around in some game builder either. I wanted to have a really firm grasp of what I was building. I wanted to write the code, and work with the tools on a fairly low level. That said, despite overwhelming evidence to the contrary, I’m not a complete idiot. I realize that the constraints of time and familiarity with the tools wouldn’t allow me to create my own game engine, or anything like that. I started by Using first XNA, dabbling with OGRE, and then settling on Unity. All three allowed me to work quickly enough to see progress, but still required that I learn JavaScript or C# and, more importantly, some work flow, structure, and design strategies.

If, in the future, I’m ever provided with an opportunity to work with a programmer more skilled than myself, a parrot or eggplant for example, I’ll at least understand what they are talking about.

I just recently created an app for the Blackberry Playbook. It is currently going through approval. It is a very small, very simple toy for very young children. Random shapes bounce around the screen and you poke at them to make them burst and fade away. You also hear a satisfying sound. That’s it. It’s called ShapeToy. The point is, simple or not, ShapeToy is a completed app. It’s a finished thing. That you can play with. I’m pretty sure that I couldn’t have done that a year ago.

The main problem with “Color Game” is that I never really designed it as a game. I created a school, and sent myself too it. Like school, learning was the point, and anything that you created has very little value as a stand alone work. There may be something that I can dig out of that and polish up into a game. ShapeToy was designed for a specific purpose. Until I reconsider the color game concept as a game first, it will never really be successful.

So I have decided to shelve Color Game for a bit until I can really rethink it.

I have started up 3 new projects. Each one designed to be a game first. I’ll likely learn something along the way, but these projects are all focused on the finished product, not the process. I’ve started on the one that seems to be the most unabashedly “video game”. If, or rather, when I get hung up on some issue, I will bounce around to the other two projects, hopefully learning something new and clearing any mental blocks. I fully intend for at least one, if not all of these projects to be finished things. That people can play, or even buy. Probably on a phone.

I’ve already started working on the next iteration of ShapeToy, that includes letters, numbers, and different sounds. I’m just waiting on a tool update from RIM that makes some of the local file storage/access features of HTML5 useable from an app. Since I think there is still an enjoyable core to the thing, I’ll probably dive back into Color Game as well, but for now, I think I’ll focus on making some games.

what did you do at game jam?

It's been so long that I was tempted to title this post "Neglect".

I participated in the Global Game Jam at the end of January, so I figured I should take a minute to reflect.
As soon as I arrived home from Mount Royal, my son asked me "what did you do at game jam dad?".

So I have to think. What did I do “at game jam”. More importantly, what did I learn.

My team were all basically strangers. Two programmers, two artists. A couple of us had met very briefly at igda meetings, but that's about it. To me, that seemed to be the right way to do things. Meet with a group of strangers, put our heads together and build something. Anything.

We started by finding ourselves a nice, quiet, centrally located, fishbowl. That glass room became our studio / flophouse for the weekend. Next we needed to decide what to build. We had a basic concept based around herding creatures to their doom. That concept was quickly fleshed out in the most ridiculous ways we could conjure. We then moved to divvying up the work. We split along very obvious art / code sides. The programmers would write code, and the artists would create the art. I went to the event fully expecting to find myself in a team full of artists. I figured I would probably end up with visual studio afterimages permanently burned into my retinas. I was cool with that. I was much cooler with leaning back painting sprites in photoshop for 48 hours. So we put our heads, and talents, together, and we made... something.

The truth is our game was a bit of a failure. It's a bit janky, the controls don't really do what they should, the little animals kind of run everywhere, and there is no front end. It functions, but only just.
That does not mean that I think that the team was unsuccessful. In 48 hours we went from not really knowing each other, and not having a game concept, to creating a functional HTML 5 "thing" that at the very least, made everyone grin for a second.

So what did I do “at game jam”. Working on my own I get pretty used to wearing several hats. Scratch that. I wear all the hats. At the same time. It's a leaning tower of fucking hats, and most of them don't fit me. At game jam I wore one hat. I wore the artist hat... Actually I probably just wore the brim. I didn't go there thinking that this would be a relaxing time. I went to do some work. It just happened that there wasn't a ton of work for me to do there. It's been a while since I've had to brave a tense all nighter to meet a deadline. Typically in those situations I would have more work than Any single human could hope to accomplish, and about 37 seconds to complete it. The days when clients call up at 4:30pm on a Friday, requesting radical changes for an important meeting Monday morning at 9:00am, are hopefully behind me... or at the very least, I now have the options of saying no or setting my price. My expectation was that I was, in fact, doing this exact thing, to myself. Instead I felt incredibly relaxed. There was quite a lot of work to do, but I could have easily done double. At one point during the 48 hours I thought about offering up art services to the other teams diligently working on their stuff, but :

1. most of the teams seemed to be well into their projects, and adding another person might be detrimental.

2. a few of the teams were working toward possible commercial releases, and really couldn’t recruit new team members for legal reasons.

3. I was enjoying just relaxing and drawing environment tiles.

At another point I made a 3D model of one of our characters and did a turntable animation of it. I was reasonably sure that this would never be used in the game, but it was fun to do, so I did it.

As it turned out, about 1% of all the work I did actually ended up in the game. At the time, I found that endlessly comical. I still find it funny.

So I really didn’t do that much work, but what did I learn “at game jam”.

Bring an air mattress. The floor is hard.
Bring a kettle. Sometimes you want tea at 3:00am.

I’ve created countless seamless textures for 3D work, but I had never created a tile set for a 2D game. I am pretty sharp with the photoshop and I can hide repeats like a mamajamma. There had just never been any call for me to create a tile set. While I didn’t learn any new techniques, I did do something new, and that is always fun.

I learned that tools are important. Not just important. Perhaps the most important. Or even the mostest important. On the art side we had tools out of every available orifice. Couple different versions of photoshop. Some vector tools. A few different animation softwares. 3D modelling and animation tools. Graphics tablets and touchscreen transforming laptops. Paper. Pencils. Burnt sticks and cave walls. At one point we could have built stuff from spiral pasta. Had anyone ventured into our centrally located fishbowl looking for art, we probably could have stuffed their pockets with doodles and sent them on their way. Since we were creating a HTML 5 game, I was unaware of any coding tools, engines, frameworks, etc. that could have helped our programmers. I’ve since found several great HTML 5 tools that we could have used to speed things up and lighten the load on our team, but not having those tools available when we needed them probably hurt us. I still think our programmers pulled off some amazing things given the time allowed.

I think that, next year I will try to offer up my time to other teams. Maybe I will create a work board for people who want to offer up their time to multiple projects. Teams can go up to the board and put down a request for art or music or assistance from an expert in some field or other, and anyone with time to spare can check the board to see where they can lend a hand.

I think mostly I remembered that it’s fun to work with other people... not really something I learned, but it’s certainly something I needed a refresher on.

Asymmetry

previous posts in this series
Intro
Randomization
Engagement


Asymmetry

Before writing this I tried really really hard to think of a sport that is asymmetric. Baseball and Cricket are played asymmetrically, with one team in the field and one team at bat, but the game requires each team to take turns at bat or in the field, making the game, overall symmetrical. It is possible that you could consider hunting and fishing to be asymmetric sports, with the hunter versus the prey. Hunting is not really a game, but a primary survival skill of human beings, as predatory animals. As a survival skill, people finding fun and engagement from hunting is fairly easy to understand. People also enjoy eating and using the toilet. These are not things that most would consider games. If there is any game to be made of hunting, then it is a competition between the hunters and not actually between the hunter and the prey. Of course that makes hunting and fishing, again, symmetric.

Many games (board games, and video games) have played with the idea of asymmetry. The playground game "tag" is a great example of an asymmetrical game. Playing a game of tag never requires every player to be "it". A player could play tag for hours and never be "it". For the players that aren't "it", the game can be fun and engaging, but, as any kid will tell you, tag is more fun when you are "it". Video games, likely starting with breakout, but then really with space invaders, made sure that the player is always "it".

The really difficult design problem that space invaders, being a video game, solved is that it sucks being the guy who is supposed to lose. It is much more fun to catch one player after another as "it" than to be one of many people waiting to be caught. No human would ever willingly play as the space invaders. This is the playground role handed out to little brothers and sisters for centuries. The dutiful punching bag. This is a role only a computer opponent could relish. A cursory glance at the standard game board of space invaders would lead most to believe that the player is faced with overwhelming odds and will need to call on all their dexterity and focus to prevail. That only becomes true as the game progresses. For the first few minutes the player is omnipotent. You are the one in control of the game and the computer will suffer the beating you dole out and keep coming back.

Maybe I should change my terminology. It is probably not so important that space invaders be a "video" game. It could be an incredibly complex mechanical shooting gallery. What is more important is that it is a "computer" game. Sure, you could compete against other players to see who can set a higher score, making space invaders a symmetric game, but it doesn't require another human player to be a complete game. It only requires a computer. A computer that doesn't care that its only role will always be the "not its" to the players "it".

Having this perpetual digital soup can available for the beating, changed game design. Ideas that you would never be able to get a team of real humans to rally behind, became the norm for video games. The next time you have a bunch of people around getting ready to play, soccer, hockey, baseball, football... or really any other sport, ask them if they would all rather line up and run straight at you while you punch them, one at a time, in the nose and crotch. They will probably tell you that idea doesn't sound like much fun. Then ask a computer. Computers are always up for it.