[Platformer Game Engine Series of releases?]

[GabrielBailey74]

I was thinking of creating a long series of releases of a 2D Platformer/RPG engine.
Advancing each update with newer things (Performance wise, bug wise, utility wise).

Things that would be in this for a example:

• GUI.
• Drawing Screen.
• Movement Handlers(KeyListeners, MouseListeners, your basic game movement to fit your ideas).
• Transparent Sprite loading.
• Great performance, catch everything with a risk of spoofing somewhere.
• Player class(health, positions, main variable class).
• Animation: sprite animation, npcs etc, water.
• Ability to place pre-loaded objects (sprites/buildings) on screen, than export, and be able to load everything drawn with 1 loader.
• Great debugging features!.

Everything that will be programmed in WILL have comments by it, so if you come across a method for example:

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18

/*     * Main call upon start (Initiates a loop for updating)     * #Update our FPS.     * #Draw our graphics.     * #Update our player.     * #Handle GameMapLoader cycle also.     * #listen for audio plays(boolean loop, int wait).     * #Call out performance class, clean up our space taken.     * #Restart the loop     */    public static void cycle() {       updateFps();       GMD.mainRender();       Entity.update();       GML.cycle();       MediaPlayer.listen(true, 200);       Performance.cleanUp();    }

Everything will be clearly explained, possibly some examples of the method if it's a bit long.

Main reason for this is that i'm new here, and I would like to bring something to this community (while teaching myself along the way).
But I have seen a couple posts relating to 'newby tutorials', id like to be able to see someone reply:

Yeah check this post :link:, pre-created Game Engine that's really easy to use/modify/distribute.

I would like to see a board created just for GameEngine releases by the users of this community, ONLY if approved, maybe a post count/medal count needed?

[Beamery]

I like the idea, could be of help for newbies, especially if you document your problems implementing each part along the way.  Also, nitpicking a little, but for commenting methods, I'd suggest Javadoc comments to make them easier to organize and easier for people to access the documentation.

[ra4king]

Javadoc comments start with /** instead of /* for a normal multiline comment. Then you use a tool like "javadoc" on the command prompt or a built-in function in an IDE to create the HTML.

On the idea, it's great for newbies, but what about you? You're gonna be making tools.....not games