Position Packet and Tracking Packet

[jimbo]

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

 

[nijhal]

*Scratches head like a confused ape*

Uhhhhhhhhhhh

Wut dis mean boss?

(excuse my light humor, but I dont really know what this means, care to tell me if it means warping and or anything like that is detectable now?)

 

[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 course. For example, the movement-type byte in the old movement_tracking packet could be overwritten with a 2 whenever it was a 3 in order to hide warping. Now we just gotta figure out what the hell they are doing with this new gigantic one.

--Jimbo

 

[nijhal]

So basicly the packet used to be a one pound box that was light brown and we changed to to dark brown so warping could not be so detectable.

But now they changed the box from one pound to 15 pounds?

That the basic analogy?

 

[odessa]

My friend, don't embarrass yourself

change this -
send_message(EQADDR_GWORLD,PacketType,pData,Length,TRUE);
to this -
send_message(pData,Length,EQADDR_GWORLD,PacketType,TRUE);

hey what do you know....keeping MQ2 updated ftw

 

[jimbo]

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