{"id":2396,"date":"2017-11-03T02:20:09","date_gmt":"2017-11-03T02:20:09","guid":{"rendered":"http:\/\/mycours.es\/gamedesign2017\/?page_id=2396"},"modified":"2017-11-03T03:02:23","modified_gmt":"2017-11-03T03:02:23","slug":"game-design-vocabulary-ii","status":"publish","type":"page","link":"http:\/\/mycours.es\/gamedesign2017\/presentations\/game-design-vocabulary-ii\/","title":{"rendered":"Game Design Vocabulary II"},"content":{"rendered":"

Let’s introduce more terms as we workshop the next steps<\/p>\n

Prototype<\/h1>\n

\"\"
\n-A game prototype is not a finished product but a dynamic, computational “sketch” of your game, a proof of concept.
\n-Prototypes are usually developed with the fastest techniques: paper or accessible tools like processing or flash.
\n-Because of that, prototypes are typically thrown away even if they are successful. The development starts from scratch.
\n-Prototypes use placeholder assets, concept art can be done separately to set a style and visual\/polish goal
\n-Most prototype fail: turn out to not be good or feasible ideas or don’t generate the desired dynamics (fun or else). And that is not a problem.<\/p>\n

Feedback and collaboration is not always useful in prototyping:<\/strong>
\n\"\"
\n*From How to Prototype a Game in Under 7 Days
\n<\/a><\/p>\n

From a good prototype you should be able to tell:<\/strong>
\n * Can the player make meaningful decisions?
\n * Is the player getting the feedback they require to make good decisions?
\n * Are the major risk \/ reward schedules in place?
\n * What is the pacing of the experience?
\n * Is there enough meat here to hang the rest of the game on?
\nFrom Common game prototyping pitfalls<\/a><\/p>\n