SavisArmador / Game-Concept-Notes

0 stars 0 forks source link

Recipe for our Game! #7

Open SavisArmador opened 8 years ago

SavisArmador commented 8 years ago

A Recipe for a Successful Game

Main Ingredients: 3 cups water 3 cups programming 3-8 original gameplay mechanics, uncut 1 render farm-fresh art asset bundle OR 1 hand-drawn art asset bundle 1 soundtrack, well made 1 enthusiastic community (Optional, recommended)

Preheat dev team to 260 days a year, or 365 if you’re behind time.

To make the base, combine three cups of water with three cups of programming. Even cheaper store brands should work, as long as they are not inefficient or infested with bugs such as TsetCTD (Crash To Desktop) Flies, or OpenGL Moths. (A distant, ugly relative of the Meal Moth)

Mix the two until a firm dough is achieved. This dough makes up the base that we season and flavor.

After a 5 minute pre-bake to kill any bugs that may be hiding in the base, begin to coat with original gameplay mechanics, to taste.

Next, prepare the presentation. The most important step of presentation is to blend the soundtrack to a smooth, workable consistency, and spread it evenly throughout the game.

Once the soundtrack has settled, add your visual flavor, a garnish of 3D or 2D graphics, all made to a distinct style.

Return game to dev team, and bake for an hour and a half to properly bond elements together, and ensure as few bugs remain as possible.

Let the game cool during a 15-minute bug-checking period, removing any you find. Then, serve hot, preferably to an existing community.

A popular variant in some cultures, known as “Early Access,” is based around serving the game without the bug-testing period or even served with the community inside the oven, consuming it as it still bakes. Many fans of this style claim that the remaining bugs add “flavor,” and that by helping to remove then, the community is enhanced with a sense of contribution.