September 2010 Archives

Unit Two: "Rebellion Run: The Start"

Review of 2 Interactive Fiction games

The first game I played is my favorite: Lost Pig. From this game, I want to take the ability to wake-up a character (the sleeping gnome) and the idea of escaping a place with another character. Grunk has to find the pig in the beginning, but he ends up needing to escape the underground cave with the pig.

The HitchHiker's Guide to the Galaxy Game was fun to play and the other game I took ideas from. Though I didn't get all the way through, I was happy to recognize familiar events and plot. It inspired me to create my own game after a story I started. This, however, I found is not helpful to other players (as they haven't read my story). Items would have descriptions that progressed the story, but didn't much affect the game if you already knew the story plot.

Setting and tone of your game

The setting of my game is an underground government building in an alternate future. At first the game was supposed to be a serious escape with some romance thrown in. Then, it had to change to a short comedy and romance because of limited time.

Influences (what factors influenced your choices)

I wasn't able to make the whole escape idea so I shortened and changed the game to a comedy/romance that takes place in four rooms. There were also some coding problems that stopped me from making the game too complicated.

For example, I wanted to lock doors. I couldn't do it so I just got rid of those rooms and worked within a single room. I also wanted to have descriptions of a room change when you enter at different points. Maddie Gillespie helped me a little bit with making scenes and moving other characters to other rooms. In other cases, I tried to work around the description by making some things scenery or objects with different options (unused, used/asleep, awake).

Opening

My opening screen is mysterious to set the tone and setting. It tells you that there isn't something right about place that the characters live. The dialogue is between two characters you never meet.

If the player figures out to turn on and off the TV, they learn more about this weird place. Examining other objects like the fridge, bed, or mirror will tell you more.

There is a ringing you have to stop in the beginning. Thanks to Dr. Jerz, the ringing will continue until you find the phone and pick it up. This motivates the PC with a clear objective. Other creative factors include limiting the actions like waking up another character until the phone is taken care of.

Code

I made the coding for cut scene myself. That was my first real accomplishment. I added a "say" to happen after the "take" command. This cut scene also only happens once.

The coding I am most proud of is the "flush" command. I made the "flush" command from scratch (using only the Inform Guide) and put limits on it so that you cannot flush anything, but the toilet. Also, so that flushing at different times produces different results.

After Jessie told me how to end the play, I created three different endings with points myself. This programming was actually easy because by this point I understood the mechanics a bit better. I'm proud of this accomplishment because near the middle of my coding (a few days in) I didn't even know how I would finish the game in time or what the ending would be. Now I have three suitable endings with a variety of points.

Main Body

After the player picks up the phone, I rewarded the player with a cut scene/change in action. There is a crash that happens during the play. The player goes to the scene of the crash and is able to converse with the other character now. I learned to give and to ask other characters things thanks to Jessie Krehlik.

Some descriptions have also changed and there are less restrictions to actions.

I didn't figure out how to make the points earned show up earlier than the ending, that would have been more motivation.

Ending

I was able to create three endings. I wanted four, but I couldn't get the code to work. Once the other character enters another room, I wanted the game to end in so many turns. It ended up that, depending on the action of the PC, the story has two lose screens and one win screen. If the player misses the first action, they will not be able to win. Depending on which end screen you get, you can earn 10, 5, 0 points.

Credits

I primarily used the Inform 7 Recipie Book. A lot of coding help came from my professor Dr. Jerz and my classmates Jessie Krehlik (and her old blogs), Maddie Gillespie, and Megan Seigh.

Usability Test Report

First

The first tester took 20 minutes to complete the game. He needed some encouragement and tips on how to play Inform Seven. I gave him the card, but he still didn't know where to start or the what the command button was.

After he got the hang out it, it went rather smoothly with him examining most everything. From him I found that I needed a description of the faucet, the bedroom items (which didn't even exist), and to change some of the bedroom descriptions after the first cut scene. I added the descriptions, but I couldn't get the coding to work for the multiple descriptions for the bedroom items.

From his dallying near the end, I found he didn't know that Number 21 was a woman or that the FFPU was a fridge. For the next tester, I didn't further describe that 21 was a woman. I did spell out the FFPU the first time and put in the code to understand the acronym.

Second

The second tester had played IF before, but only for a short time. He knew the basic commands and it took him 16 minutes to complete the game. He actually found the win scene. The last tester had found the lose screen, but still earned 5 points.

I learned that when I had made changes after the first tester I messed up the constant ringing and some changing descriptions.

There was the same problem with Number 21 again. He knew it was a person, but didn't know the girl wasn't awake after they fell out of bed. This caused him to try to punch or kick 21. I changed the description of the 21 when the PC tries to wake her to something more obvious. "It seems the fall already did that for you."

I learned some new orders that I would implement if I had time. The tester tried to: set new orders on phone, call on phone, switch off phone, listen to 21 (when she's awake), talk to 21, show 21 the phone, give the phone, unplug the FFPU.

Third

The final tester hadn't played IF before, but new the story from what she'd read of my writing. It took her 25 minutes, but she knew to talk to the character after she woke up. From here, I found the last part always tripped up the testers, but it is supposed to be difficult.

The girl (other character) speaks in quotes/riddles. The testers eventually figured out what she needed (of which there are three options). I decided I would leave this the same. I found that only the last tester turned on or off the TV and didn't even get to the prompts.

Perhaps I should start with the TV off and have it turned on prompt an informational screen. I also found that when the TV is off the description of the living room is still "cartoons play in the background."

Other Students Unit 2 Projects

"...if you just put them in their jobs where they have their game face on. They won't really feel like they're all togeth- er in a common cause. You have to get them in other settings where they begin to see each other as humans, and when you do that, they're much more likely to behave well toward one another in the work setting."

About My First Scratch Game: "Late for Class"

The Games of Inspiration - Mad Libs and The Scratch Story of Hope D

Mad Libs is self-explanatory. Players entered words into questions asked. At end, answers were placed in a story that the player hadn't seen until the final scene.

Story of Hope D is a narrative that tells the story of how one user found Scratch, developed games, loved it, and created a story about it. Players click on a character that says "Next" to progress/read more

Mad Libs later faded in my mind, but I kept the idea of "chose your own" way. I found inspiration in Jessie Krehlik's maze. Krehlik's maze inspired me to create more levels that take my character in other directions. She had an idea of several levels and once you reach a target, it takes you to the next level.

I wanted to combine the two (Hope D and Krehlik's maze) into a story that had some interaction/maze-like qualities. The game turned out to be mostly a narration/story with minimal interaction because the complication of coding a maze was more than I was looking to tackle.

I followed Hope D's source code for the beginning in switching backgrounds and having the link to the story be my character. At the time, I didn't have source codes for the maze so I tinkered with the commands until I got the character to move properly in one direction.

Opening Scene - The opening screens have minimal instruction. The character says "Hello" and if that doesn't prod a click, she then says "Poke Me!" The text in the background tells the short story of character Africa who is late for class.

Section One - The player now moves the character to the school using the arrow keys. Each time you reach a door it takes you to the next level. Each completed level gets the character closer to class. The directions are simply: "Help Africa get to class." After clicking on the character doesn't work, testers always went for arrow keys.

Section Two - This level is a bit more challenging. The background has stairs going up or down. If the player chooses down (or the wrong direction in any other screen), the character says something like "Um...no" or "It's not time for lunch."

When the player goes up, I designed a block (with the help of Dr. Jerz) to follow the character up, blocking her torso so it looks like she walks up the stairs.

Section Three - Taking the upstairs will get you to the last task screen. This has encouraging words saying, "There's her classroom. You're so close." The door to the classroom is on the left and once the player touches the door, they get the win screen.

Win - The win screen has no win or lose appearance. The character is always late to class, but you get confetti for trying to help.

Lose - As mentioned before, if the player hits the wrong button, they are sent to the FAIL screen. It says "FAIL: This encourages the player to not fail so hard and so they try again.

Credits:

http://scratch.mit.edu/projects/HopeD/208289 - Scratch Story of Hope D

http://scratch.mit.edu/projects/funnyman1120/1177753 - Mad Libs

Jessie Krehlik and her maze

http://www.pennsylvaniamentor.org/campustour/undergraduate/660/Seton_Hill_University/Seton_Hill_University1.html - Seton Hill picture

Usability Testers - Jen, Brian, Katelyn

 Usability Report for "Late for Class":

Abstract

In testing my first scratch game, "Late for Class", I found the majority agreed that the directions were unclear and the game too short. Players also believed the game was intended for children because of its simplicity.

If I were to spend more time on the game, I would add two more levels after the second level so that the game was more challenging for a player. I would also make the game more maze-like, taking from Krehlik's code. For example, the player would have to avoid a piece of paper on the floor or the character would slip, like Krehlik's pawn who avoids the floaters for fear of starting over.

To solve directions, I would take out the "Poke Me" in the beginning and make the sequence timed to switch screens/backgrounds automatically, leaving the player to work only with arrow keys.

First tester: Jen, female, 20s

Took 1 minute to click the girl. After clicking twice (click stopped working), immediately went to arrow keys. After win screen, she tried again with same result. Then asked if it was over. Total playtime: 1.75 minutes

2 positives -

Amusing and relatable about being late

Told a story

2 negatives -

How quickly it ended

Not challenging - good and bad

Unclear instruction

Game was funny/fun: Agree on both

Game is finished: Disagree - needs more levels and directions screen

Directions are clear: Disagree - Don't know to click the girl to start.

What is age group?

Elementary

What can be improved?

Add more levels and detail to second level screen. Add directions page.

After this tester, I added words to the second level screen and added, "Poke Me" to the girl's salutations in the beginning. I also stopped the commands/arrow keys from firing the fail screen if the player wins.

Second Tester - Brian, male, 20s

Took 10 seconds to click the girl. After click stopped working, he tried to drag the character to the school. After 3 click/drags, he used arrow keys. Failed once, going down the stairs on second level. After win screen, he tried again as he asked if it was all. Total playtime: 1.5 minutes

What are three striking aspects of game?

Polite - gives you confetti so as not to kill your self-esteem

Tells a story

Graphics are fun, but childish

Short

Not difficult.

(The last 3 are negative.)

Game was funny/fun: Agree on fun, not funny. - There is one punch line at end

Game is finished: Disagree - needs length and instruction about where class is

Directions are clear: Disagree - Goes from clicking to arrow keys

What is age group?

5-10

What can be improved?

Pick either arrow keys or clicking. "I don't normally see both in games." Tell the location of the class at the beginning like second floor in such building. Add levels/make it longer. Make it like a maze where target can be seen, but it is difficult to reach.

I noticed that both parties guessed about the ending, not knowing it's a win screen. However, they did not list that as a negative or say it needed to be changed when asked. I changed the text for my last tester so that it reads "You win...Kinda" with further explanation and confetti.

Third tester - Katelyn, 19, female

Immediately poked/clicked the girl and went through the screens, but at first level with arrows took four click-and-drag-tries to then use arrow keys. Clicked the wrong arrow key on second level, but then clicked the appropriate key. The FAIL screen is late in coming up so it showed up on the last screen. Took the player three tries to realize this error. Total playtime: 2 minutes.

What are three striking aspects of game?

Fun speech bubbles

Lack of instructions

Fantastic Lab Coat

Game was funny/fun: Agree on fun

Game is finished: Disagree - (Kinda) There is no win, but it has all the parts. There could be more levels.

Directions are clear: Disagree

What is age group?

Elementary

What can be improved?

Give a clue on what to use (to move character).

In this test, I found the player did not ask if it was the end. She knew it ended. She did mention the not-so-win screen though. After this test, I changed the glitch with the late FAIL screen.

Conclusion

The directions are ruled unclear on every test even after changes. If given more time, I would take out the clicking and leave on arrow keys and test that before adding more direction.

I would also add more levels and make the game more challenging by adding more maze-like qualities.

See other game reports and portfolios on the class blog.

The Usability Testing Tips were mostly review because I took Writing for the Web my freshman year, but everyone needs to review. I had forgotten that I should ask questions that have a quantity (disagree strongly, disagree somewhat, agree, etc.) and to balance that with a short test.

This will be challenging because I want to know so much about different aspects of my game. However, this will not keep my volunteer's attention so I will have to test multiple people.

"Sequence Your Subjective Questions from General to Specific...By simply mentioning something in a question, you call attention to it."

I actually forgot about this part, but it is a good way to direct the test without focusing in on one spot too swiftly. I may be concerned about the direction of the characters, but if I ask first where they found problems with the game. The player may decide an issue with instructions was more important than the direction.

Later while writing questions:

I'm having a hard time making up questions that aren't opinion, but also aren't specific. I have two general questions so far:

"How would you improve this game?" and "List 3 postives/3 negatives of the game"

For EL405 New Media Projects, I am to develop a game using the tool Scratch. It's been a long process, but I decided on a text-based adventure game. I started with a character who is late to class and needs the players help to get there.

So far I have several scenes and costumes, but only two in which the player needs to click up or right. I plan to develop another interactive scene in which the player needs to click left.

At this point, if the player clicks up or right when they aren't supposed to, the game will take them to a "Fail" screen. If they make it past my preliminary levels, the gamer will get the "End" screen where they earn confetti.

My plan is to better develop the down and left buttons as actions and (if touched at the wrong time) will send the player to the "Fail" screen. I will use the "when player clicks down" then "broadcast fail." However, for "left" I will need to copy my previous directions which include: "when player clicks left" then 'if - touching color - else broadcast FAIL" then "switch costume" then the desired movement.

Note that I have a copied costume for each level. So that the character's look doesn't change, but if it's not the right costume number for the right screen, then she won't be running all over the place.

At this point, the buttons do nothing. I also need to do usability tests to see if my simple directions will be enough for a player to know when to click on the character and when to push an arrow key.

Difficulties I've had include getting the character to only move on the desired screen. I've solved this with the help of my professor Dr. Jerz and the "if/else" statement bars.

I also attempted to have confetti pop up, but when I succeeded I found it very static. Shelly Polly, classmate, helped me by suggesting the background be multiplied with different confetti and then switched back and forth to give the appearance of movement.

Another point of contention, I wanted the character to go behind the background I had set and appear to go up the steps. Dr. Jerz told me to design a box that appears in front of her, but blends into the background going the speed she goes. There was a lot of tweaking done there to get them both to move at the same incline, at the same time.