Printable View
anyone feel like giving me a crash course in Gaia Games packet editing? I've never experimented with editing packets before, but thought it seemed like an interesting adventure.
Anyone?
Also, if anyone is up for some haax, I have a few questions about Gaia that I need your opinions on.
What don't you understand? It's a simple model. Client sends data. Server receives data and sends data back to client. Client receives it (in this case WPE or the packet editor in question acts as a middleman). Client acts on that data if programmed to. That's basically the entire cycle of the client-server interaction. These abstract events happen constantly as you're in the environment.Quote:
Originally Posted by Flareboy323
On the other hand, I'm writing an open source client for Towns 2.0 soon. Perhaps that will assist in your endeavors. As for "haxx", not really interested but what do you have in mind? What do you need opinions on?
I understand all of that just fine. Like, what are the random packets that just contain hex that translates to like:Quote:
Originally Posted by The Unintelligible
a....a....hg.....43.....c...56....
Not even words or anything. How could you edit packets to, say, teleport yourself places maybe. Couldn't that be done if it just sends a packet with X and Y coords?
It's magic. We programmers are also Wizards. You muggles wouldn't understand.Quote:
Originally Posted by Flareboy323
-_- are they encoded somehow?Quote:
Originally Posted by Artificial
He just told you magic.Quote:
Originally Posted by Flareboy323
Your best bet is to learn to read Tarot and divine the meanings from that.
What he said.Quote:
Originally Posted by Artificial
God. I come here for some help, and all I get is complete denial -_- I don't understand why people can't be serious once in a while. Think about it this way: If you never teach anyone else how to hack Gaia or make bots or FLPs, what happens when you stop? The next generation of tinkerers, hackers, and programmers will have to completely re-invent the wheel. This makes for no innovation or anything. If you teach the next generation how to make the wheel before quitting, they can improve on it's design, have more advanced tactics on making it faster and quicker, and maybe even revolutionize it completely, based off of your design.Quote:
Originally Posted by The Unintelligible
lol I don't care for the "next generation" of "tinkerers," "hackers," and "programmers." I don't care for this stuff at all. To be honest, none of this stuff is even going to help you. You'd be better off simply learning how to program rather than doing this (or doing something productive outside of the field of computers for that matter).Quote:
Originally Posted by Flareboy323
Be grateful I'm even sparing time to appeal to your question.
Weren't you the one who:Quote:
Originally Posted by Flareboy323
a. Started his own Gaia Online cheating forum.
b. Openly admitted to seeking out the leaked contents of our programmers area.
Why would I trust you with any form of knowledge? I'd probably just see it benefit EBfagsU
Should just throw the kid a couple sauces Artificial. I doubt he'd learn from them though. I mean, you've already released a fair amount of things as far as I know. Did he learn from them? Nope. Not to my knowledge he hasn't.
Ok, then how about this. I've never used WPE, so I'm not 100% sure exactly how they display packet information, but regardless of that, you need to read up on TCP/IP: Transmission Control Protocol - Wikipedia, the free encyclopedia. The data which is sent and received in these packets is ultimately up to the discretion of the server/client. You're wondering why you don't see English within these packets? It would be redundant to send something like 'walk left' every time you wanted to walk left. It would be much easier to send something like an integer value (or even set certain packet flags), which the client can interpret as walking left. That's just a data redundancy issue. If a game sends packets frequently, then the longer the packets, obviously the less efficient it's going to be (which is why they'll mostly try to shorten it as much as possible, and let the client deal with it instead).
While stumbling around in WPE (or something like Wireshark) may allow you to empirically discover the nature and formatting of the packets, if you truly want to find out how they're structured, you're better off decompiling the .swf file and taking a look at the corresponding .as files.
+rep. Good work explaining it to him and all. Pretty much most of the time you'll see data serialized in some form rather than being sent in a format harder for the client/server to process.Quote:
Originally Posted by Artificial
You see a bunch of incoherent and seemingly useless data? That information actually has meaning. Sometimes it's encrypted, but a lot of the time packets are just represented differently than instructions like "exit room". Decompile the client source, find out what each piece of information means and what it does. Experiment. Go from there.