Jump to content
splinter2k

The new Anti teleport script. Reported to server's RPT log

Recommended Posts

Greetings,

The new Anti Teleport script seems to be logging to my RTP log file. For example:

11:43:57 "TELEPORT REVERT: PlayerNameRemoved (IDRemoved) from [9046.53,1969.15,0.00096184] to [8.02051e-006,6.52649e-006,0.00146103] now at [9046.53,1969.15,0.00096184]"

I have a quite a few of these entries from about 6-7 different players. Does anyone know how to interpret this log entry. What concerns me is that the player seems to have made a round trip in one second, if I'm reading this right.

Any guidance would be appreciated.

Thanks,

Splinter

Edited by Splinter_2K

Share this post


Link to post
Share on other sites

I think that is a anti teleport. They try and teleport and they game puts them back. This is the logs working, he should still get a ban from you though, as he was trying to script.

  • Like 1

Share this post


Link to post
Share on other sites

I think that is a anti teleport. They try and teleport and they game puts them back. This is the logs working, he should still get a ban from you though, as he was trying to script.

Thank you for the quick response.

Regards,

Splinter

Share this post


Link to post
Share on other sites

Be careful, a teleported player can be a victim of a cheater. So don't ban them only because of the logs you see.

  • Like 2

Share this post


Link to post
Share on other sites

Be careful, a teleported player can be a victim of a cheater. So don't ban them only because of the logs you see.

Agreed. My thought was to look for multiple entries from the same player within a short time period. For example, the following block of entries are from the same player:

6:07:14 "TELEPORT REVERT: PlayerNameRemoved (ID) from [-1.94505e-008,6.85843e-009,51.7151] to [11402.9,3308.22,0.00163603] now at [-1.94505e-008,6.85843e-009,103.41]"

6:07:14 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-7.65572e-008,2.13482e-008,102.215] now at [-1.94505e-008,6.85843e-009,103.425]"

6:07:15 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,99.6876] now at [-1.94505e-008,6.85843e-009,103.453]"

6:07:15 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,97.2093] now at [-1.94505e-008,6.85843e-009,103.482]"

6:07:16 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,95.0265] now at [-1.94505e-008,6.85843e-009,103.5]"

6:07:16 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,92.6161] now at [-1.94505e-008,6.85843e-009,103.498]"

6:07:17 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,90.5691] now at [-1.94505e-008,6.85843e-009,103.473]"

6:07:17 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,88.5302] now at [-1.94505e-008,6.85843e-009,103.427]"

6:07:18 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-1.94505e-008,6.85843e-009,51.7151] to [-1.94505e-008,6.85843e-009,86.4753] now at [-1.94505e-008,6.85843e-009,103.37]"

6:15:33 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [878.083,1766.01,0.00137541] now at [2.91294e-005,-6.33799e-006,103.688]"

6:15:33 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91407e-005,-6.36518e-006,102.491] now at [2.91294e-005,-6.33799e-006,103.659]"

6:15:33 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91294e-005,-6.33799e-006,99.9963] now at [2.91294e-005,-6.33799e-006,103.535]"

6:15:34 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91294e-005,-6.33799e-006,97.3089] now at [2.91294e-005,-6.33799e-006,103.356]"

6:15:35 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91294e-005,-6.33799e-006,94.7186] now at [2.91294e-005,-6.33799e-006,103.198]"

6:15:35 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91294e-005,-6.33799e-006,92.4673] now at [2.91294e-005,-6.33799e-006,103.127]"

6:15:36 "TELEPORT REVERT: PlayerNameRemoved(ID) from [2.91294e-005,-6.33799e-006,51.7968] to [2.91294e-005,-6.33799e-006,89.8391] now at [2.91294e-005,-6.33799e-006,103.173]"

6:21:20 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [12246.2,3119.43,0.00163537] now at [-2.26335e-008,9.23463e-009,102.828]"

6:21:20 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,101.121] now at [-2.26335e-008,9.23463e-009,102.938]"

6:21:20 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,98.6964] now at [-2.26335e-008,9.23463e-009,103.113]"

6:21:21 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,96.295] now at [-2.26335e-008,9.23463e-009,103.32]"

6:21:21 "TELEPORT REVERT: PlayerNameRemoved (ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,94.2132] now at [-2.26335e-008,9.23463e-009,103.498]"

6:21:22 "TELEPORT REVERT: PlayerNameRemoved (ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,92.2971] now at [-2.26335e-008,9.23463e-009,103.602]"

6:21:22 "TELEPORT REVERT: PlayerNameRemoved (ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,90.3017] now at [-2.26335e-008,9.23463e-009,103.614]"

6:21:23 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,87.7749] now at [-2.26335e-008,9.23463e-009,103.534]"

6:21:23 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,86.3259] now at [-2.26335e-008,9.23463e-009,103.393]"

6:21:24 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,81.6099] now at [-2.26335e-008,9.23463e-009,103.209]"

6:21:24 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,82.4827] now at [-2.26335e-008,9.23463e-009,103.077]"

6:21:25 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,80.3552] now at [-2.26335e-008,9.23463e-009,102.999]"

6:21:25 "TELEPORT REVERT: PlayerNameRemoved(ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,78.4274] now at [-2.26335e-008,9.23463e-009,102.991]"

6:21:26 "TELEPORT REVERT: PlayerNameRemoved (ID) from [-2.26335e-008,9.23463e-009,51.4352] to [-2.26335e-008,9.23463e-009,77.9938] now at [-2.26335e-008,9.23463e-009,103.038]"

I'm assuming this is more than a cheater Teleporting someone else.

Thanks,

Splinter

Share this post


Link to post
Share on other sites

There is a bug in the anti-TP thing: if a player dies and respawns, then the new respawn point is seen has a TP. This can be explained by the code used by anti-TP : between 2 checks, it does not that the players died and respawned.

  • Like 1

Share this post


Link to post
Share on other sites

There is a bug in the anti-TP thing: if a player dies and respawns, then the new respawn point is seen has a TP. This can be explained by the code used by anti-TP : between 2 checks, it does not that the players died and respawned.

Exactly. This is from my RPT (I've been testing this in my server). I had zeds kill me >> hit abort >> respawned into the game >> and it runs this loop:

3:46:43 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,72.2622] now at [2.39434e-005,1.94833e-005,103.267]"

3:46:44 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,71.8908] now at [2.39434e-005,1.94833e-005,103.302]"

3:46:44 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,71.6179] now at [2.39434e-005,1.94833e-005,103.359]"

3:46:45 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,71.4059] now at [2.39434e-005,1.94833e-005,103.393]"

3:46:45 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,71.205] now at [2.39434e-005,1.94833e-005,103.373]"

3:46:46 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,70.9792] now at [2.39434e-005,1.94833e-005,103.3]"

3:46:46 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,70.7267] now at [2.39434e-005,1.94833e-005,103.212]"

3:46:47 "TELEPORT REVERT: TG ! Jimmy (40605797) from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,70.4818] now at [2.39434e-005,1.94833e-005,103.163]"

Take note of this "from [2.39434e-005,1.94833e-005,51.7503] to [2.39434e-005,1.94833e-005,70.4818] now at [2.39434e-005,1.94833e-005,103.163]" the FROM field and the TO field are the same. Since I know the exact circumstances behind this loop (for this one example) I can tell that it's looping me when I try to respawn--so it's not someone teleporting me. That probably also explains why the FROM and TO fields are identical.

In any case, it's a bug that has been raising some questions in my server.

Share this post


Link to post
Share on other sites

This is the skin change bug.

It killed me, when I first logged on :

You log on the place you were, the game tp you to change your skin, then the Anti TP tp you where you were.

And it loops.

If you hit the water you die.

Edited by Ameo

Share this post


Link to post
Share on other sites

This is the skin change bug.

It killed me, when I first logged on :

You log on the place you were, the game tp you to change your skin, then the Anti TP tp you where you were.

And it loops.

If you hit the water you die.

Correct, Sir. It's not that big a deal to me, but when the server has a mess of people in it who can't figure out what's going on--it takes a toll on traffic. That's really my concern, the players who are subjected to it something they can't control (and don't understand often times).

Share this post


Link to post
Share on other sites

That's right Jimmy.

Razor do you read this ? Is there a fix on schedule for this anti-tp problem ? People may deals with it, but it happens often, for all heroes, dunno for the other "special" skinz.

Sure thing, if it don't kill you, you come back at the beach, no matter where you were.

Edited by Ameo

Share this post


Link to post
Share on other sites

On next release, it will be an option during the mission file built. See pre-release note.

Hero skin bug should be gone too.

Share this post


Link to post
Share on other sites

We know about this its a humanity issue. It has been fixed we are just waiting to release.

  • Like 1

Share this post


Link to post
Share on other sites

Anti-TP seems to cause more problems than it fixes. And cheaters can bypass it with four lines of code, so it is really useless.

I dont agree tbh.. We haven't had any mass hacker teleporting going on since the new 1.7.6.1 patch, so whatever the devs changed it most certainly worked. Problem indeed is with individual hackers. We still have hackers teleporting around the map. As far as I've seen they're not able anymore to teleport loads of players at the same time.. (this is what I've been seeing in our server logs at least).

  • Like 1

Share this post


Link to post
Share on other sites

.

Edited by ebay
  • Like 2

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×