Cheat Engine

[DjSt3rios]

Not really, Nowadays server do not use GameGuard, as they were problems. Most of the servers just disabled game guard. I found out that only if i add a breakpoint it crashes.. i debugged it with no breakpoints and no BSOD. Now about the variable thingy, a 10 digit number is 10 bytes right? but how could I store it if the maximum amount of bytes is 8? Damn C++ is really confusing. As I saw the key is always 10 digits long, either negative or positive. I also tried saving it as a text but i found out its not working that way. By the way, I am not sure but, In cheat engine the value is shown as 4 byte. That doesn't mean that a long variable can hold it, right? I am really confused..

[atom0s]

[DjSt3rios]

Hmmm Okay. I will try to create an unsigned int, and i will also check its maximum value of the key. Otherwise I will try with an unsigned long.
Also, What exactly do you mean by an anti-cheat might still be running? the weird thing is I never had issues with Dev C++ and debugging.

[atom0s]

[DjSt3rios]

I have AVG Anti-virus, I disabled it temporarily, and now I didn't get BSOD. The application now seems to be okay with the memory problems, although now my application cannot read the username of the player properly. It might be another memory problem but for some reason, I don't think so. I will try to stop all threads and only pick the username, and see what happens. I will edit this post soon.

edit: Yep it doesn't seem its like memory problem. I disabled all threads, and it still gives me some weird letters every time I run it. I also tried to run it as administrator and with/out debugging. The text is unicode so I suspected maybe using Visual Studio's compiler it might require some more work to read unicode text, even though, with the way I use ReadMemoryString, it shouldn't be happening, because it reads 1 character each time... I changed strcpy to sprintf... if i use strcpy it gives me a really huge message with a lot of "M" characters..

[atom0s]

If the string is unicode you need to treat it as such.

'char' is specific to multibyte (ASCII), wchar_t is specific to unicode.
std::string is also specific to char. If you need the unicode version use 'std::wstring'.

Both your ReadUsername and ReadProcessMemoryString are specific to char types and not unicode. Its an issue with your code, not Visual Studio.

[DjSt3rios]

Hmm. I tried what you said, After a few tries I managed to make it work a bit, but I still had problem converting wstring to char, I mean I did but some weird characters were printed instead of the username. Now I managed to fix the problem using char, just like I had it, i just increased the number of the bytes to read from 1 to 2, and works like a charm. I don't know if this can cause any problems, but looks okay so far. I will fully test it now and see how it will go.

Edit: Seems okay so far. Thanks a lot, I will update if anything goes wrong.

[atom0s]

You can convert a wstring to chars using:

std::wstring wstr = L"Some random unicode string.";
std::string str( wstr.begin(), wstr.end() );
const char* pszString = str.c_str();

[DjSt3rios]

Mhm, Thanks for the info but I still have problems using those. In the username alot of "M" characters appear... maybe I should just use normal char and string?

[atom0s]

If the string in memory is unicode you will need to read it as unicode.

You can just stay to using the unicode string instead of converting it afterward though. There is unicode versions of every string function you use in your code.

[DjSt3rios]