roflxd is an umbrella term used to classify all ROFL parsers written by fraxiinus. The goal is to provide developers will easy to use ROFL parsers in the language they want to use.
(I also find writing ROFL parsers to be a great way to learn a new language. So a lot of roflxd projects will be my first project in a language.)
While roflxd projects might differ wildly from each other, every project must at least be able to:
- Verify the integrity of a ROFL file
- Parse the file to a data structure
- Output the data in a format like JSON (or provide a sample project that does)
| Project | Language | Notes |
|---|---|---|
| roflxd.go | Golang | The README labels it as "incomplete" but the ROFL parsing works and meets all roflxd requirements. |
| roflxd.cs | C# (.NET 6) | Fully compliant. |
The following projects are currently planned, or are in progress but not published yet.
| Project | Language | Notes |
|---|
The following projects were created before roflxd or are missing key features.
| Project | Language | Notes |
|---|---|---|
| Rofl.Reader (ROFL Player) | C# | My first ever parser, created for ROFL-Player. Missing the ability to verify data and does not parse player or payload data. However it is capable of reading partial data from LoLReplay replay files (.LRF). Contains incomplete code for reading BaronReplays files (.LPR) |
| Rofl.Reader (ReplayBook) | C# | Updated version used in ReplayBook. Missing the ability to verify data and does not parse payload data. However it parses all player data. Unable to parse anything besides ROFL files. |
Riot Games decided that replay files will just be a dump of the a game's packet data. Packet data is obfuscated in order to deter cheaters. No progress has been made to decode this data because obfuscation is updated every patch. Also Riot would probably send you a cease and desist.
Vote here: #1