Developer Blog – VR Design Document Part 3

By | May 24, 2016

While a good deal of this post remains redacted, it should still serve its purpose as a sample design document. All will be revealed in due time!

III. Narrative Synopsis
Shoot stuff and avoid being shot.

III. Game Mechanics
“Space Blast” is a mobile VR [redacted for the time being]. The game is played [redacted for the time being]. The player takes the role of a transformable space mech with two modes: spaceship and robot. [redacted for the time being]. [redacted for the time being] [redacted for the time being]. The objective is to attain a high-score; iterations might involve allowing the player to choose to fight an end boss.

In this example the Game Mechanics introduction reiterates the Gameplay Synopsis. It is more specific in a few instances however.

1.Gameplay Mechanics; Core Version
Player:

  • The player pilots a maneuverable spaceship [redacted for the time being], [redacted for the time being] mech [redacted for the time being].
  •  [redacted for the time being]
  • Both modes are navigated using the lowest common denominator brand of bluetooth controller.
  • The player must navigate [redacted for the time being]

At first glance these mechanics may seem to obey the “start small and make it smaller” indie edict. In reality this list is fairly ambitious and may need to be trimmed. A transforming spaceship means an additional mech model, [redacted for the time being], and animations. It also means additional FSMs. The [redacted for the time being] feature will require additional study and implementation. On the plus (minus?) side, [redacted for the time being] necessitates lots less art assets in exchange for a modicum of FSM work. We’ll need some fairly involved random generators however.

Enemy:

  • Low poly, four or fewer types
  • The A type will “hover” in front of the player, match his/her speed, and fire.
  • The B type are kamikaze and will fly straight at the player.
  • The C type will overtake the player while firing.
  • The D type will be terrestrial.

In space, no one needs to pathfind. Each enemy will simply fly in a straight line; only their speed and direction will vary (according to type). Iterations beyond the MVP should involve assigning enemies unique weapons, hitpoints, and savvier AI.


A Note from Admin:


I hope you found this content useful. If so, please like and subscribe and consider contributing to

so that I can continue to produce great #gamedev and #game art content while battling cancer!

Subscribe and get ahead with the latest tech recommendations, tricks, and tutorials!

Or subscribe to:
NCP on Twitch
NCP on YouTube
NCP on Twitter (warning: politics!)

WIP Sites:
learnindiedev.com Unlike Udemy, this site will feature live lessons and game jam learn-a-thons (exactly what it sounds like)! Featuring No-Code Video Game Development, the only video course to become a published text book!

openforcommissions.com Why be hard to find? Upload your portfolio, change your open/close status with a single tweet, get paid!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.