Monday, 28 April 2014

Sketchup: The main images used in the Flash file

Here are the screenshots from my Google Sketchup which I used as reference when creating my room in Flash. These images can also be found in the Flash file itself.

This also includes the panoramic view I created using several printscreens of the sketchup file.











Distribution: Title, Thumbnails, Description and Controls

From writing my evaluation and covering the distribution I've decided to create the content which would be produced when distributing the game to the various different Flash Gaming websites.

Title
[No character limit] How I Escaped - The Waiting Room
[25 character limit] HIE - The Waiting Room / Escape: The Waiting Room

Thumbnails [Standard Sizes]

[140x90]
[250x200]


 Description

Are you ready for the first in the series of How I Escaped? Great! Then your first room will be the Waiting Room. Forget all the arbitrary room escape games you've been playing, you're dealing with the big dogs now. Point and click through your surroundings to find clues which will not only help you escape the room but discover the story as to why you are there too! If you manage to escape from this room, you'll be good as gold to escape from a room in real life.

Controls

Mouse [Left Click] and Keyboard [Typing].

Important Downloads: Font and Google Sketchup


Grizzly BT font is available for download for free here

Google Sketchup is also available for download for free here

How I Escaped - The Wating Room is available to for download here
 

It is recommended that you download the Grizzly BT font when viewing the FLA file directly.

Sunday, 27 April 2014

Evaluation: Audiences, Distribution and Cultural Context

For my artefact, I have created a Room Escape game. Usually, Room Escape games are likely to be either found as a browser based or as a mobile device game. I had chosen to go for the browser based game. In comparison to other browser based games I believe that Room Escape game definitely fits very well for the intended delivery platform. For this Evaluation I will be looking at the Audiences, Distribution / Delivery and Cultural Contexts / Genre. Overall this will cover the ludology of Flash games.

Audiences
As a whole I believe my game would be suitable for it's intended audience of age 13 and up. The intended primary audience for my game would have played room escape games before and are likely to have completed a few. With that being the case, I feel as though my room escape game should not be a problem for these users and they should be able to complete it in a suitable time of around 10 minutes. The secondary type of audience would be those who are browsing gaming websites such as Newgrounds and are finding games to play for fun. From doing my user testing, I've found that even these types of audiences do not struggle to complete my game. The concept of point and click would be easy to grasp for both intended audiences.

Distribution / Delivery
As my game has been exported as a SWF file this means that the game can be distributed across to many online gaming websites. The SWF format is widely accepted and many websites allow this type of submission. My game would be easy to distribute onto gaming websites and this process would typically involve creating an account with the companies website and submitting the game through their database. Although not a necessity, some authors may also choose to add adverts to their games before distribution has taken place. Due to the layout of my game, adverts would be easy to implement and would merely involve shifting frames to the right so that there is room for the advert [to display at the beginning]. Quality control is often used to ensure that games distributed to their sites are of good quality. This is normally done through a rating system as judge by the website's users. Due to the level of professionalism my artefact brings, the distribute of my game should not be of a problem, even with the quality control algorithms on these websites.

Cultural Contexts / Genre
Room Escape games have become very popular on the internet and has it's own genre. In comparison with other room escape games, my one "How I Escaped - The Waiting Room" fairs very well.
The duration it takes to complete my game, as found from using testing, takes 5-30 minutes on their first go. This in comparison to the other room escape games of that length is very similar.
I'm happy with how the visual of my game has turned out, for being vector drawn it hasn't turned out too much like a cartoon and that is mainly because there are not black lines outlining the objects. All types of art styles are suitable for Room Escape games, including photo realistic and simply just vector drawn, so in this regards my room escape game meets it's cultural contexts.
A negative point of my game could be that it did not have any instructions on how to play it, but many room escape games - such as Crimson Room - typically do not have instructions for the game but instead assume that the users would have the vernacular computer knowledge for these types of games. As these games would already be in the category of Room Escape, it would therefore be obvious what the user must do. From the beginning, as mentioned in this post, I made it my goal to make sure that the users challenge should be to figure out the puzzle, not figure out how to figure out the puzzle. I believe that with the title, genre and targeted audience, in game features such as the narration, side arrows and roll over arrows it would be clear enough for the user on how to navigate through the room without instructions.
Many room escape games nowadays have very arbitrary which have irrelevant number colour puzzles involved which you have to figure out in order to escape the room. This wasn't something I wanted to do, even if it would mean breaking the cultural contexts of how these games work. I wanted to make sure that the items and clues the users finds would be involved within the environment and to make sure that these are relevant for the user to escape. I feel as though I have done this very well and hope that more room escape games would take this approach.

Overall I believe that the Audience, Distribution and Cultural Contexts have all been met to the standards that I had originally hoped for. The artefact make not come off as being professional when compared to industry standard work, but that's not what I was going for. The various different room escape games are not always going to be professional and are often made in the developers spare time. I believe that my game is up to par with the other Flash made room escape games and in that regards, it is professional.

The Finished Game && Previous Versions [Download avaliable]


Throughout the course of making the game there have been sudden script / art changes which has resorted in me naming the files as new versions.

Each of these versions have been uploaded to the Newgrounds Dump for your access.

The Waiting Room [Final]
The game with music, sound effects and narration as well as some various other features changed.

The Waiting Room [V2]
The game was completed and had a different inventory system script.

The Waiting Room [V1]
 This included the main appearance of my game, but only allowed the user to pick up one item.

The Waiting Room [Prototype]
This was created to get a rough idea on how I would script the inventory.

Saturday, 26 April 2014

Working Processes: Finishing The Game - Adding the Narration & Sound Effects, Cut Scene, Window contents, MOUSE_LEAVE and backToMainFromVending

Since I manged to get the sound for the narration of "It's locked" I decided to add the other narration clips as well as the sound effects.

To do this, I went back into Audacity and selected the narration clips I wanted and exported them individually.


I then imported them into Flash.

The main difference between the scripts for the narration and sound effects was that the sound effect scripts wasn't as advanced, this was because I did not need to make sure they would overlap. In fact, if they overlapped that would be even better.

The script, as mentioned in previous posts, for the narration looked like this:

if(narrateChannel!=narrateItsLocked){
narrateChannel=whatsThat.play(0,0,narrateTrans);
}

whilst the sound effect script would be much simpler and only look like this

soundFXChannel=soundFXFuseDoorOpen.play(120,0,soundFXTrans);

As I didn't create the sound effects, it meant that some sounds didn't start at the part I wished them to start. Instead of editing each sound in Audacity and re-exporting them. I instead used script to make sure they started in the right place.

The first number in the brackets affected where the sound would start whilst the second number affected how many times it would repeat. As I didn't need the sound to repeat, like I did for the music, I kept the number at 0.

I put the priority on the sound effects as I felt they were more important than the narration at this stage. After I had finished with the sound effects, I moved onto importing the rest of the narration.

When testing the game, I noticed that the narration could get a little annoying if they were repeated when doing the same actions. I put in booleans to registered if the sound had been used before, and made it so that when the booleans were true, the sound would no longer play. Some narrations, mainly the important ones, weren't limited with booleans as I felt it was important for the user to hear them again.

In the end, I didn't end up using all the narrations I had scripted. Too much narration would turn out to be bad and take the user away from the experience. I used narration where I felt it was necessary. Such as trying to read a note without enough light. Or trying to read the notebook without your glasses. This way the narration would let the user know that something wasn't right and had to be changed.

The majority of sound effects were obtained from http://www.freesfx.co.uk/
This was a really good website and contained sounds for nearly everything I wanted apart from the vending machine noise and a few others. A more detailed version of the sources can be found in my bibliography.

I then went onto the cutscene. This was very enjoyable to create. I took the viewMain frame and converter it all into a single movieclip. I then animated it with a tweet going left and right and back to the centre. I set the tweet to ease 100 so that it would look much smoother.

Since the protagonist had just woken up, I wanted to animate the eyes opening. I created a rectangle which filled the whole stage and used the select tool to curve the line upwards like an eyelid. I then tweened the eyelid upwards to imply that the protagonist had just opened their eyes. I selected the movieclip which contained the room and tween blurred it so that it only once the eyes were opened that it would be unblurred.

I then added the narration of "Where am I - I need to get out of here" onto frame 17 and then cutscene was finished. I made the Enter Name frame direct to the cutscene instead of the game, and I instead made the cutscene direct to the game after it had finished.

I then worked on the window. This was something which was referred to as many things in the user testing. Such as a widescreen TV or a blackboard. So I wanted to make sure it actually looked like a window.

I first took a picture with my camera mobile phone and cropped the image. I then imported this into Flash.


Instead of tracing around the image, I broke the image with ctrl+b. By doing so it meant that the image could now be trimmed in Flash.

I selected the Magic Wand tool, located in the Lasso Tool options and selected the sky. It selected the whole sky and I hit del on the keyboard.

I then turned the image into a silhouette by filling the rest of it in black, which was possible as I had already broken the image.


Afterwards I then went to the in game window and deleted the contents. In a new layer I placed this silhouette and used the Disort tool, located in the Free Transform Tool, to give it the right aspect.

After this had been done, I gave the background a gradient between Dark Grey and Orange.

I was very happy with the results:


I noticed, just like my supervisor had said, that the mouse didn't disappear once the mouse had left the stage. Instead the mouse, as a movieclip, would stay where it was just before the mouse had left.
As this was the case, I wanted to create a script which would make it so that the mouse would leave when not on the stage and come back when the mouse moved on the stage. This was a rather simple thing to accomplish.

 My script looked like the following:

stage.addEventListener(Event.MOUSE_LEAVE, cursorHide);
stage.addEventListener(MouseEvent.MOUSE_MOVE, cursorFollow);

function cursorHide(evt:Event):void {
    if(cursor_mc.visible==true){
        cursor_mc.visible=false;
    }
}
function cursorFollow(evt:Event):void {
    cursor_mc.visible=true;
}

This worked great; but as expected, when the user would pick up an item a glitch would occur. This was because when an item is picked up the cursor would go invisible and instead of dragging the cursor, they would drag the item.

To solve this issue, I removed the eventListener on the start drag of an item and added it back on the stop drag of an item. This fixed the issue and it worked flawlessly.

There was now one more thing to change and that was one of the back buttons. As the vending machine is accessible from both the desk and the main view, when on the vending machine, I wanted it so that it would go back to the last view you were on instead of straight back to the main view. In order to do this, I created a boolean called backToMainFromVending.

backToMainFromVending was placed on the main view and set to true, the boolean was also placed on the desk and set to false. This way, I could add an if statement which would know where it was last time and take take the user back there. The script I coded was the following:

back_btn.addEventListener(MouseEvent.CLICK,backtoMainXRightListener);
backSide_btns.addEventListener(MouseEvent.CLICK,backtoMainXRightListener);
function backtoMainXRightListener(ev:MouseEvent):void {
    if (!backToMainFromVending) {
        trace("viewTable from Vending"+backToMainFromVending);
        gotoAndStop("viewTable");
        back_btn.removeEventListener(MouseEvent.CLICK,backtoMainXRightListener);
        backSide_btns.removeEventListener(MouseEvent.CLICK,backtoMainXRightListener);
        stage.removeEventListener(Event.ENTER_FRAME, receiptHitVNumbersListener);
    }
 else if (backToMainFromVending){
        trace("viewMain from Vending"+backToMainFromVending);
        gotoAndStop("viewMain");
        roomView.x=-605.25;
        back_btn.removeEventListener(MouseEvent.CLICK,backtoMainXRightListener);
        backSide_btns.removeEventListener(MouseEvent.CLICK,backtoMainXRightListener);
        stage.removeEventListener(Event.ENTER_FRAME, receiptHitVNumbersListener);
    }
}

I added this script to the viewVending layer.

Friday, 25 April 2014

Working Processes / Planning - Feedback from User Testing [6]

I user tested my game again to see what time it would take them to complete it.
This user took 14 minutes to complete the game.

So far the times taken to complete the game are as follows:

12 minutes
14 minutes
7 minutes
13 minutes
14 minutes
7 minutes
28 minutes
18 minutes
14 minutes

The average time taken to complete the game is now:  14 minutes. Brilliant!