So there are some people running around with a plugin that detects you like a mile away even if your in a dungeon and keep vulning you.

They are detecting you even outside of the range of onplayercreate event being called in my plugin. I read in the documenation you can increase the range of the detection but this still doesn't appear to work.

myACF.ocm = ocmPK
myACF.distMax = 1000.0;
var coaco = myACF.CoacoGet();
var e = new Enumerator(coaco);
var aco;
for (; !e.atEnd(); e.moveNext())
{
aco = e.item();
MyHandlers_OnObjectCreatePlayer(aco);
}

Any ideas? I detect players but the range still isn't greater then that of what is picked up when i register a handler.

Thanks.

That's not what ACF.distMax is for. The server decides what objects your client knows about and when you find out about them. ACF is just a way of enumerating subsets of those objects. It's not a way of fooling the server into telling you about objects it wouldn't ordinarily tell you about.

There is no way in SkunkWorks to do what you want to do, nor will there be in the future. I don't know how those remote-vulning plugins work, and I'm not really interested in finding out, since Turbine considers it cheating and has banned people for doing it.

Interesting, does Turbine publish the spec. for their protocol? I mean is this documented information? If not I'm curious how they would be able to get it besides doing a lot of work of sniffing the communication between the client and server and then going through the work of decoding/decrypting it however it is done unless it is in plain text lol.