Anyone know if this is related to ukeys?
|
Hello if anyone can help me with this. Basically the client has a problem loading if anything within the cache is changed. Even changing one byte messes the entire client up and stops it from loading if anyone has any ideas of what might be causing this or a potential fix that would be very helpfull. (Maybe this should be moved to requests idk)
Thank you for any advice!
Anyone know if this is related to ukeys?
Changed one letter on an interface. Just using alex's libs, I don't believe the cache is encrypted otherwise I wouldn't be able to read the data.
Hmph could you explain why not? It's one of the only things I could find dkk write about 614 clients requiring something to do with ukeys.
Post the code for reference table generation in client
Renamed the refrencetable in 614 client and seems to be different going to change my refrence table encoder and try to pack when I have time to see if that fixes the problem!
It's not throwing a referencetable error because It's still encoding as the same "protocal" but differnet stuff is in to for 614.
Thanks
Any specific things you came across that would suggest it's the clients fault and not our cache editing libs? Would help me narrow the search if the reference table stuff doesnt pan out!
From the areas I've looked at doesnt seem to have been edited majorly (I haven't looked very far yet) so It's probably to do with the reference table tbh.
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |