screenx screeny worldx worldy
 

why do they take the x and y? Shouldn't they just take x or y depending on if its screenx or y or worldx or y?

worldx( x,y ) converts screen x,y to level x
worldy( x,y ) converts screen x,y to level y
screenx( x,y ) converts level x,y to screen x
screeny( x,y ) converts level x,y to screen y

Why does screenx need the levels x and y to tell me just the screens x

maybe because that would limit their usefulness on a gmap?

(I am talking about 3D terrain here)

What do you think these functions do, and what arguments do you think they should take?

well i mean screenx should only take x and screeny should only take y, same with worldx and y.

I mean it doesn't make sense to give it an x and y. All worldx does is convert the screens x to the levels x, I dont see wheres the Y comes in as any use, I mean you could put any number in there as the y and you'd get the same output.

3D terrain, as Evil said.
It affects the y coordinate, so I assume Stefan put the x,y in the screenx/worldx to keep continuity between functions.

im working with 3d terrain and i see absolutely no differance, im basically using this to keep weather on the players screen :P

I win the prize?

Uh, no. The mapping of ground coords to screen coords (and vice versa) is not linear in the y direction; it involves a modifier that can only be determined through use of an x coordinate.

Ohh thats true, because the terrain can cause the coords to be in a differant place.