wrpl unpacker is outdated
Yay5379 opened this issue · comments
The wrpl unpacker is not compatible with replays from newer versions of war thunder. (This is most likely due to the addition of the nuclear bomb)
wrpl unpacker hasn't been updated since 3 years, the game evolved a lot in that timestamp, anything would make the replays uncompatible, as just a simple turret speed change would make it uncompatible.
By default, a replay only works in it's version, not another one.
What do you find useful inside the replay? Do the versions before the format change have value for you?
Now the replay contains blocks whose structure differs from the previous one: [Header] [DataSize] [Data]
I will have to recognize it as the data flow progresses.
It is easier for me to support only the current version, so that the parser is not cluttered with dead branches.
There isn't any real useful info in replay...
So idk what it could be used for
Yes, the content of the blocks has not changed. I guessed many fields from the header. From the useful there is the version, the size of the first block and the offset of the last block. Thus, for all 3 blocks, you can calculate the size for a given header size of 0x4c4. The rest of them duplicate the fields from replays.wdb and the first block.
Hello! I also have some interest in having .wrpl extract working and I do hope that server replay can hold a bit more information about the match.
Problem
This mission end window is displayed only once in a game right after you leave a match or it ended.
From this window you can get a lot of information about each of the vehicle you used in this match.
- Time spent.
- Total critical hits
- Total hits
- Total kills
- Total caps
- some other.
Possible outcome???
Would it be possible to parse/extract server replays just to get key server data and ignore all other information that could change during next update?
- Timestamp of user spawn a vehicle.
- Timestamp of user scoring a kill/hit/crit hit in specific vehicle.
- Timestamp of user successfully capping a point.
- Timestamp of user dying in vehicle
Server replays are split into multiple parts. They are listed at https://warthunder.com/en/tournament/replay/ and this is an example replay: https://warthunder.com/en/tournament/replay/type/154177510472539583
Random Update (It's been 2 years): Whenever I try to extract a replay I noticed that the error message is always construct.core.ConstError: parsing expected b'\x00BBF' but parsed b'kill'. I also noticed that replays that do not have a nuke are able to be unpacked. This leads me to theorize that the nuke causes some sort of quirk in the replay system.
Opening a new issue with more details about what the problem might be.
This leads me to theorize that the nuke causes some sort of quirk in the replay system.
This would make a lot of sense.