{"id":135,"date":"2019-01-16T21:24:05","date_gmt":"2019-01-16T21:24:05","guid":{"rendered":"http:\/\/mycours.es\/gamestudio2019\/?page_id=135"},"modified":"2025-04-08T12:08:05","modified_gmt":"2025-04-08T12:08:05","slug":"prototyping","status":"publish","type":"page","link":"https:\/\/mycours.es\/egd\/prototyping\/","title":{"rendered":"Prototyping"},"content":{"rendered":"

\"\"<\/p>\n

What is a prototype?<\/h1>\n

-A game prototype is not a finished product but a dynamic, computational “sketch” of your game, a proof of concept.<\/p>\n

-Prototypes are usually developed with the fastest techniques: paper, accessible editors, pre-existing engines, “fast loop” game engines like Unity.<\/p>\n

-Because of that, prototypes in the industry are typically thrown away, even if they are successful. The actual development starts from scratch.<\/p>\n

-Prototypes use placeholder assets. Concept art can be done separately to set a style and visual\/polish goal.<\/p>\n

-Most prototype fail: turn out to not be good or feasible ideas or don’t generate the desired dynamics (fun or else). That is not a problem.<\/p>\n

Why prototyping?<\/h1>\n

The reasons for building a prototype are varied. Here are some examples:<\/p>\n

> To have a finished game at the end of a fixed time, such as in a game jam<\/h3>\n

Indie games that started in a jam<\/p>\n

\u00a0<\/strong>The concept can be stated in one sentence: a FPS in which time progresses only when you move.<\/p>\n