[Guide] Memory Editing - The Basics

[Jadd]

Time to rip this post apart....



You do know that CE is known for getting people banned... right?



WRONG. All memory is client side. Regardless of where the originating info comes from to fill that memory. You can change your stats/level/etc all you want, but it will be client side only.



Wat? See my above note. This is just plain rubbish. I can change all of them without any issues.



....


Finally got something somewhat right.




This should be humorous.



You do realize that ALL addresses can be read/written to? Whether or not you SHOULD is a different story. Please don't tell people things that aren't true.

Also; static addresses are addrs that don't change; and will always point to the same thing. (Functions, certain 'data', etc.)



Close! Just because it isn't static; doesn't mean it won't have the same 'function' as you put it.



For the love of god; at least quote Wikipedia on what a pointer really is. It's just a 'thing' that 'points' to another location in memory. That's all.



Meh; I'm not even going to bother finishing ripping your post apart. It's just too much fail to do so.

I've edited out the parts you mentioned. If you'd like to read it again, I'd appreciate if you'd tell me whether it sounds better or not.

[Cypher]

I think that the "serverside" vs "clientside" memory was a good idea in concept, just not spelled out correctly.

Anything "in memory" on your computer can be read or written to (with the correct permissions).

Some information in memory will have no useful effect on WoW to write to, because it's just a copy of the "real" data that lives on the Blizzard servers. Your level is a good example; you can change the level your client displays in memory, but all significant behavior will still act as though you're at your correct level, because the servers know the "real" value of your level, and you can never touch their memory (unless, of course, you're running a socks proxy in ring 0!!!!!1!)

As Apoc points out, you can read from or write to any memory (with the correct permissions, and possibly after doing some memory protection setting). But a lot of memory you *shouldn't* write to. Note: kernel memory is exempted from this "can write to any memory" thing because unless you can get in the kernel, you *can't* write to it, for good reason. But kernel (ring 0! l3333t!!!!!) stuff is far beyond the level of folks who'd be reading this tut.

Yo dawg, I run mah proxiez in ring0!

[Jadd]

Yo dawg, I run mah proxiez in ring0!

I lol'd.

Flr.

[miceiken]

I think that the "serverside" vs "clientside" memory was a good idea in concept, just not spelled out correctly.

Anything "in memory" on your computer can be read or written to (with the correct permissions).

Some information in memory will have no useful effect on WoW to write to, because it's just a copy of the "real" data that lives on the Blizzard servers. Your level is a good example; you can change the level your client displays in memory, but all significant behavior will still act as though you're at your correct level, because the servers know the "real" value of your level, and you can never touch their memory (unless, of course, you're running a socks proxy in ring 0!!!!!1!)

This is what I understood from it aswell, except new people might not get that.

[CryptoCombat]

almost anyone posting in this section should at least know the difference between client and serverside. understood what jadd meant (yes, he was wrong) but i didnt even notice the err, because it was an area that's common knowledge.

on a side note, I've used CE with my main for years, reading and writing. armor and weapon Id's. etc.

[Krillere]

For anyone not knowing, here's how it would look in C++, ( Sorry for ugly code.. )

BlackMagic^ WoW = gcnew BlackMagic()
WoW->OpenProcessAndThread(SProcess::GetProcessFromProcessName( "Wow.exe" ) );
String^ Name = WoW->ReadASCIIString( 0x00C923F8, 12 );

I got a quick question, what's the "12" in the ReadASCIIString function? What's it for?

[namreeb]

My guess would be how many bytes to read?

[Jadd]

For anyone not knowing, here's how it would look in C++, ( Sorry for ugly code.. )

BlackMagic^ WoW = gcnew BlackMagic()
WoW->OpenProcessAndThread(SProcess::GetProcessFromProcessName( "Wow.exe" ) );
String^ Name = WoW->ReadASCIIString( 0x00C923F8, 12 );

I got a quick question, what's the "12" in the ReadASCIIString function? What's it for?

How many characters to read in the string, and 12 is the maximum amount of letters you can have when naming your character.

[Cypher]

For anyone not knowing, here's how it would look in C++, ( Sorry for ugly code.. )

BlackMagic^ WoW = gcnew BlackMagic()
WoW->OpenProcessAndThread(SProcess::GetProcessFromProcessName( "Wow.exe" ) );
String^ Name = WoW->ReadASCIIString( 0x00C923F8, 12 );

I got a quick question, what's the "12" in the ReadASCIIString function? What's it for?

Correction, that is how it looks in Managed C++.

Managed C++ is NOT 'C++'. 'C++' refers to unmanaged C++. Please be specific next time to avoid any confusion, because I'm so sick of people getting the two confused and then having to explain to them the difference and why it's so important.

[suicidity]

I'm sickened by that crap.

char* Name = (char*)0x00C923F8;

Win.

[Apoc]

Correction, that is how it looks in Managed C++.

Managed C++ is NOT 'C++'. 'C++' refers to unmanaged C++. Please be specific next time to avoid any confusion, because I'm so sick of people getting the two confused and then having to explain to them the difference and why it's so important.

It's actually C++/CLI. Managed C++ is the uglier; more ****ed up version of C++ for .NET. (Yes; there's a major difference. The main one being syntax)

[flo8464]

Navigator::Process proc(Process::getProcessByProcessName(L"wow.exe");
std::string name = proc.readAsciiString(0x00C923F8, 12);

Uhhh, with my lib it is a two-liner.

[ramey]

still don't get why you're not just injecting a dll because you're using C++.. but hey.

[Krillere]

Sorry for the confusion.

[Glynbeard]

this thread is full of lols.