Author Topic: How to client-sidedly get a player's position  (Read 2661 times)

I was wondering if there's a way to detect a player's position on the map on the client's side. Which function or variables to you use to find a player's position/transform?

I'm pretty sure you can get your own position by doing ServerConnection.getControlObject().getTransform() or something like that.

No one will help you with other players.

I was wondering if there's a way to detect a player's position on the map on the client's side.
There is.
Which function or variables to you use to find a player's position/transform?
You have to figure that out yourself D:

I'm pretty sure you can get your own position by doing ServerConnection.getControlObject().getTransform() or something like that.

No one will help you with other players.
The ServerConnection.getControlObject().getTransform(), ServerConnection.getControlObject().getPosition() and ServerConnection.getControlObject().position functions and variables don't work on other players.

You could get the other positions through other means by making external apps, etc. but that's pretty shady and discouraged

Heh, if you can't figure out how to do this on your own, don't even bother.

Heh, if you can't figure out how to do this on your own, don't even bother.

Implying you figured this method out yourself instead of having someone show it to you.

You could get the other positions through other means by making external apps, etc. but that's pretty shady and discouraged
Or by removing the blocker from the getposition function, or by using a way more easy way that leads to slightly off positions

You guys need to stop talking about this. Nobody is going to think you're cool and know hax and workarounds if you forget everyone else over by letting more people use it and badspot has to do something drastic to patch it, thus taking away more privileges for benevolent modding in the future

You guys need to stop talking about this. Nobody is going to think you're cool and know hax and workarounds if you forget everyone else over by letting more people use it and badspot has to do something drastic to patch it, thus taking away more privileges for benevolent modding in the future
^this

this is why we can't have nice things, people always get selfish and we lose more cool stuff

You guys need to stop talking about this. Nobody is going to think you're cool and know hax and workarounds if you forget everyone else over by letting more people use it and badspot has to do something drastic to patch it, thus taking away more privileges for benevolent modding in the future
Let's get this cool quote:
Quote from: Badspot
Look, it's not possible to secure a function in an executable running on an open client.  The point [...] is to prevent kiddies from stuffting all over everything.  If you spread information on how to access this function you're just being a jerk.
Now follow these wise words and stop telling people how to do it or you're a jerk!

Just dropping in to say there's pretty much no way Badspot could entirely remove our ability to get other players' positions. Even if he patched current torquescript methods which I'm positive he knows how to fix already, playerpointer+0x7A0 is the location of their position in memory. Even if he removed storage of positions in memory, we could hook into every packet received and build a list of positions. That said, there's very few non-abusive uses for clientsidedly parsing player position data. It's clear that most of us know how to get a position clientside, and thus that it's not really a secret, so any pride derived from knowing this is pointless. Hammereditor, sorry but Badspot has voiced his opinion and he doesn't want us doing what you're asking. Everyone else, it doesn't have to be a debate on ethical scripting every time someone wants to know this. Alright then, have a great day Coding Help.

Basically what Aide said above.

But what's the use? The only useful thing you can make is a radar that tracks your own position really.

Just dropping in to say there's pretty much no way Badspot could entirely remove our ability to get other players' positions. Even if he patched current torquescript methods which I'm positive he knows how to fix already, playerpointer+0x7A0 is the location of their position in memory. Even if he removed storage of positions in memory, we could hook into every packet received and build a list of positions. That said, there's very few non-abusive uses for clientsidedly parsing player position data. It's clear that most of us know how to get a position clientside, and thus that it's not really a secret, so any pride derived from knowing this is pointless. Hammereditor, sorry but Badspot has voiced his opinion and he doesn't want us doing what you're asking. Everyone else, it doesn't have to be a debate on ethical scripting every time someone wants to know this. Alright then, have a great day Coding Help.
yay youre back

Basically what Aide said above.

But what's the use? The only useful thing you can make is a radar that tracks your own position really.
Client sided player positions could do tons of cool stuff that are not necessarily bad.

Ex: Mumble positional audio plugin without getting the positions from the memory and a whole load of other neat things

I think you're going to have a tough time writing a mumble plugin in torque.