MQWarp/MQZone/MQGate Detector (Code Name: The VZTZ Hammer!)

spider661 · #1 06-28-2008, 02:04 PM

Quote:

case MQGhost: //Lieka: Not currently implemented, but the framework is in place - just needs detection scenarios identified

is this working now or no and if not has anyone found a way around it? i have seen a problem with it on my server as of late and would be nice to get told about it when im not online.

even if its just a simple check is pc close to a npc and what is the npc faction if its hostile there cheating i would be happy with that most the custom zones i use i just set all the npcs to the default hostile faction that npc loot editor sets it to. faction is 14329

KingMort · #2 06-30-2008, 03:13 PM

On behalf of Raid Addicts, I want to thank you for this fix. I am sure it will help a ton to stop cheaters on my server.. And I am sure it will also help my stress level.

Your a God send thanks, and keep up the good work !

King Mortenson
www.raidaddicts.org

KingMort · #3 07-10-2008, 08:28 PM

Seems that I am having zone looping issues in certain zones. Any Ideas why?

**trevius** · #4 07-10-2008, 09:50 PM

Your zone_points table isn't fully updated. Personally, I disabled the mqzone detection on my server so that I don't have to mess with it until either I or someone else gets all of the zone points added in and updated. The rest of it works fine. To disable mqzone detection, look at the rules posted for it.

KingMort · #5 07-12-2008, 04:04 PM

Yeah it is disabled but still in some zones people are going into loops, zoning in and out over and over or something... Only started happening after the code went in..

**TheLieka** · #6 07-12-2008, 07:58 PM

Never heard of this one. Is it only certain zones? If so, what zones?

Dax

**cavedude** · #7 07-12-2008, 08:00 PM

I had this looping problem with original code on the forums, however TGC has never had this issue with the altered version KLS put into the official code base. It was the incorrect zone_points in the DB causing it of course (putting in valid coords for both x,y,z, and target_x,y,z corrects this), and I believe KLS removed the zone check in the core code.