No matter what you do it will take a lot of work

I've just wrapped up an update to my iOS game Snappy Word. It's a word game built in Swift for iPhone, iPad, Apple Watch and iMessage.

Snappy Word

I originally wrote the game for Right Pedal Studios back when the Apple Watch came out. The game was one of the launch apps and I'm quite proud of being there at the beginning.

I was lucky to get Snappy Word assigned to me when Right Pedal wrapped up, so rather than ~re-releasing it I decided to do a major update. This meant making it work with Swift 3 and the latest WatchOS, adding in an iMessage version, redoing the art and adding in a new game mode.

Despite it being a fairly simple 2D word game the rewrite in Swift 3 and the addition of new frameworks ended up taking a few months of part time work to finish.

But I learned an important lesson doing this update:

No matter what you do it will take a lot of work.

I've already started my new game - a cool 3D game built in Unity with my mate and talented artist Pete Mullins.

Billy Carts made in Unity

The amount of work to get the initial 3D game up and running was probably a little less than it took for me to wrap my head around the iMessage framework. But showing the 3D game to friends got oohs and aahs. This was a "real" game.

This game is definitely a leap ahead of my previous stuff, and yes, it will take a lot of work. But you know what? I'm really looking forward to putting in that work because this time the effort is going to show on screen.

As I've learned everything takes effort so you might as well go for gold :-)

Design Tips! (Part Two)

Here is Part 2 of the Design Tips from my Passfield Games now defunct Design section. As I mentioned last time, these are based on the old adventure and action platform games I used to make, but may have some useful gems of advice within...


#4 A Game World is a Precious Thing to Waste
Or, Avoid dead ends with no rewards

If you have areas in your world that serve no purpose except to pad out the game then you need to redesign the level. Lose the dead areas or create a reason why they are there: you could add some bad guys, a bonus (even if it’s hidden) or an NPC with some back story or clues.

And remember, bigger is not always better.

A tightly packed Quake III Arena level is way more fun to play when there’s always some action.

#5 Be Consistent
Or, Don’t mess with the player’s mind!

This applies to all aspects of the game design from menu layout to character design.

1. Music. Game selection menus should always play the same music. In game music can be shuffled.
2. Clues. If a “Red Wall Tile with a Crack” can be smashed to reveal a secret cave, then all “Red Wall Tiles with a Cracks” should do the same thing.
3. Danger. If the player can swim in blue water then NEVER have blue colored water in a later level then can kill the player. For God’s sake change the color to Slime Green or Lava Red!
4. Obstacles. When replaying a level for the umpteenth time a player shouldn’t find a bomb in their path that wasn’t’ there on the last three attempts.

GAME DESIGNER TIP#2
Don’t waste time writing up detailed design documents. The team will never read them. Ever. It’s a complete waste of time. If your publisher or employer insists that you write huge design documents then simply paste random blocks of text into a Word file. You can find chunks of random text on most web sites. Try using text from this site!

#6 Lead The Player Through The Level
Or, Getting lost isn’t fun

All game levels have a start and an end. Players should be led through the level in an intuitive yet unobtrusive way.

Banjo Kazooie uses musical notes to plot a path through the levels. Crash Bandicoot uses crates and apples. Snow boarding games use slaloms and flags. Racing car games use time gates.

Use these paths pointers to take advantage of the lazy gamer! And yes, it’s okay to take advantage of lazy gamers as long as the astute and hard playing gamer can appreciate the design.

For example:

1. If the Apples that your game character has to collect lead down a certain fork in a path then place a special bonus item down the other path. Place a time gate just after a sharp turn in a racing game so the player will automatically race toward it as soon as they turn the corner – but add a side road at the corner that can hold a special powerup.
   

#7 Bad Guys Should Never Overwhelm The Player
Or, No one likes to be picked on…

This is a pretty straightforward design rule but some people tend to forget it. If the player has a gun, for example, don’t put them up against a horde of bad guys armed with rocket launchers. Try and balance the difficulty of the enemies with the experience and abilities of the player.

And, unless it’s absolutely necessary, make sure the player starts the level with a bit of breather – don’t drop them into a horde of enemies intent on killing them. If you want to have a horde of enemies then give them a chance to catch their breath first – then you can smash their false sense of security and unleash the horde.

You can ignore this rule if you’re making a game that’s all about killing loads of bloodthirsty aliens and/or goblins.