[Lorenc_]

Quote:

Originally Posted by SecretBoss I run some tests because I wanted to make a function to continue messages to a new line if they are very long and I received such messages when the string was too long Logs: Code: [19:43:30] [join] SecretBoss has joined the server (0:192.168.2.2) [19:43:50] sscanf warning: String buffer overflow. [19:43:53] sscanf warning: String buffer overflow. [19:43:54] [part] SecretBoss has left the server (0:2) [19:44:18] [connection] 192.168.2.2:55307 requests connection cookie. [19:44:19] [connection] incoming connection: 192.168.2.2:55307 id: 0 [19:44:19] [join] SecretBoss has joined the server (0:192.168.2.2) [19:44:33] sscanf warning: String buffer overflow. [19:44:38] sscanf warning: String buffer overflow. [19:49:32] sscanf warning: String buffer overflow. [19:49:34] [part] SecretBoss has left the server (0:2)

Yeah but sscanf handles it AFAIK. So it shouldn't be a problem.

Managed to portionally fix it by searching all my formats carefully. However, the random messages are being unfortunately bugged.

Please let me know if you know some ways to cause overflows in ways I wouldn't imagine (or something)