Evac and #zone problems?

[WildcardX]

We are working diligently towards adding "similar" functionality to the 6.2 client, but at this time it doesn't look like it will be equal functionality. This is because the 6.2 client isn't responding to a packet like the Titanium client is that allowed me to add the zoning feature for evac/succor that is consistent with live.

To add this same level of functionality to the 6.2 client, we'd need to discover a packet that we do not have.

I suspect the best we can do for the 6.2 client is to add an intra-zone movement to the safe coords that doesn't cause a proper zoning of the 6.2 client. No doubt this will mean, that like before, aggro will not be cleared in all situations for players using the 6.2 client.

What does this have to do with the #zone command you ask? The changes I made send a different packed if you just type #zone nexus depending if you are in the nexus zone or not.

Anyway, I hope those of you who have the 6.2 client understand that there may be some limitations in this matter and we do not want to dummy down the new functionality we have achieved for the Titanium client to accommodate the 6.2 client.