Wednesday, 6 April 2011

Unity Tools - Movement

Starting in Unity my first job was to just basically get an object running left and right on a flat surface. Using a very basic blocky placeholder of a chameleon, I imported it into unity and tried to find a script that would allow it to move left and right on the X and Y axis.  As Ecotone is a 2D platformer/puzzle all movement/values in the Z axis will have to restricted and set at 0.

Using the ‘Platformer Controller Script’ I used in the ‘Unity 2D Gameplay Tutorial’ some time ago, I imported the script into my project to use in my prototype. The Platformer Controller Script allows an object to respond to keyboard input, including moving left and right with arrow keys, jumping with space bar and running by holding the alt key whilst moving. The variables speed, gravity etc can be adjusted in the script settings.


The first obstacle I encountered was for some reason the character wasn’t sitting on the plane. It would hover slightly above the ground and run left and right in mid-air. At first I thought it might be something up with the model but then I remembered in the tutorials that the character controller works with a Capsule Collider which is a capsule around the object which determines how it interacts with the rest of the world. The Capsule Collider my object went way below the actual model (See image above) so all I had to do with scale the Collider to fit inside the model correctly.

Monday, 28 March 2011

Ecotone Design Pitch

Ecotone (formerly called Camoleon) was very thrown together project towards the end of Semester 1. I had taken more focus on the other two projects which unfortunately left to this one being neglected compared to the other two. The end result was two very quick Initial Pitch boards with a quick overview of the game and one page of a quickly done level design.
Despite the half arsed-ness of it, our M.A. Tutor Josh said Camoleon was his favourite of all three projects. So the project I spent the least amount of time and effort on got the best marks, try making sense of that if you will. 

Maybe there are subconsciously some reptile-esque influences in the world right now but since I came up with this idea several chameleon characters have started popping up in films. Specifically Disney’s Tangled and Rango, so it seems now my MA show will be under fire from the inevitable ‘You ripped off Rango/Tangled!’ With competitors like that it’s really tempting to just scrap the idea concept and start something fresh but I know whatever I come up with will have some smug pretentious geek chuckle to himself cause he’s seen it somewhere before. 

So my real challenge is ‘man-ing up’ and just going with the concept I have, and try to inject some originality into the important areas. In my spare time I've been reading a couple of Game Design related books I bought off Amazon.co.uk and one in particular is actually brilliant containing almost our entire degree in around 500 pages.

So my current goals for this project are developing some sort of visual design document, whether that's a pitch/GDD/level document or whatever and hopefully, a very basic prototype to demonstrate the game in action.

Ecotone Mechanic Functions + Flashbang Science Internship

As mentioned last semester, myself and another M.A Student Daniel Startin have been in an internship with a company called Flashbang Science for some time now. Our role in the company has been to transform their site to have more interactive elements which will draw children age 6-11 to the website. This included designing character mascots for the company (Flash the Bunsen Burner and Bang the Beaker) which can now be seen on the company website and on their portable trailer they use for science sessions.
 
On top of that, we have been in charge with all the design for the ‘Fun Stuff’ section of the website, working on puzzles, quizzes and flash games. Our current project is ‘Flashbang Tubes’ a pipe mixing game which will be the first of several games to hit the website next month (fingers crossed). The company also has intentions of developing iPod versions of all the games.

Besides that, our Friday morning lectures have started up again and this semester we have to attend them all because nearly half of the DE4201 module is an essay reviewing the lectures! I can’t be the only one in thinking this essay was made literally just to force students to attend those lectures. Thankfully the first lecture with Lightning Designer Claire Norcross wasn’t a mind numbing boring as the previous semester’s lectures had been. With lighting been such a significant element in creating atmosphere and mood in games, I would have appreciated some more relevant lightning techniques as opposed to lightning product designs.

Regarding the Ecotone prototype I’ve managed to create a list of all the mechanics/scripts I’ll need to hunt down/write for the very basic structure of the demo.

- A camera to follow the main character from left to right.
- A player controller so the player can move left or right.
- A normal jump and double jump.
- A collision detection so the player can jump off walls or surfaces.
- A player start for the character to spawn.
- Death Zones
- Checkpoints
- Pushing or Pulling Objects (Rigid Bodies)
- Grabbing and clinging to objects.
- Climbing on walls/ceilings
- Camo changes texture on trigger surfaces
- Material mechanics on specific textures change the physics of the game

The ones in bold are the ones I imagine will be the trickiest to find/write as they are very specific to my game concept whereas most of the others have more than likely be used in other projects and can be found in the Unity wiki.

Epic Backlogging

My main objective this semester is to develop one of my game concepts from last semester, the chameleon texture/property blending game. My goal is to create some kind of basic working prototype using a game engine (likely Unity 3D). Having little to no prior knowledge of using Unity 3D before the majority of this semester will probably be practising and learning how the engine works. Besides that alot of reworking and details will need to be worked out including level designs, all the scripts and animations I’ll need, the mood and atmosphere I want to set for the game and obviously some visual design documents to accompany the prototype. It’s taunting because this project is really jumping in feet first, I have no idea how doable or difficult any of the above tasks will be. I have a feeling at some point I’ll need to scrap alot of my initial concepts.
Camoleon (now titled Ecotone) first needs its main character. The protagonist is the character which will incorporate everything about the game; the player should be able to tell what it’s capable of just by looking at it on paper. However, there’s a surprisingly amount of diversity in Chameleon’s as shown.

Picking the appropriate type of chameleon isn’t as simple as just picking a style I like, there a several important factors that will affect the style I go with. The first is my own limitation, there’s no point me trying in doing some amazing Pixar-esque cartoon chameleon with lip syncing. The second limitation is what mood/atmosphere I want to create in my game. If it’s a stylized cartoon world, full of colour and just a light hearted platformer or whether I want to appeal to a different audience. On top of that, I have little experience (or patience) for modelling software so unless I plan on commissioning someone else to model for me, it’s gonna have to be a very simple design.

The early sketches (above) show some of the working outs with the shape and position of the joints. I wanted the Chameleon to be somewhere in between cartoon and realist, but one of the important elements I want to get across is making him appear vulnerable and physically weak. My plan at the moment is for there to be no enemies in the prototype instead the enemy/obstacles are the environments and nature itself. The chameleon should feel weak and insignificant in the scale of the world so it’s important he doesn’t look or come across as tough or brave but instead frail and scared.

One the trickiest task’s I see ahead of me is deciding whether the chameleon is going to run on two or four legs. For simplicity sakes I imagine two legs would be easier to animate, but the chameleon will need to use all four legs when climbing anyway so maybe not. My MA tutor Josh suggested it could stand on four legs but run on two legs as it picks up speed which is a good idea, but it might be harder than it sounds.

Tuesday, 25 January 2011

Unreal Engine + Unity 3D

After doing some research on both Unreal Engine 3 and Unity 3D I spent a day on each following tutorials and getting an idea for the tools and components each engine offered. The Unity 3D tutorial I followed was a step by step guide on how to create a simple 2D platformer using the assets and scripts provided by the tutorial.


Unity 3D Tutorial:The first thing I noticed about Unity that triggered alarm bells in my head was it's heavy reliance of scripting. Unity works with components which consistent of small Javascripts which tell the engine what to do and where to do it. After initially getting the hang of the scripts Unity's GUI is actually really user friendly and pretty simple to understand, it uses most of the same features as the Unreal Engine including lightening, built in physics, geometry building etc. Looking at the long long list of tutorials this engine seems really deep and powerful, almost overwhelming. The tutorial I finished (above) gives you a run down on how to make the game run on a 2D plane (basically just ignore the Z axis) and how to add scripts to GameObjects to make them react in an appropriate manner.

For anybody interested the tutorial can be found here: http://unity3d.com/support/resources/tutorials/2d-gameplay-tutorial.html

Unreal Engine 3 Tutorial:This tutorial was featured in the Mastering Unreal Technology guide book I recently ordered. It's basically a 'crash-course' on the main tools in Unreal. Including applying physics to game objects, particle effects, Kismet, texturing etc. This tutorial was more in depth and covered a broader range of areas in Unreal than Unity.

Semester Two Direction

Semester one concluded with my project of three separate documents containing detailed level designs for three different game genres. They included an action/adventure (God of War), an action/adventure (Legend of Zelda) and an unique concept themed around stealth and platforming (Camoleon). Starting the new semester, I need to decide on a direction to take my MA in. I am confident in my design abilities but my ideas are worthless unless I can prove they work and more importantly, are as fun in reality as they are in my head. For that end, I feel the focus on Semester Two should be finding a way to take my designs off the paper and into reality.
There are several options open to me, modelling software or game engines. To be honest I’ve always been intimidated by modelling/game engine software. I don’t like not having full control over my work and a machine often decides to ignore what you tell it and deletes things spontaneously. On top of that I don't have much patiences for computers, at least with my design work I know Photoshop will work if I want it to. Our tutor seemed to heavily push a game engine called 'Unity 3D' on a few of us. At the same time I have recently begun looking into the 'Unreal 3 Engine'. It feels like a bad idea to learn two complicated game engines at once, so I'm going have to make a decision on one of these engines soon.

I think it's important to consider my 'post degree' career, which of these engines is going to be more useful in getting me a job? From that perspective Unreal seems more logically, lots of the game developers are using the Unreal Engine to develop their games these days so it would be a useful skill to add to my CV. On the other hand Unity seems more 'indie' friendly and apparently offers alot more flexibility and creativity than Unreal.

I’ve always admired independent games but I can’t say I’ve ever really been into them that much, the aspect of video games that’s always appealed to me is being able to interactive with fictional worlds. Games have the potential to be one of the most powerful narrative mediums when they get it right. Sadly they rarely do, most titles are plagued with abysmal dialogue, zero atmosphere and clichés so overused it would make Michael Bay cry.

Developers still don’t appreciate the unique storytelling tools that this medium has and continuously ‘borrows’ from filmmaking (very often doing a poor job at that). Millions and millions of dollars pour into AAA titles, so why are so many games failing in this subject? 
It’s been really inspiring to see indie developers getting stuff right that big developers aren't. In a Semester One blog I mentioned what a great job Limbo (PlayDead Studio) did at creating such a strong moody atmosphere. Likewise, Amnesia (Frictional Games), is one of few genuinely terrifying games on the market. Amnesia has probably done more to evolve the horror-survival genre than any other big AAA game has done since Silent Hill 2. On top of that the innovation in the indie markets even the itunes charts is significantly more impressive than most best selling console games.

So whether to focus on a engine that the big developers use...or the small ones. I think the next step to take is to try both and see which I get along with best.

Friday, 3 December 2010

Exercise One: Camoleon - Completed


The final project of Semester one was the completion of 'Cameleon' my unique game concept revolving around the theme of camouflage and stealth. I can't help but feel this project got neglected a bit compared with the other two in Exercise Two. It's a shame too as towards the end I realised what an interesting concept this would have been to explore and build on. Perhaps I'll revist it in the future.

The project is presented over two A3 sheets, one sheet is the rough outline and introduction of the concept, explaining the key features and mechanics. The second sheet is a quick sample stage demonstrating proof of concept. Both presentation sheets feature a 360 controller diagram with instructions labelling it. I thought the fact the game only used three buttons was an important thing to point out as the simplest games are often the most popular amongst wider audiences.

One big difference between this stage and the other two is that this game is 2 dimensional. In a way it's easier to draw a two dimensional stage (it requires alot less annotations too) and it doesn't require complicated 3D diagrams. 

Conclusion: Despite spending little time with this project, I actually really like the concept and would consider delving deeper into it at some point. I seemed to put most my energy into Exercise Two as it felt like those were the two that would be most useful to show in a portfolio, to show I can work within limitation of a concept but still express my creativity. 

Exercise Two: Voodoo Dungeon - Completed


The next project I completed was the second half of Exercise Two, my Legend of Zelda dungeon based around the Carry/Voodoo Ball. The Voodoo Dungeon is a a three floor level, the objective being to reach the end boss like other Zelda dungeons. There are mini-objectives to reach this main objective, the most important being the capture of the Houngan's with the Voodoo Ball and carrying them to the main hall before firing them into the giant masks mouth.

The level is presented over three A3 sheets, one sheet per floor of the dungeon. Each floor has its only 2D top down perspective map with a key for all the icons and a 3D room layout of the more complex environments (usually rooms with puzzles). My main focus of this level was to show how versatile the one mechanic I added could be to the gameplay. There are various different uses for the Voodoo Ball demonstrated in both combat and puzzle solving. To keep things fresh I also tried to make sure the rest of the mechanics (hookshot, bow etc) were used in conjunction with my own concepts. As with God of War, a typed level walk through will be attached with the level designs with an in depth explanation of every room, puzzle and environment description. 

Conclusion: This brings Exercise Two to a close. Zelda was a very different type of game to design for compared to God of War. With Zelda I had to think alot more about the environments and puzzles rather than the combat mechanics. Infact, I'd say besides the bosses I didn't even give the combat much consideration at all. Also worth mentioning is it was interesting to do visuals for the presentation on both these games. I used a Zelda-esque colour scheme of greens and yellows for the Voodoo Dungeon and an older, orange and brown pallet for God of War. I imagine if I had the chance to revise all the work on these levels I would change alot. I would especially have liked to add more hidden areas and clearly illustration for a few objects.



Exercise Two: Hyperion’s Prison - Completed


The first thing I finished was the first half of Exercise Two and that was designing a level in an existing video game but implementing a unique mechanic of my own creation. The first one I finished was God of War with my Achillies Armour mechanic. The level is approximately 45 minutes of playtime and is about 50% combat, 20% puzzles and 30% exploring, climbing and platforming. 

The stage is presented over two A3 sheets, the first demonstrating the stage in its whole from a top down 2D perspective complete with a key on the right. Also on this page is some quick bullet point notes on the Achillies Armour and below that is a ‘Pacing Chart’. The pacing chart is something I had seen designers on previous God of War games talk about during development videos so I thought it would be worth doing one myself. The idea is to never let the pacing drop too low and if it does something should be introduced into the level to bring it back up.

The second page took a while longer than the first. The idea was to take the rooms from the 2D map that were difficult to communicate from a 2D perspective and draw them in 3D with annotations. The decision to do this came from the earlier ‘Reverse Level Design’ project when I had trouble communicating a more complex room layout in 2D.

To go along with the two level pages I will also type a level walkthrough with details regarding every room on the map. That along with the two map pages should hopefully be enough for anyone to pick up and understand the entire stage.

Conclusion: Overall I’m glad I picked God of War for this exercise. Although there were limitation on my creativity regarding the mechanics this level has taught me things the others haven’t. Unlike Zelda, God of War is a fast paced, adrenaline pumping game for the masses. It’s important to make sure the game doesn’t slack but it’s also important the game doesn’t repeat itself or start to feel tedious. I tried to make sure the puzzles and fights are placed appropriate in the stage so the player never feels they’ve had a bit too much of one thing at once.

Thursday, 2 December 2010

Exercise Two: Hyperion’s Prison

Just like the Voodoo Dungeon, I first drew up some concepts and locations by end before fiddling about in Maya to create a 3D model roughly interlinking rooms and demonstrating a sense of scale. God of War is more restricted in terms of design; combat is the most important theme of the game so alot of the areas need to combat arenas.  Between the combat there are some puzzles or short platforming sections.

One of the best bits about the franchise had been the sense of scale in the visuals and environments. With that in mind wanted to have that focus on scale and ways to portray that scale. The objective of the stage is to steal an item on a platform directly above the location of Hyperion’s prison, where the light is brightest and most dangerous.  At the very start of the stage the player is overlooking the prison, they can see the location of the objective far in the distant and they know their goal is to slowly make their way over to it, exposing themselves to more and more danger the closer they get.

The armour isn’t obtained till about halfway through the stage. The decision for this is the player would not fully appreciate it’s abilities without first witness the danger they would be in without it. The first half is getting closer to the objective and seeing the intense power of the light Hyperion emits, turning enemies to dusk upon contact. The player is at just as much risk and must spend that time avoiding deadly exposure. Once they obtain the armour however, after feeling the brutality of Hyperion’s light they will feel powerful and rewarded from being able to survive that intense power for prolonged time.

Wednesday, 1 December 2010

Exercise Two: Voodoo Dungeon

After I generated some puzzles and concepts for the Voodoo dungeon I started piecing things together to make very rough map outlines. I decided I would try something new in designing levels for this semester so thought it might be useful to very quickly block out shapes and sizes in Maya. I drew up some shapes and rooms to get an idea of the scale and overall shape on the dungeon. From there I could rotate them camera up 90 degrees to look straight down on the stage and import the image into Photoshop.

This very quickly gave me something to work from, I could annotate and draw notes on each room of the model and add/subtract areas I saw appropriate. With all the annotations and adjustments made I could start drawing around the model to fill out a 2D map of the 1st floor of the dungeon. I hadn’t decided exactly what the contents of each room would be at this stage, so as I went along and filled in each room I brainstormed and came up with some different puzzles and obstacles the rooms could have.

From my earlier Reverse Level Design exercise, I knew it was important that my level should be communicated efficiently to anyone who read it. When I reverse designed God of War I soon found out that rooms with trickery geometry and puzzles were very difficult to communicate from a top down perspective. The most obvious solution would be to draw a 3D map of the stage but with the size of this dungeon, a full 3D map would just look too confusing. Instead, I decided to take the rooms I felt might look a bit confusing from a flat down perspective and created small 3D diagrams of their interior, making it (hopefully) alot clearer and easier to understand. 
The diagram on the left is the original version of the room on the right. The perspective seemed a bit confusing so the room diagram was recreated from a clearer perspective on the right.
I knew I had to come up with an overall objective for the dungeon and not just sorely rely on the ‘Get Boss key, beat boss formula’. Taking into consideration both the Carry Ball and the Voodoo theme of the dungeon I created a concept where the player would have to catch three Houngan (Male Witch Doctors) and carry them into cells which they would then have to present in the main hall of the dungeon to make the path to the boss. The boss of the dungeon could be either the leader of the Houngan’s or some kind of entity they worship. The important point in this objective is that the player needs the new special item to complete the dungeon, so it’s not just a secondary pointless object.

The first floor of the Voodoo dungeon is an introduction to the setting/feel of the stage before the real objective is shown to the player. I selected some of the basic Zelda mechanics (hookshot, bombs, bow etc) that the player would have at this stage of the game. The range of equipment the player has for this dungeon would probably place it mid-way into a full Zelda game.

I got the basic shape of the 2D map from the blockmap I created in Maya and then added the little icons to represent items or enemies. I created several unique mechanics for the Voodoo dungeon; the two worth mentioning are the Voodoo Portals and Voodoo Curses.

The Voodoo Portals are large masks on the walls of certain rooms. When awoken their mouths open revealing a green portal inside which the player can step into. The portal will take player to another Voodoo Portal somewhere else in the room. This mechanic is introduced on the first floor very briefly in Room 8.

The Voodoo Curses will be introduced on the second floor. They basically manipulate the environment into a confusing puzzle and the player must locate the mask that controls the curse and shoot it with an arrow. Doing so will return the world to normal. A similar idea takes place early in the dungeon in Room 2, the entrance hall. The large entrance door can only be opened by shooting the correct masks littered around the hall.

The second and third floors will revolve mainly around catching the Houngan’s which will open the pathway to the boss and the end of the dungeon. Whilst revising or populating some of the rooms I made sure that all of the equipment the player has is used regularly to make sure the dungeon has variety and surprise. 

Tuesday, 30 November 2010

Exercise One: Mechanic Development

At the same time as Exercise Two, I have been exploring the mechanics I picked for Exercise One several weeks ago. For each mechanic I brainstormed the ‘character’ a game concept could be based around, the tone and age demography and different ways I could use the mechanic. From the brainstorms I drew away the key points and notes.

For the Morph Ball, some of the key points I explored were perspective (either making a 2D or 3D game) and the use of secondary character. One of the points I discovered was the transition between Morph Ball and normal mode is almost like two separate characters so I thought, why not literally make it two separate characters? The concept I drew from my notes is some kind of 2D, puzzle/platform game where the two characters both have different uses.

The Octocamo was another mechanic I explored, I knew the key for this was finding unique uses for the camo and exaggerating its power. I thought as well as taking the camouflage the player character could also take the element/texture. So if they were to take a metal texture the character would literally become metal. Each element could have different uses to solve or get around the environment.

The others had slightly less interesting results, for Game Speak
I developed a concept where the player would have different languages to talk with different species in the environment. They would have to talk in game to get out of situations or get NPC’s help. Right now, the next challenge is picking a concept I will actually take and develop a level around.




Monday, 29 November 2010

Exercise Two: Finalized Mechanics + Level Concepts

After further thoughts and input from some outside influences + opinions, I have decided upon the two mechanics I will be using for each game. For God of War, I have selected ‘Achillies Armour’. It really boiled down to the Sickle or the armour but I could think of more gameplay scenarios revolving around the armour.

I scrapped the Hades Helmet early on because I thought it would be pretty boring and unfulfilling to use as most of its perks are performed automatically by the NPCs.  I decided against the Mjolnir and Sword of Attila as there are already similar weapons on previous God of War games. So really, it was between the remaining three. The shield was next to go, first and foremost because the armour did the same job but the player wouldn’t have to be weapon-less whilst using it. I also had to try keep the appropriate God of War tone. Kratos is a character fuelled with rage and violence and him using a shield to protect himself didn’t gel as well as the other ideas.

To be honest, the decision wasn’t that difficult between the armour and sickle, I picked the armour because I’m already exploring Portal mechanics in Exercise One and wanted to make sure my work has some variety. So the Achillies Armour is the winner here.

Picking the Zelda mechanics were a little trickier as I thought I had several potentially interesting ideas to pick from here. First to the bin was the Climbing Claws. Although I can imagine some interesting segments using them, they’re pretty uninspired compared to some of the other ideas. Next was the Fairy Container, no real reason for chucking this one I just didn’t take a shine to it. I quite liked the idea of using the Spear in some of the level mechanisms but the scenarios in which you would have used it would feel incredibly contrived. 

I decided against the Magic Flute as it felt like it was giving me more work than I really needed to take on. So between the Magnetic Poles and Carry Ball, I had to write and see for which of the two I could think of the most secondary uses for it. Between them both, the Carry Ball won.  So the Armour and Carry Ball are the two selected mechanics for both games for which I will create a level design for.

It didn’t take me long after making those decisions to come up with concepts for a level. I knew for the Armour I wanted a level which would constantly expose the player to something dangerous that only the armour would protect them against. I quickly thought of the idea of Light or Heat. The movie ‘Sunshine’ (a film about astronauts travelling to the Sun), gave me the idea of the level I wanted. 

Keeping with God of War’s canon, I searched for a Greek God or entity that had the power of Sun or Light. Obviously Helios is the God of Sun in Greek Mythology but he has already been a reoccurring character in the franchise so I sought for something different. I found that the Titan Hyperion was the Titan of Light, also the father of Helios. From my knowledge Hyperion hasn’t made an appearance in the franchise as of yet so I thought that would be a good starting place.

Now in Greek Mythology, Zeus imprisoned all the Titan’s at the very pit of Hades in Tartarus. That gave me the idea that the level would be Hyperion’s Prison in Tartarus, over the years Hyperion becoming so furious and insane from imprisonment he emitted an intense light around the area. I drew some rough sketches and notes for the stage.

I wrote up a list of all the God of War play mechanics and tried to link them together to randomize and generate some order and time each mechanic could be used in the level. At the very start of the stage I want the player to see the scale of the stage from above it, so they know exactly what they are descending into.

My concept for the Zelda dungeon didn’t come as immediate as the God of War one did. I wanted to make sure the Carry Ball would get the right amount of expose so it had to be a dungeon where you had to shrink and carry things around.  Initially I drew similarities to the Carry Ball being like a giant Poke-Ball but it carried objects as well as living things but somebody made a passing comment about how it was like Kirby (a Nintendo character who sucks enemies up and spits them out). The idea of the item being alive instead of just an object seemed infinitely more interesting.

So with this idea of the Carry Ball being ‘alive’ in some way I gave some thought to scenarios. I thought maybe the item might once have been a person who had a curse put on them. Then I had to consider who would have the power to put a curse like that on someone. After a series of convoluted thoughts I came up with the idea of a ‘Voodoo themed dungeon.’ The Voodoo dungeon would have a series of curses on the rooms the player would have to solve, as well as enemies and environments being themed after witch doctors and Voodoo culture.

So with both concepts in mind, over the coming weeks my primary task is to come up with all the puzzles and environments for these levels before finding a suitable method of presenting these concepts visually. 

Sunday, 28 November 2010

Exercise Two: Legend of Zelda Mechanic Concepts

Like before I brainstormed numerous mechanic possibilities for a 3D Legend of Zelda game, mainly with a dungeon item in mind that I could use to design puzzles and obstacles with. Unlike God of War I could be alot more free and unique with the Zelda mechanics without worrying about make sure the equipment had to all be combat based.

1. Magic Flute: The first concept is a Magic Flute, an item which allows the player to control NPC animals in close proximity. When played near one of these NPCs, they will follow and assist the player until the flute is withdrawn. Different NPCs will have different unique powers that can help the player, e.g. a large animal might help you lift a heavy object etc. When playing the flute enemies will stop attacking the player and dance.

2. Magnetic Poles: Two large magnetic poles. When activated the two are inseparable. The player can place the two magnetic poles in specific spots and activate the poles at any time. If the player is holding the other stick when they activate it they will be pulled towards the other pole. The magnetic poles can be useful for moving large objects or reaching out of reach areas.

3. Climbing Claws: These allow the player to climb specific surfaces and walls much quicker than normal. It also allows them to jump from a wall onto another surface. The player can also use them to attack or dig holes in damage floor surfaces.

4. Carry Ball: A large spherical object the player must carry with both hands. Certain objects, enemies or characters of sizes usually too heavy to transport can be pulled inside the ball. When empty the player can shoot a beam from the centre, sucking whatever it hits into the ball. Pressing the button again will release whatever is into the carry ball. This can be used to carry large objects, trap enemies or carry NPC characters.

5. Spear: At first glance this mechanic looks like a regular Spear but it has several uses within the context of the game. Besides being used a melee weapon, the spear can be thrown to hit objects or enemies. It can also be used to in the place of a broken leveller, sticking it in the mechanism and pulling it like a switch. It can be used in other mechanisms as switches or handles to twist and turn devices.

6. Fairy Container: A lantern like object the player can use to hold one of three coloured fairies in the world. It can hold one fairy at a time and with a fairy inside, equipping the containing will give the player a unique power. Green: Will freeze time for a few seconds. Blue: Illuminant hidden objects or writing in the room. Red: Attract enemies to the player.

Wednesday, 24 November 2010

Exercise Two: God of War Mechanic Concepts


From my brainstorm I selected six mechanic concepts to put into God of War and construct a level from. Above is a quick mock up of the six pieces of equipment I have created for God of War. Like I said earlier, it was important to make sure all the mechanics influenced the combat in the game but with a useful second function to solve puzzles or obstacles. 

1. Cronus Sickle: The sickle can cut portals in the environment to and from the underworld. Creature will emerge from the underworld and drag one enemies into the portal before they close. Once used again and a portal is reopened the remains/red orbs of the enemy will return to the player. The player can trap enemies in portals and then release them in deadly areas to instant kill them. The underworld portals can also be used for puzzles, pushing objects into them and making them reopen elsewhere etc. The Sickle is also a decent melee weapon.

2. Helmet of Hades: When worn, the helmet allows the player to see astral objects and undead spirits in the environment. Any undead souls in the area will flock to the player and protect/fight them in battle as well as assisting them proceed in the environment.

3. Achilles Armour: The Achilles armour makes the player invincible from all damage from enemies and the environment. The armour will appear on Kratos when selected and disappear once magic/stamina is depleted.  The armour greatly increases the players weight making them run slower and attack slower. On the plus side, the immense weight of the armour can prevent the player from being pushed, blown or pulled off a ledge. On top of that jumping from a height whilst wearing the armour can smash a surface or object below it. 

4. Sword of Attilia: A massive sword the player can use in combat to defeat enemies. Made from steel the sword also has the ability to conduct heat and electricity. Conducting heat in the sword might help the player melt ice paths or warm up water, conducting electric might trigger mechanisms in the environment.

5. Svalinn Shield: A defensive and offensive weapon the shield can be raised to protect the player from enemy attacks and projectiles. The shield can be thrown like a boomerang, cutting down all enemies or objects in it's path. It can also reflect beams of light or lasers into other objects and surfaces.

6. Mjolnir: The Mjolnir is a powerful hammer, the player can attack with normal swings or swing and smash down to the ground with it. When the Mjolnir smashes into the ground it can create shock waves which might effect the environment around the player. It can smash large boulders or walls that might block the player.

Exercise Two Brainstorming

Exercise two is taking an existing game and adding a unique mechanic created by me, then designing a level within that game to show off the mechanic. I thought this exercise would be easier than the first but when I actually started thinking about it I soon noticed it was trickery than I thought. I had to make sure the game mechanics I selected were appropriate for the game.  For example, if I picked Resident Evil it wouldn’t be appropriate to have a mechanic which revolved around platforming as that would completely go against the rest of the game.

I had a look at some of games and mechanics from my exercise one brainstorm to see if it would trigger any ideas to which games I should look into. I wanted to pick different types of games so that mechanics I created for each would have to be exclusive to that game and not something I could apply to another title.

The Legend of Zelda was my first obvious candidate. Not so much because there is alot of variety in the tools and mechanics but because Zelda games are made up of dungeons which revolve around puzzles and enemies requiring you to use the new piece of equipment you gain in each dungeon. That alone sounded like a good match to show off a level design using my own mechanic. 

Each dungeon introduces a new piece of equipment the player must use to solve puzzles and beat the boss at the end of stage.

My second thought was the God of War franchise. The reason I thought of God of War is because the mechanics and equipment in God of War usually have dual usage. Almost every piece of equipment is used to both solve puzzles/obstacles in the environment and to bloody defeat enemies. As mentioned in an earlier blog, I’ve always liked mechanics that have one than one obvious use.


As with Zelda, I brainstormed some mechanic concepts in a God of War fashion, it was important to make sure they felt consistent with the rest of the series, the equipment being primarily combat oriented. I started by researching some mythic object/weapons from Greek mythology but it soon became apparent the series has already exhausted the most obvious/coolest Greek mythic concepts. So I looked into other mythologies to find some ideas that God of War hadn't used yet.
I tried coming up with different uses each mechanic might have besides fighting (some alot more interesting than other). My next step for this exercise is to define each of the mechanics with specific features and from there pick the one best suited to design a level around.

Tuesday, 23 November 2010

Exercise One Brainstorming

As stated in the previous blog, Exercise One is for me to create some unique game concepts based around existing game mechanics. The first thing I did was brainstorm as many games with interesting/unique game mechanics I could think of onto a piece of A3 paper. I tried to avoid obvious mechanics found in a broad range of games and stick with ones that are mostly exclusive to the title they are found in.

From the brainstorm I picked several different mechanics that sounded like they had enough weight to base a game concept around. I collected some reference images from each game and compiled them together below.


MORPH BALL: From the Metroid series (specifically Metroid Prime), the player has the ability to transform into ball allowing them to roll around the environment, access smaller areas and rolls up ramps. The Morph Ball also has the ability to drop bombs and climb 'spider tracks' to reach otherwise inaccessible areas. I picked this mechanic because I liked the idea of switching from first person perspective to third person when you control the Morph Ball. The Morph Ball was almost a game within itself, the controls and abilities were completely different from the regular mode and it gave the environments a completely different perspective. Conceptually I also like the idea you turn from a character/human into an object almost, often using the morph ball as a object or conduit in complex mechanism in the environment.

OCTOCAMO: Based on an octopus' ability to change it's appearance to blend in with it's environment, Metal Gear Solid 4 gave the player a special auto-camo suit which would change it's texture to blend into the surface the player was leaning against. The core concept of Metal Gear Solid is stealth and the player would use the octocamo to blend seamlessly into the walls, floors and objects of the environment to sneak past guards undetected.

MASKS: Majora's Mask's central theme was 'masks' the player would collect throughout the game which would help them beat dungeons and solve quests. When worn masks would transformed the player into a totally different character, with new moves and advantages to get around the world. I usually find games with 'transforming' mechanics pretty uninspired but Majora's Mask managed to get it right and all the main masks were useful and more importantly, fun to use.


GAME SPEAK: From the Oddworld series, the player character of the game, Abe, uses 'Game Speak' to communicate with members of the same species as himself. Buttons are assigned which allowed Abe to shout commands to other characters, including 'Follow me', 'Wait' and 'Work'. Using game speak the player must guide Abe and his friend to escape portals avoiding the enemy NPCs who too, have their own unique game speak which they use to talk to one another.

BRUSH TECHNIQUES: The Celestial Brush, was the one of the most prominent mechanics in the PS2/Wii game 'Okami'. At any time during the game the player could use brush techniques to fight enemies, bloom flowers and trees or alter the environment. This could including painting stars in the sky, manipulative water and fire or change the environments from night to day.

PORTALS: As the title suggests, Portal's unique mechanic revolves around the Portal Gun with the power to shoot an entrance and exit portal anywhere in the environment. The Portal Gun was used to solve small environment puzzles usually contained to one or two indoor rooms. The player could send objects or themselves through the portals in order to reach the exits.

The next steps for exercise one is to take these six mechanics and brainstorm some scenarios and different obstacles these mechanics could be applied to in the process creating some unique game concepts based around them. I will then select the mechanics with the most interesting scenarios and take them on to the next step of the project.