All Other Games listed here!!

[v1rr3n]

I am sorry if any of this info has been posted before. If it has, perhaps there is a need to bring the stuff back up because there has been a lot of statements made pertaining to this.

I figured I would start by explaining why you get undesired results with memory editors (Cheat Engines, tsearch, etc.) and the injection of DLLs. I'll start with explaining how massive multiplayer online games are made.

The developers make two components to the game. Client and Server.

CLIENT
The first is the client. It is what you download and install, and it is what you see when you launch the game. One way to put it is, it only handles your input into the virtual world and the output of certain things in the virtual world. The output is displayed visually to you as what you see when you play the game. The player's locations (ON THE SCREEN, NOT THE ACTUAL LOCATIONS), names, chat, and other visual data is some examples of the output. Now, when you hear people say client side or server side they are refering to how the online game (both client and server make the game) manages certain mechanisms in the game. An example of a client side hack would be a bot which is really just replacing your human input with that of simple AI or code. Another example is multi-client hacks. Other examples outside of conquer is Lambert hacks in Counter-Strike and Counter-Strike: Source. Lambert hacks are simply skins that are full bright, no shadows, and usually very bright colors. This makes other players more visible. Basically client side hacks are altered components of the client or the altering of memory loaded when the client is executed. This brings us to the problem with memory editors like cheat engine or injection of your own code (DLL injection). You see, when you edit memory you are editing the client which in mmorpgs doesn't handle any of the important parts of the game. You are simply fooling yourself. Now that doesn't mean memory editing doesn't work in ALL mmorpgs. Why is that? Well the game developers didn't use enough foresight in the design of their games to code the core parts of the game to be handled by the server.

SERVER

Now for the server. This is where all the important and valued components of the game are handled. The server can be viewed as a counterpart to the client or vice versa. The client and the server communicate with each other and together make the online game. As you may know, there tends to be multiple servers particularly in conquer, even other ones than the multiple servers you chose to create your characters on. By this I mean the login servers or possible even more, but that isn't relevant to this post. The server is the part of the game that determines the damage you deal with the proverbial "roll of the dice" or what item falls when you kill the creature. It also handles the locations of players in the game along with what stats, equipment, and money you have.

POSSIBLE HACKS

If you read above you'll see that the most desirable hacks are server side hacks. The problem is you can edit your memory to perform any of these hacks (except in rare occasions in some games when the server may not handle that component of the game). So what do you do?

Packet Editing. For those of you who don't know, Packets are messages transmitted via the network. Remember how I mentioned the server and client communicate. Well packets is how they do it. Alot of games tend to be vulnerable to packet editing. Unfortunately, Conquer has packet encryption.
What does that mean... Well unless you can find out their method... No server side hacks. So you can't have no gold hacks, infinite health, infinite mana, CP hacks, teleporting hacks.. etc (unless they slipped up on something and left some component client side).

CONCLUSION

Not all hacks are server side. This still leaves quite a few possible hacks. Of those are bots, auto-potters, aimbots, and possibly a few more client side enhancements.

There maybe a few things you might want to add or if you see any errors please let me know.

-Viren (v1rr3n)

[Ken]

Click the thanks button next time.