I sent this to LethalEncounter directly, but he misunderstood my reasons.
I recommend no one use the packet collector. They have, or will be implementing countermeasures.
This is not because of the packet collector but because of other memory-reading and monitoring methods which people cheating with high-speed movement are using, as well as other cheats.

Hail the mighty cheater, who cannot even play video games fairly.
Thanks for the heads up.

Just interested, what kind of counter measures? You mean some kind of scanner in the client?

I'm not certain, but if I wanted to counteract the botting programs which read and modify process memory to look at or change their world, I'd do this:
(1) Find anyone attempting to attach to this process.
(2) Find if there are any breakpoints set. That is, if we are running under a debugger.
(3) Have a thread (or unrelated functions) call a memory verification routine which did a CRC or other checksum against known values, for certain parts of their application.
I'm certain Sony programmers are clever, I'm just not certain they are devious:
(4) Let the client have bogus values which appear right, but will run people off cliffs or make it obvious they are cheating. They did this with EQ1 using evil easter eggs: talk about things that only cheaters can see, and you get nailed.
(5) Embed a known and trusted RSA public key in the server, and make it fairly hard to find using XOR tricks or the like.

let me ask you, what makes you think that, because of the dev chat?

I think they know better than us, trust me.

Evil Easter Eggs....now that's cool

Arremis wrote:Evil Easter Eggs....now that's cool

Are they the ones that you cant find cause they keep getting up and running to the spots you've already checked?