What strikes me as odd is if outspark were truely serious about fixing this problem, they should request more information. Instead of just date, time, and events leading up (which are clearly evident by now), they should request the minidump file.
Although I'm not sure if that holds any information that they can use, but normally all games come with some sort of error-handling. Meaning they either keep a log, or create an error-report file.
It appears every time those spammers crashed my game in my outspark folder a minidump file was created.
/Outspark/Fiesta/Dump/MiniDump.dmp
Although getting rid of the people who do this is a good idea, its a short lived solution at best. Fixing the problem at its roots would permanently solve the issue.
Originally Posted by MaxOff
|
well i dont play fiesta right now, so i cant tell how the trick works, but my guess is that they send an char that cant be rendered in the current font, so installing a font like cyberbit and changing the font.ini so fiesta uses that font may prevent the trick from working.
cyberbit is free for non commercial use.
anyway, dont blame hackers. It may was a hacker who found that out, but its normal users who exploit it.
|
All characters are glyphes. As such each font has respectively 256, or 65536 characters depending on whether its unicode or ASCII. So the characters themselves arent the issue as all of them are capable of being rendered. However, at index value 0, exists a null character. The null character signifies the end of a string.
Depending on how strings are handled, a null character can turn a string stored in the computer as "this is a \0 null charactered string" to read "this is a ".
Why is the null character so dangerous? Well if I could place one in my post, nothing in the website beyond that character would exist.
Since it crashes the game, there must be an internal problem, buffer overflow, or null-pointer resolution.