Bakkesmod obfuscates player inputs and actor info in online matches, to prevent a competitive advantage. That's obviously never going to change, but I'm wondering if you'd consider exposing an API that gives the player inputs well after the fact, to prevent the competitive advantage.
I'm thinking something like the info could be on a fixed delay (240-360 ticks behind), or maybe just a list of them is gettable once the match is over.
My use case would be reconstructing a multiplayer situation in freeplay for training/learning purposes (practice a recovery that I flubbed, or a shot that I missed, etc). Currently you have to reconstruct a scenario from the replay, which suffers from some jankiness due to replays running at a lower tick rate.
mgavin
commented
7 months ago
Bakkesmod obfuscates player inputs and actor info in online matches, to prevent a competitive advantage. That's obviously never going to change, but I'm wondering if you'd consider exposing an API that gives the player inputs well after the fact, to prevent the competitive advantage.
I'm thinking something like the info could be on a fixed delay (240-360 ticks behind), or maybe just a list of them is gettable once the match is over.
My use case would be reconstructing a multiplayer situation in freeplay for training/learning purposes (practice a recovery that I flubbed, or a shot that I missed, etc). Currently you have to reconstruct a scenario from the replay, which suffers from some jankiness due to replays running at a lower tick rate.