player.localx & player.localy

[DustyPorViva]

On gmaps, these will return the player's local coordinates in the level, not on the gmap.

[salesman]

Can't you just mod the player.x or player.y by 64?

player.x [PERCENTSIGN] 64;
player.y [PERCENTSIGN] 64;

The only problem is that I think it may be off by a small amount because it can't return odd decimals

[DustyPorViva]

Actually it's int(player.x/64)*64 + player.x

[salesman]

Originally Posted by DustyPorViva

Actually it's int(player.x/64)*64 + player.x

That's definitely not the local x coordinate

[napo_p2p]

Could use:

PHP Code:

player.x - 64*getmapx(player.level.name);  //Local x
player.y - 64*getmapy(player.level.name);  //Local y 


[cbk1994]

Originally Posted by DustyPorViva

Actually it's int(player.x/64)*64 + player.x

... what?

Sales is correct, however, this would be a great addition (for serverside and clientside).

[Inverness]

I agree with the suggestion.

[DustyPorViva]

Originally Posted by cbk1994

... what?

Sales is correct, however, this would be a great addition (for serverside and clientside).

Ya, that's my mistake. I was thinking something totally different because I was working on a script using that. My bad :P

[salesman]

Thought of something while I was at work that would give the exact decimal instead of a .0625 approximation which is what you get when simply doing player.x [mod] 64

PHP Code:

int(player.x % 64) + (player.x - int(player.x)); 


but what napo said might be easier

[DustyPorViva]

It is pretty simple, but to have to do this whenever we want to do a simple comparison check in a level gets redundant. Not to mention for LATs and such, it's probably way out of their league.

[salesman]

Originally Posted by DustyPorViva

It is pretty simple, but to have to do this whenever we want to do a simple comparison check in a level gets redundant. Not to mention for LATs and such, it's probably way out of their league.

Agreed, player.localx and player.localy would be nice