Jasoco wrote:At the risk of being stupid and an idiot because it goes against every 3d game ever made, but I always prefer to refer to X and Y as being the floor and Z being the height of the room. It always seemed weird to have Z be north and south and Y being above and below. Just seems stupid and I blame iD Software even though they probably didn't come up with it, but I need a scapegoat to blame and they were the first to come to mind. i.e., the ground in that game would be X and Y and the Z would be the characters jumping or on stairs position above the ground level.
So basically, in my adventure game engine, X and Y are the left, right, up and down of my map and "elevation" is the Z coordinate for when placing scenery or having a flying enemy. Makes much more sense this way to me and doesn't require me to edit my project to replace all the Y's with Z's.
I think your way of doing things is intuitive in your Adventure engine, since it's mostly top-down. For almost-side scrollers, Z for depth make more sense, since Y is closely related to height there.
Jasoco wrote:Also, Robin, your new code seems to work just as well too. Using it for now unless I hit the same bug I had before. Hopefully it works perfect because I like how much less space it takes.
If my memory serves me, mathematically y is up/down (as in height), and because of games people started using z for height (because maps were drawn top-down, and when later drawn 'from the ground', the axes are positioned differently).
Jasoco wrote:At the risk of being stupid and an idiot because it goes against every 3d game ever made, but I always prefer to refer to X and Y as being the floor and Z being the height of the room. It always seemed weird to have Z be north and south and Y being above and below. Just seems stupid and I blame iD Software even though they probably didn't come up with it, but I need a scapegoat to blame and they were the first to come to mind. i.e., the ground in that game would be X and Y and the Z would be the characters jumping or on stairs position above the ground level.
So basically, in my adventure game engine, X and Y are the left, right, up and down of my map and "elevation" is the Z coordinate for when placing scenery or having a flying enemy. Makes much more sense this way to me and doesn't require me to edit my project to replace all the Y's with Z's.
I think your way of doing things is intuitive in your Adventure engine, since it's mostly top-down. For almost-side scrollers, Z for depth make more sense, since Y is closely related to height there.
I'm talking more along the lines of games like DOOM. For some reason X is east and west and Z is north and south and Y is up and down. Makes no sense in that game, but that's how they refer to it. And it's not even like Z simply means depth, since as soon as you aren't facing North, Z is no longer in front of you.
On a straight side-scroller where it only goes left and right and up and down, Z would be for objects layered on the screen. (Hence Z-order.) From far in the distance to right in front of the camera. See also: Parallax layers.
I guess for a game like the one in the OP either way could work. The way I'd do it is X and Y for ground and Z for height off the ground.
