The detection in question started around Aradune. I ended up changing my window title to "Jade47 - Onlyfans" and named the program Mcafee.exe or something along those lines. Never got tripped up because I fact checked, and wanted to make sure I covered my bases by not telling anyone. Glad I did, because now I can point to the exact reason people got suspended in comparison to me.OFC, used it back on agnarr alot and think i booted up mqnext on aradune when that came out. All different accounts then the one that got suspended though, if they IP trace off of stuff from years ago...sure i guess.
I think the use of MQ increased after it went open source. And this is a reaction to that increase. Getting banned can lead to either repeating the offense or, as they hope, stopping that person from cheating again.
The breaking of the MQ agreement and keeping MQ off of TLP servers is what prompted Jenn and crew to crack down on it. I believe that silent agreement was made between Daybreak & Redguides, MMOBugs and the MQ team. Believe they met eqmule & co in person to actually physically sign the agreement.
They said at the start of the agreement, if it was not honored, they'd get increasingly nasty with hidden detection methods that they didn't want to fight the developers of MQ on. It would have been mutually beneficial to allow MQ only on live servers and for MQ devs to leave TLP alone. Once Next was made public, I imagine they believe that the agreement wasn't honored anymore, and reacted accordingly.
For the record I still find it funny that MySEQ is what did people in and not MQNext. I'm fairly certain they have limited capacity to detect MQNext still given that it hides from existing detection methods. It's just behavior analysis that ends up getting MQNext folks in trouble, or they run MySEQ alongside MQNext and that leads to them getting flagged.
This is a conversation ingame from EQ2 where "Windstalker" (Holly's userame) talked in open channels in EQ2 (Stormhold TLE) about MQ, in 2015, around the same time as the agreement.
Hate to break it to you, but it's more likely it was MySEQ that did you in at this point than MQNext. MQNext hides itself, not unrelated processes to MQNext.There's no way it could be the MySEQ...
Last edited: