Update on movement tracking data

[Theoya]

Hey there!

I'm looking at using movement data for a project, but before I go and try and implement it Id love to know if you've already done it, or made any serious progress on it that I can use as a jump off point.

Specifically looking for X/Y here, and failing that a decent map of what Bytes and what sections of what Bytes mean what.

[NinjaFalcons]

Check for the bytes 607385feb0xx where the xs are something like 01 02 etc. The format is then x,y,z each are 4 bytes and floats

[pjsny]

@Theoya dm me on the r6 dissect discord, I've reacted to this message, my username is pretty much the same

[Theoya]

@pjsny For sure! I cant seem to find it though, would you mind tossing me a link?

[KevinCCucumber]

As much as I appreciate the thought, but I would rather not have something public that is able to read player positions from a replay.
As soon as player leaves the match, the replay file will be dumped to the harddrive. Sharing a tool publicly that is able to scrap players positional data from a replay allows just leaving a match and basically get enemy positions for free right the second you leave.
I am interested in the positional data stuff as well but I dont want to open the box of pandora.

[Theoya]

Eh, I don't think thats a pandoras box to be worried about.

Sure, worst case you can leave the game and get that position data, but its not going to be relevant for long at all, and that team's down a player now.

So all and all, definitely worth any worst case. I have a pretty impactful usecase in mind

[pjsny]

@KevinCCucumber reading positional data from replays is standard across games. It's really not a controversial idea. As to whether whoever does the work to reverse engineer it wants to open source it is up to them. My friend and I had positional data a couple seasons ago on replay version <7 but didn't feel like releasing it