Scribd
Upload
20 views2 pages

Assignment 4.1

Uploaded by

Cristi Damian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
20 views2 pages

Assignment 4.1

Uploaded by

Cristi Damian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

ASSIGNMENT 4.

1: MORE THAN A MECHANIC (IMPROVE YOUR PROTOTYPE)

Suggested Due Date: 6/1/16, 11:59 PM

You should be starting from a playable, but incomplete, prototype. This week�s goal
is to create a complete prototype, one that has all the key parts of a game. Focus
on getting more components into your game that you want and need: player actions,
game actions, goals and conditions, ways to win and ways to lose. Next week, you
can concentrate on balance and polish.

Do you still LOVE your game concept? If not, change it until you do. What about
your goals? If these have changed, make sure your work this week reflects that. You
have a core mechanic; now it�s time to envision it as part of a system:

Consider how the game might start (i.e. a starting state) and also how it might
end.
What about goals for the player to achieve or strive for? The timing and number of
these goals will shape gameplay.
In order to reach goals, the player (or players) will need to perform actions.
Determine what these might look like.
Think about obstacles for the player to overcome.
First, think about the bullet points above and make some notes. Don�t even start
prototyping yet; instead strategize for your iteration. Do not feel that your next
prototype has to reflect all of your decisions. Keep it simple and build your game
incrementally.

Are you still dealing with problems from your last testing session? Try altering
your rules, rather than adding more. Novice game designers frequently reach for
more rules, more mechanics, when they find problems. A better solution is usually
to simplify your game instead. Tackle problems with these experiments first:

Amplify features: Double it! Halve it! Big changes help you understand what is
going on.
Can you remove a rule to make it better?
Can you simplify a rule to make it better?
Take a break for reflection. Think about your process so far. What is going well
about your design process? What is challenging?

At this point, it�s important to make sure your game is working before you bring in
new testers. Play your game! Play it with friends or play it by yourself.

For the deliverable: The format is up to you, but keep it brief.

Tell us about major changes you made this week. Explain how your game has evolved
as a system. Comment on start and end states, etc.
Include a set of instructions and how to set up and run your current prototype, as
well as the player rules.
Include at least one picture of your prototype in play.
Comment on your process so far.
Guidance for Peer Feedback:

Provide feedback to at least two participants who posted just before you (their
posts will be just below yours). If those participants have already received
feedback, look for participants who have not received any. Follow the Peer Review
Feedback guidelines and consider the following:

Consider the changes that the participant described. Is there one that is
particularly interesting? What is interesting about it? Does this change influence
your own thoughts regarding your game?
Does the participant's process sound similar to yours? Compare it to your own
process.
Is there one aspect of the prototype where you can offer suggestions for
improvement?

You might also like