Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

AU23_Admin

How to spot teleporters in logs // How to see who killed who (for when hackers kill normals)

Recommended Posts

You cannot see who killed who in the RPT file. You can correlate player ID's with times of death, but not who killed them.

Positional data can be sort of eyeballed in the RPT file but its really not easy to determine teleportation events by tracking it and some folks that are real abusers of the system will show no positional data at all....like this guy here:

19:39:43 "LOGIN ATTEMPT: "3383808" (MAS) lulz"

19:39:43 "Locality Event"

19:39:43 "READ/WRITE: ['PASS',false,'29048617',[],[["ItemFlashlight"],["ItemBandage","ItemPainkiller"]],["DZ_Patrol_Pack_EP1",[],[]],[0,15,15],"Survivor2_DZ",0.94]"

19:39:43 "LOGIN LOADED: B 1-1-A:41 ((MAS) lulz) REMOTE Type: Survivor1_DZ"

19:39:44 "Locality Event"

19:39:44 "READ/WRITE: ['PASS',[],[0,0,0,0],[],[],-83020]"

19:39:44 "LOGIN PUBLISHING: B 1-1-F:1 ((MAS) lulz) REMOTE Type: Survivor2_DZ"

The READ/WRITE at 19:39:44 should have locational data where the 0,0,0,0 is...but it doesn't, but this very same individual was able to destroy the entire area of Berezino and its surrounding industrial spawns with some kind of hack that was allowing him to shoot off around 2300 rounds of G_40mm_HE in the space of a minute.

So overall locational data is pretty hard to use to track teleporting because even if someone does have locational data, there is no legal to use applications that can translate it into how much distance was actually traveled in how much time and unless the differences in the shift in numerical position is extremely vast between two very close time stamps its nearly impossible to be sure.

Share this post


Link to post
Share on other sites

That's because the hive is no longer reporting minute by minute position updates, which by the way I think is stupid. Apparently we admins are rampantly abusing our access to the logs and hunting people down like dogs, oh wait...

No all we get is at best Login/logout positions.

  • Like 2

Share this post


Link to post
Share on other sites

×