Buy a composition notebook or keep an electronic document label it with your Project Codename.
This is your Project Notebook or Portfolio. Your Project Notebook is your life. Take it with you everywhere you go. You never know when a brainstorm, idea, question, or fundamental design flaw will pop into your mind. Document everything that you think of, especially the problems you don't know how to solve. You'll be surprised how often an insurmountable problem is a trivial matter to solve just a few days down the road. You'll hear or see something that will click in your head and "Whoomp!" there it is. Keep your Notebook nearby when you are playing competing products and take notes. Go somewhere where you can be alone with your game for a period of time without distractions.
A) Project Code Name - Every game has a codename to designate it during production. This usually isn't what the game is finally named on release, marketing people love to change names at will.
B) General Description - This is a general overview of the game, what it's like, how it works, what happens on each level, etc. We start with the original Game IDEA, then fill in the blanks enough that anyone reading it will know what we are talking about.
C) Screen Description and User Interface Specification - What screens do we need for the game, what will they look like, How will they work, how will the player interact with them and what feedback systems will be available to let the player know his status. Each screen is treated individually and explained, including mock up screen shots wherever possible.
D) Art Specification - What graphics elements do we need? What Characters do we need, what personality traits do we need to show in the art, how big are they, what animations do they need, etc.? What do the graphics screens look like, and how big, number of colors? What kind of font do we need? How big, colors, etc. What WORD graphics do we need
E) Sound and Music Specification - What kinds of sound effects do we need? Intro and\or Intermission music? What file formats will we support? How are we going to do sound?
F) Paradigm Specification - How are we going to do this project? What approach will we take? What functions and procedures do we need? What information will they need? In what order do we draw the sprites? How often do we update the feedback screens? Speed controls? Once we answer these kinds of questions, we flowchart the game from the player starting, through all the options screens, to playing the game, what happens each animation frame in order, how we end the game, how we restart the game or leave the program.
This material may consist of step-by-step explanations on how to solve a problem or examples of proper writing, including the use of citations, references, bibliographies, and formatting. This material is made available for the sole purpose of studying and learning - misuse is strictly forbidden.
var canvas = document.getElementById("myCanvas");
var ctx = canvas.getContext("2d");
ctx.imageSmoothingEnabled = false;
var x = canvas.width/2;
var y = canvas.height-30;
var dx = 2;
var dy = -2;
var ballRadius = 4;
var fireBallRadius = 2;
var paddleHeight = 40;
var paddleWidth = 60;
var paddleX = (canvas.width-paddleWidth)/2;
var numEnemies = 50;
var enemyHeight = 30;
var enemyWidth = 50;
var health = 3;
var rightPressed = false;
var leftPressed = false;
var spacePressed = false;
var hasPaused = false;
var enemies = ;
var playerFire = ;
var enemyFire = ;
var totalEnemies = 0;
var activeEnemies = ;
var totalKillded = 0;
var hasSetupEnemies = false;
var gameOver = false;
var bgDrawn = false;
var score = 0;
var playerHealth = 3;...
This is only a preview of the solution. Please use the purchase button to see the entire solution