Recent content by jimbo

JCasper, Could you clarify the following please? Faking a received packet or a sent packet? And is it not the case that all packet sending was obfuscated? I haven't had a chance to delve into that yet. :( Thanks, Jimbo

Because they are the Network Nazis. It is just what they do. They block everything that might consume the most infinitesimal amount of their precious bandwidth. If it isn't work-related, then don't do it on our network... And no, you may not have a connection to anyone elses network. Now go...

Re: RedQuest v9.0 (works with 4/18/07 patch) It isn't new encryption. Just new opcodes. Whew.... ;) --Jimbo edit: nope. I stand corrected. my new opcodes lasted only until i logged off and back on again. then they were changed again. neat! :rolleyes:

Re: RedQuest v9.0 (works with 4/18/07 patch) 404 on me for the source code :(

Re: RedQuest v8.2 (For 04/05/07 patch) Nice work RQ. I'm glad to have all the source back in one spot so I can keep mine consistent with the baseline. Now I just need to figure out this lib linkage. --jimbo

It is open source. Do what you like with it TP. --jimbo

Someone asked me (via pm) for an example of how to use this. So here is a simple example: PLUGIN_API BOOL OnSendPacket(DWORD Type, PVOID Packet, DWORD Size) { //if it is a movement tracking packet... if (Type == PKT_MOVEMENT_TRACKING) { sprintf(Msg, "movement tracking packet\n")...

The movement tracking packet consists of one or more segments of 17 bytes, plus one byte tacked onto the end. That last byte seems so simple now, but it was a big pain in the ass to figure out. When the last movement_type was 2 (stationary), the last byte is just a copy of the first byte of...

I have found pieces of the PacketAPI in several places, but never the whole enchilada at once. So I have pieced it all together and here it is, with the fix for EQ having moved the parameters around in their SendPacket function. If you see any bugs, please let me know. It is working for my...

Odessa, Literal Answer: old packet --> new packet unsigned short SpawnID; unchanged unsigned short TimeStamp; unchanged int ZHeading:12; 11 bits instead of 12 for range of -512 to 512 unsigned int HeadingRemainder:2;\ unsigned int Heading:10; > unknown 21 bits instead of 20 unsigned int...

I spent an ass-load of time figuring this out. So throw me a red cent if you find it helpful. Or if you know the two pieces of it that I don't know (Unknown2 and Unknown8), give me those instead. :) I think it is complete enough for most purposes now though. typedef struct _PositionPacket...

nijal, That was my theory, but as odessa points out, I had a big oops in my packet sniffer. So I was FOS. :o Thanks for the pointer odessa. You da man! (and I'm glad you are back) --jimbo

Warping has always been detectable. If you are going to write position-spoofing plugins of any kind (like ghost, etc), you need to know these two packets. This will only be of use to plugin authors. We would all like to know what all is being tracked in order to write safer plugins, of...

All this crap is wrong. EQ changed the ordering of some parameters that it sends to a function, and it led me down the wrong path for about five hours of work. :o All the irrelevant, misleading WRONG stuff deleted to avoid confusion.--Jimbo

Bump. I have the same question. I am just getting ready to install one and join in. I used Ventrilo for a bit long ago, but it required a lot of maintenance and I eventually quit repairing it. Hopefully it has improved. I would use whichever one requires less-frequent jacking-with, even...