Out of sequence target cursor issue

[MuadDib]

It's just informative. The best way to battle this, is using #Cprop checks for checking if client has existing cursor, removed after the cursor call in a script.

[Repsak]

That would require that we/I add that in every script using Target(), polluting the script base with something basically unnecessarily.

The hook feature would allow us/me to handle this problem in a single script, without polluting the already existing scripts base

I don’t know how demanding it is to make a hook for this in the core, but there is no doubt a hook is the best solution. Just give us a character ref and messageType.

[CWO]

Thats how I handle it right now, a packethook. I set it to set a prop on someone when either a regular target packet or a Multi placement packet is sent and check for that prop and erase it on the target return packet. If the prop isnt there when they return target, then I send them a warning about targeting when not having a target and stop the packet from going to the core.

[Repsak]

Of course, why did'nt I think of that, to hook the Target cursor.

Thanks.