Saturday, 26 February 2011

Introduction to Computer Gaming - Week Five - The Virtual World vs. The Real World

After reading the article on the massive theft on Eve I decided to do some research into virtual incidents and how they made an effect in the real world/people in it.

It wasn’t long until I came across a very interesting article entitled ‘A Rape in Cyberspace’ by Julian Dibbell. I spent a good while enthralled by it; the events that transpired were both fascinating and horrific.

The article centred around a startling event that occurred in the multiplayer computer game (or MUD) called LambdaMOO; a text based online virtual reality game, capable of having multiple users (players) connected at the same time.

The incident involved a player using a ‘voodoo doll’ subprogram, which allowed him to control other player avatars and have them do things against their will. These actions, which included describing sexual acts that character performed on each other, went far beyond the community norms to that point and continued for several hours.

The repercussions of this act on the virtual community were immense; they were interpreted as sexual violation of the avatars and provoked outrage amongst the LambdaMoo users, raising questions about the boundaries between the real word and virtual reality, and how the game should be governed in the future.

After the incident occurred numerous users posted comments about the emotional trauma that was caused by the player’s actions. One user, whose avatar was a victim of the ‘cyber-rape’ called the attacker’s voodoo doll activities ‘’a breach of civility’’ while in real life, ‘’post-traumatic tears were streaming down her face.’’ However, despite the strong emotions, including the fury voiced by many users on LambdaMoo, none were willing to punish the user behind the incident through real-life means, after all no ‘real’ crime had been committed, no bodies had touched, no real act of violence had taken place. This being said, the effect it had upon the victims was real; after all the attacker had violated their minds, and is not the mind part of the body?

One victim posted a request that the attacker player be ‘toaded’, a term meaning to delete the account of the user and their avatar; it was, in its purest form, a request for the avatar’s execution.
Three days after the event users of LambdaMoo arranged an online meeting which Dibbell (the Article’s author) attended, to deliberate what should be done about the user who caused the incident. The meeting lasted almost three hours, but no definite conclusions were made. After attending the meeting one of the master-programmers of the game decided on his own to terminate the user’s account. Additionally, upon his return from a business trip, LambdaMoo’s main creator, Pavel Curtis set up a system of petitions and ballots where anyone could put to popular vote anything requiring master-programmer (known as ‘wizardly’ in the game) powers for its application. Through this system LambdaMoo users put into place a ‘@boot’ command, which temporarily disconnects disruptive guest users from the server, as well as a number of other new features.

The fact that such an event could stir such emotion and make such an impact to the players of an online game, along with the changes to the game and the ‘community’ that was then build through the attack’s actions, are extraordinary.
The events described in the article made many people curious about the legal implications of online activity, including Lawrence Lessig, and the author of the article himself (who went on to teach cyberlaw as a Fellow at Stanford Law School Centre for the Internet and Society.)

After much thought over how such an event could cause such a reaction from the public, I have come to a simple conclusion; it doesn’t matter where or how the crime was committed, but the fact that it was committed at all.

With the subject matter of real-world rape being one of complete seriousness it may be difficult for some people to take ‘virtual rape’ as anything despicable at all, more so of a ‘joke’ and something the avatar victims shouldn’t take to heart, but the clear fact is the users of that online game were a community and some thought themselves protected from such actions.

Some might liken the incident to that of a hacker breaking into someone else’s computer and stealing information about them; but of course that is accountable as a real-life crime. The real-world community involved with the cyberrape had to debate with the law as to whether such a thing could be counted as an actual crime; with that kind of social and moral examination becoming something that changed the future of not just that game but the people involved with its creation and its users.

Saturday, 19 February 2011

Introduction to Computer Gaming – Week Four – Design Elements

This week we focused on design, and the terminology used for certain aspects of gaming. Below I've identified and described some of these aspects in the two games I originally played and reviewed in my first blog.

Colossal Cave Adventure:
Style of competition: Single Player Competition (Player vs. Environment)
Positive Feedback: The player receives feedback in the form of the items/actions taken having a direct effect on what they can do later in the game (for example there may be a lamp in a room, and if they take it they will be able to use it later to light their way, which then it turn reduces their risk of death) and then, as they progress through the game the further they get the more chances they have to pick up valuable items.
Boundaries: As the game has no graphics, the boundaries are not ‘visible’ but rather told to the player; they appear to be on a map and cannot go beyond what the map has sketched out.

Possible Outcomes: There is definitely more than one outcome in a game like Colossal Cave Adventure, and although there is a set map-path, the player can chose multiple ways to make their way around it.
Recuperation: The Player often has large periods of exploration before having to deal with a particularly dangerous/challenging situation.
Ethical Constraints (morality): There doesn’t seem to me any particular morality in Colossal Cave Adventures (for example, the first time I played I killed a bird, that I’m pretty sure I was supposed to catch! But the game allowed me to find a way around problems like that later on)
Turn based or real time: Although I don’t think the game could really be classed as either, if I had to choose I’d swing for Turn-Based – the game gives the player endless time to decide on the next action and the player can also hold large amounts of resources at any time.
Main sources of Fun: Narrative, Challenge, Discovery
Internal economy of the game: The game places items around the game that the player must pick up – though if they forget they can go back and get them or find another way around a situation – although there is no specific drain on the resources there isn’t an abundance of resources either.


Level of Challenges: The difficultly never really increases or decreases, but there is a definite hint that you should think back to previous interactions you’ve taken in order to work out what the best move should be.


Conciseness: As the game has no graphics it can’t ‘show’ the player where they are, so instead it tells them; something some players might find boring, but it also sets the scene for the action, whilst also giving the player specific details that might have a direct correlation to an upcoming challenge.

Emergence: There are hints of emergent gameplay; for example there are ways a player can use an object in more ways than the game might be directing them to.
NetHack:
Style of competition: Single Player Competition (Player vs. Environment)
Positive Feedback: The player receives feedback in the form of levelling up, and items received for defeating in-game monsters.
Boundaries:  The boundaries include visible walls inside rooms, but also invisible walls when walking along the paths between rooms; keeping the player going from room to room.
Possible Outcomes: The game includes multiple paths/directions to take, not only in game, but with the choice of character/gender etc. that you pick out before you start playing.
Recuperation: The Player gets short periods of rest-bite, but due to the nature of the gameplay, and the ever-changing situation, the player can never be sure of how much time they will have to recuperate.

Ethical Constraints (morality): Net-Hack certainly has a direction to comply with the ‘plot’ of the game (more so than Colossal Cave Adventures) as the storyline is more complicated, and there is a stronger fantasy, RPG feel to it; though I have not played through the entire game so there may be later chances to ‘betray’ the storyline.
Turn based or real time: The game is certainly more Real time than Turn based, as the player can move constantly, and the in-game monsters move at their own pace.
Conciseness: The game doesn’t rely on description, and gives the player direct instructions/commands as they/in the moment they meet with the object of interaction; for example the moment they come in contact with a monster the game informs the player they just started a battle with said monster and let the player go on from there; informing them at each point of the battle what their actions are resulting to.

Level of Challenges: As the player levels up, the challenges in game also adjust to the new skill level of the player-character; leading the player to think more about their choices in battle and use of objects.

Sources of fun: Fellowship (with the kitten), challenge, fantasy
Internal economy of the game: The game allows the player to collect gold, along with other items within the game, which can then be used later, though there doesn’t seem to be any particular limit on the gold one character can handle there is certain a limit to the items one can collect (for example, if you miss an item to collect, you can’t always go back and collect the same item again). Also resources can be collected from battling monsters, though that involves risk of defeat/death.

Monday, 14 February 2011

Introduction to Computer Gaming – Week 2 - Extra Blog - Level Ideas & Beginnings of Design Document

After listening to some of my friends and their ideas for game levels I decided to start work designing my own and I first went about coming up with some sort of foundation to base my level on.

I have always been a big fan of the movie ‘The Labyrinth’ ; a 1986 Fantasy movie starring David Bowie and Jennifer Connelly. The basic plot of the film revolves around the young heroine, Sarah Williams having to solve a Labyrinth in order to get to the Goblin City to save her brother from Jareth, the Goblin King.

Through her journey through the labyrinth she comes across all sorts of puzzles and challenges she must face in order to move forward. As the requirements for the level include things such as puzzle-solving, with exploration elements I thought I might draw some inspiration from these aspects in the movie.

Below I’ve listed some of the ideas I’ve had that I’d like to include in my level.

Interactions:

-Doors hidden within walls (have portions of the wall that the played is able to pass through, but with all the same material to make it appear ‘invisible’) : The gamer must push a number of switches in order to activate a ‘clue’ to the location of the passable part of the wall.

-Noise triggers in the ground to act as a clue to the right direction in which to go: as the gamer walks upon the invisible triggers they are activated and a sound will be played, directing the player through the labyrinth

- Riddle Doors (Two Doors, with a Riddle (user has to input the answer into the game – if it’s incorrect the wrong door opens and they go back to an earlier point in the game) -

-Trapdoor (section of the floor triggered so that once a gamer steps on in, the floor drops, leaving them on a new gaming platform)
-Stair-room – A room likened/influenced by the painting ‘Relativity’ by MC Escher (the gamer must work their way through the room of stairs in order to find their way out)

I also plan to set my game inside a labyrinth/maze, but rather than it being underground, I plan on using a ‘sky dome’ to create a feeling of it being outside.

The puzzles are subject to change; as some elements may not be completely possible to implement inside of UDK.

I’ve also started a rough draft of my Design Document, and have begun drawing some concept art and maps for my level as I plan on included a lot of graphics for reference.

Saturday, 12 February 2011

Introduction to Computer Gaming – Week Three – KISMET

This week we covered the basics of KISMET and how to use it in order to implement certain interactions within our game level.

My possible KISMET interactions include things like: switches to open doors, noise triggers, trapdoors, condition doors (doors that open once a certain condition is met by the gamer)

KISMET use often consists to a lot of trial by error when trying to implement interactions (especially when you may be trying new, or combining different interactions together) and although most of the fundamentals of using KISMET for interactions such a user inputs, and animation of objects were covered, there are definitely certain aspects of my puzzles that will require a little more research and practise to implement.

For example, noise triggers would be very similar to things like auto-opening doors; a small collision box would be placed on a part of the floor, so that once the gamers comes into contact with it, the game goes on to the next action, which in this case would be to play a sound (something I shall have to download and input into the program) instead of opening a door.

Other interactions like trapdoors may be harder to create, as although we covered the subject of lifts, a trapdoor varies greatly, as instead of the user pressing a switch or standing on a patch of floor that rises slowly, a trapdoor would have to drop instantly upon the gamer coming into contact with it.

Also, I want to make my game very much about the exploration of the area, and allow the gamer to try and work out the correct path through a series of small puzzles and clues that I will input into the game; so not all of my chosen ‘interactions’ may require extensive KISMET use, although the ones that do will most certainly need further research into how KISMET works and what the tool is capable of.

So, in order to start the process, I’ve given myself the job of looking into what I can personally implement with KISMET and what I may need to change in order to make the game better for both me as a designer and the gamers; with how they would want the interactions to work and how they’d want them to feel within the game.

Friday, 4 February 2011

Introduction to Computer Gaming - Week Two - Design Documents

Q1. Why do you think there is so much variation in the structure of each design document?

A1. A design document is fundamentally unique to the designer themselves and what game elements they want to showcase. For example, if the game has a weaker plot line but is strong visually, the designer may want to highlight this point; including documentation of the environment (drawings, screen shots, character designs), and perhaps only touching briefly on the plot line. Of course, there could be an opposite to this; perhaps the game has a low budget or is going to be run on a weaker gaming system and thus is unable to run heavy graphics; in this case the designer might want to draw attention to what they have done to make up for this in terms of story, character interactions and gaming experience.


Q2. How much technical information is contained within the design documents? Would a programmer be able to pick up any of these design documents and create the gameplay based on only the information presented within the design document?

A2. The design documents contain an astonishing amount of information; including menu designs,  cheat codes, player communications with instructions/interactions, how the game should react to certain inputs (and sometimes if no input occurs at all).
Although a programmer perhaps may be able to create the game described in the design document, the gameplay itself is something altogether different. The gameplay should be something unique, at least in feel, for every game; and no doubt the designers’ intend this. The programmer themselves cannot completely understand what the designer wants in terms of atmosphere and how they want the player to feel/interact with the games elements. For example, perhaps the designer wants the player to feel particularly uneasy on a certain level, using dim lights, sound triggers, extra shadows and maybe even very specific details like rain pattering upon the windows; with the player avatar being made very aware of these things with interactions/drawn vision. These small details are perhaps too specific to be included in a design document, thus the programmer’s creation may feel bare and be a somewhat incomplete experience.

Q3. Discuss a few good points about these example documents, and then identify a few areas which you would improve in your own design document. For example, you may want to reduce some of the long paragraphs of text in some documents and present that same information as a bullet list to make the information more accessible.

A3.
I particularly liked Grim Fandango and the style of design document used; the heavy graphics – though not computer generated, but rather sketches were lovely to view and gave me, as a reader, a greater idea of what kind of atmosphere and feel the designer means for the game to have.  The plot and interaction descriptions are also amazingly rich in character – almost as if they are a story.

The maps used in Technomancy were also brilliantly realised, and the level of detail used for them allowed me to imagine the gameplay that bit better and how the player would advance through the level/s.

The Claw on the other hand relies heavily on the technical components and contains absolutely no graphics; giving the reader a large dose of practical information on the system specifications and user interaction/instructions.

All of these design documents have things that uniquely give the reader something special to lock on to, though these points can also be their downfall; relying too much on information and specs, and not on story, experience and gameplay (ultimately why a gamer would want to purchase the product) could leave the reader feeling no real passion for the game itself. The opposite can be said for design documents that use heavy graphics and no real information at all could give the wrong impression to a reader; that the designer, although confident in how the game should feel/look, hasn’t thought about basic foundations of how the game will run and what it should include technically.

Within my own design document, I would want to draw inspiration from Grim Fandango, and use graphical pieces to convey the design, but also including enough information, so that the reader can understand the more technical aspects; though I would aim to keep these simple so as not to weigh the reader down with unnecessary information.