As long as you have a screenshot, it's possible to easily reconstruct the message you see.
The message you search is:
Code:
(ŸËž²) \c0xffffffff\c%s\c0xffff7878\cŽÔÀÌ °ÔÀÓÁß¿¡ ÀÔÀåÇό̜ÀŽÏŽÙ.
(Note: Due to differences in the fonts, the symbols look slightly different here. I can assure you that the hex values are still correct, though! You should copy the characters into a new text-file and save it as a ISO-8859-15 [Western] encoded document.)
Contrary to what you'd expect, the message isn't in Thai but in Korean. To get a somewhat usable Google-translatable text, you can create a new html document like this one:
Code:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr" />
</head>
<body>
<p>(ŸËž²) \c0xffffffff\c%s\c0xffff7878\cŽÔÀÌ °ÔÀÓÁß¿¡ ÀÔÀåÇό̜ÀŽÏŽÙ.<p>
<hr />
</body>
</html>
Opening this page in a browser of your choice should give you the original Korean text.
Now, as for the method of finding strings like this:
Pop up Windows' character table and start looking for symbols you can reconstruct. Remember to use the font you also use in Pangya (in this case: Verdana or Arial, depending on what you changed it to). For this string, the beginning and the end are notable. And we know there's a colorchange as well as a field for a string somewhere in the middle.
So, click together the first part (excluding the parentheses) and search for this string in ProjectG... you'll get a few results but just by looking you'll notice the difference in the following characters and the absence of the previously mentioned colorchange/nickname. So continue to jump from result to result - until you hit the message seen above.
The second line is a tough one - it doesn't have any readable characters except the ones we already searched for. That's where trial & error comes in... ugly way to solve it, but meh...
