fco / jsgames Goto Github PK

Create abstraction for lives

• Use requestAnimationFrame to optimize animation proccess;
• Create abstraction for graphical modes;
• Add WebGL support as graphical mode (ThreeJS) to improve graphics and performance.

Create a "power up" that gives us an extra life.

needs #11
Implement more lives

Implement a way to pause the game

Probably using websocket

Create a "screen" where we can configure the game. Like: what power ups it should use

If you click the mouse button (or press space) the bar should go up in a big velocity, if it hit a ball while going up, it should go back down and the ball should get faster. If it doesn't hit any ball it should stay "uped" and going down in a slow time

Implement abstraction for Power Ups

When the ball touch the bar it will be glue until the next mouse or space click.

Create abstraction for levels

needs #13
Create abstraction for local ranking (localstorage)

Create power-up to bring extra balls (at least one more) to the scene. Increase balls velocity, but normalize when just one ball left.

The bar can shoot per 10 seconds;
The next shoot can only be fired after the actual one is destroyed;

Something like:
Some files for stages, as the following example:

-- stage1.stg
### ### ### ### ###
### @@@ @@@ @@@ ###
### ### ### ### ###

Those files would describe how blocks should be laid out on the stage. Each three character combination is the code for a different block that should also be specified on a separate file, as in the following example:

//RegularBlock.js
exports.symbol = "###";
exports.type = "Poligon";
exports.transform = function (block) {
        block.draw_colision_area      = false;
        block.solid                   = true;
        block.do_not_colide_with      = ["Border"];
        block.type                    = "Block";
        block.color                   = "#000000";
        block.add_vertice(-13, 0);
        block.add_vertice(12, 0);
        block.add_vertice(12, 15);
        block.add_vertice(-13, 15);
        block.going2destroy = going2destroy;
        block.on_colide_with("ball", function(bola) {});
};

And that should be enough to load the stages.

Remove the Blocks class from brickbreaker.js and create a file for it.
Make the constructor search for all brick files instead of sending it for it

needs #13
Implement a multiuser ranking abstraction

needs #14
Implement a server for centralize the ranking

Create interface for ranking

needs #10
Implement more levels

Use sprite on objects

Create power-up to turn the ball unstoppable temporally:

• Ball can only collide with scene limits;
• Ball still can hit bricks but do not collide to them;
• Ball is unstoppable during a few seconds.

on death it shouldn't restart the level, only reset the ball
on finish lives should restar the level

needs #12