Jump to content

View more

Image of the Day

Inventory ! Va falloir trouver une autre couleur pour le cadre D: #AzTroScreenshot #screenshotsaturday https://t.co/PvxhGL7cOH
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

Sign up now

JavaScript based 2D / 2.5D game engine

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 martens.ms   Members   


Posted 25 January 2011 - 08:31 AM

Hello everybody!

I just found this forum and thought that it would perfectly match my current development stuff.

So, I'm currently developing a little JavaScript-based and lightweight engine for browser gaming. The target are mobiles or slower devices.
I'm currently challenging the architecture. It is built upon mainly in these different "objects / constructors"...

Current architecture:
- Cache: The cache is accessible by everyone, it manages stacks and their entries (via id). e.g. models, levels, objects are hosted there.

- Engine: The logical level, engine loads levels, manages the objects and calls the compositor
- Engine.Hitmap: The hitmap with simple true/false entries.

- Compositor: Translates Objects (Tilegrid Coords & Sizes) to Pixel-based ones (if 2D) or to the 2.5D or 3D coordinates. Can be switched anytime (maybe compositing scheme?).

- Renderer: Uses different technologies to render. Same structure required for all renderers. Currently an HTML-generating renderer, but maybe Canvas or WebGL later.

Examples / Links:
You can find a sample game (wherein I'm experimenting a lot, so please don't flame if it's not working) at

I also built a little editor (rapidly in about 30min) which is in my opinion "just a frontend for the engine and manages it":

To help you have a clue what's going on in these Classes, I created a JSDoc reference:

My current challenge:
The Quest and Player- or NPC-logic. I currently implemented a simple Engine.Character Class that creates a character instance per object. I now have the problem for using quests or other "global interface interactions" that may influence the characters or NPCs.

Imagine you have an NPC walking around until you talk to him. Then he wants you to follow to a given position. After you followed, he wants to show you how the game works (e.g. fighting and stuff). You get points, upgrades and stuff - or quests you will have to solve. These quests are in my opinion something like attached events for objects. E.g. "destroy object with id bla" will be triggered if the object was destroyed. The callback function attached on it will now be called and upgrades the questmap.
...well, or something like that.

I currently have no idea how to realize that (in a well-designed game architecture). So I'm asking you for suggestions or ideas.
You are the pros, I'm just the JavaScript ninja that has no clue of game engines =D

Please have in mind that the underlying DOM (Document Object Model) in web browsers is heavily slow - compared to other environments.
That's why I built the structure in that way.

...I want to thank for any idea or opinion on that!


#2 fatkat   Members   


Posted 27 January 2011 - 04:31 PM


AWESOME I'm doing javascript game development myself!

Your editor is the coolest thing you've got. That's awesome. Are you just relying on animated gifs to do animation? I am thinking of doing image sets for animation so I can control which animation is playing depending on user interaction. Perhaps a set of animated gifs for different animations and swapping the images? Not sure the best way to do baked animation.

So far I am staying out of the <canvas> although my 1st ever completed game (a tetris clone) uses <canvas> check that out here: http://cedarrapidscl...js/tetrominoes/

My intention is to create a new game prototype each week.. The first prototype is a work in progress that will be completed this Saturday. I'm trying to learn collision detection and basic physics - see it here: http://cedarrapidscl.../tyler/messing/

I like your overhead tile based game it's got a very rpg like feel to it and reminds me of the original Zelda.

As far as game engine design and architecture, at this point why worry about it? Make the thing work and if it's an ugly mess, you can clean it up on your next version. When I first started trying to make my physics engine, I was trying to take everything into consideration and create an object hierarchy for linking and such and I just decided and getting nothing visible done, I figured TO HELL WITH IT and just to make SOMETHING work - at least that way I know right away if my game idea has any potential and is worth porting and developing into a full game.

After I get an idea that's amazing and will make me quite rich, I'll spend the time perfecting the engine (and converting it to a platform where I can charge - an app store)

#3 Sirisian   Members   


Posted 28 January 2011 - 01:09 AM

I would have converted it to <canvas> before posting this. Using the DOM like you're doing isn't advised and flickers in Firefox 4b9. I mean it wasn't recommended when people tried to make games in it when it came out. Good start though. Try not to use copyrighted images. There are free sprite libraries online. (Many people have very strong feelings toward copyrighted content).

#4 martens.ms   Members   


Posted 28 January 2011 - 09:45 AM


Edited by martens.ms, 13 February 2015 - 05:33 PM.

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.