seebs Posted January 3, 2020 Posted January 3, 2020 So I'm guessing that the reason that a ton of things now say "%%" is that there's a client-side bug which sometimes passes server-provided messages to a printf-like function incorrectly, resulting in things like the Kismet +50x0p23ccuracy proc. But if there's now a 64-bit client, that implies client source exists now, I assume, so... would it be possible to fix the client-side bugs, and NOT send double % on everything?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now