Planned Features, Limitations

[Gleeok]

@franpa suggested this: http://armageddongames.net/showthrea...l=1#post892301 which I thought was pretty good. :)

So if I got this right so far -- we have an event, warp, object, collision, tile properties layer..? ...this seems like a lot though - how about making 'warp' an 'event'..

Are you doing any optimization with your layers similar to what 3D engines do, where only what is visible to the player actually gets sent to be rendered?
.

I don't think depth testing is useful for 2D, but yes and no, obviously things off the screen will not be rendered though there it's not feesible to check every tile for "what it will look like after it is rendered". This would result in much worse performance.

[CJC]

@franpa suggested this: http://armageddongames.net/showthrea...l=1#post892301 which I thought was pretty good. :)

So if I got this right so far -- we have an event, warp, object, collision, tile properties layer..? ...this seems like a lot though - how about making 'warp' an 'event'..

Well... the layer wouldn't necessarily be set aside for these purposes. If the tile properties where assigned to the TILE and not the layer (Ala Comboing, though probably with the ability to attach a script to a tile, for the case of event triggers), and if all layers stacked their properties to that position on the map, then we could use some layers for visual purposes, some for solidity, and some hidden for events (though using more than one of these might prove dangerous).