That %% thing

[seebs]

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?