[TheLieka]

We've got code in place to prevent MQ2 /warp and /zone functions. The anti-/warp code isn't hard, but it does take some tweaking, as you've got to allow a certain amount of leeway for lag. We have also had issues with zones that use intra-zone portals (such as Paineel, Felwitheb, and one of the Freeports), but I believe that Null (one of our superdevs) was able to resolve that. I'll take a look at it. Many of the variables are currently hardcoded, so I'd need to integrate it into the Rules System before I release it.

The anti-/zone code (though fantastic) relies on your zone_points table being fully populated with x, y, z in addition to the target_x, target_y, target_z. I'm hesitant to post it because I don't want 10,000 PMs about why people are getting attacked by the hack detector, when it's related to their database.

I don't have the zone_points table fully populated, as my server currently only supports Classic, Plane of Fear, Plane of Hate, and Plane of Sky, so if you wanted to allow access all the way through PoP, you'd have a lot of work to do in getting the zone_points table up to date.

If you guys want the code, I'm happy to post it, but I am afraid that it will generate more work than most people will be willing to do.

Thanks,
Dax