Open hamhotline opened 9 years ago
I've had some progress, leave your contact so we can share some data.
skype: hamhotline email: hamhotline@gmail.com
We'd love if you'd share the results & informations with the loldevs project. Feel free to join our IRC Chat @ freenode. Currently the project is kind of sleeping but that hopefully changes in the future again. http://loldevs.github.io/#contributing
Hey @themasch @hamhotline is there an active community which parses .rofl files to extract stats n stuff?
I do not know of any. Lost track of all this a few years ago shortly after I stopped playing league. Good look finding one, let us know!
Well now I can finally confirm that to me it also seems the type byte is 2 bytes but I'm getting types which have both bytes with values
Looks like Riot changed the specs for the standard block structure in the latest patch, as far as I can tell. The
type
byte now is 2 bytes, rather than one, based on some quick investigation. Or, perhaps, Riot added another byte with unknown information.My guess is that they changed the
type
byte to be 2 bytes for flexibility, as all of the header blocks I've manually checked withtype
bytes have0x00
as the second byte. Although that evidence could also point to a new unknown byte that they're not using yet.Anyone else able to confirm this on their end? Any ideas on the new byte?
EDIT (1/3/15): After a little more investigation, I think there's also a good chance that Riot changed the spectator encryption method or other things about the spectator mode than just a new type byte. Not sure. I'll keep updating. Let me know if you'd like to join me and I'll give you my data.