Offset checking

Doodman · Post by **Doodman** » Mon Jun 09, 2003 10:45 pm

I used MQ before they turned off the old UI completely and then VI was going to (or did) implement some offset checking to prevent trainers and things like MQ.

Does anyone know if they are still doing this? And is MQ doing anything to not be detected?

I'd love to begin using MQ again, but just wondering about what VI might be doing to combat it.

Thanks.

Valerian · Post by **Valerian** » Mon Jun 09, 2003 11:19 pm

1) Yes. they are still doing it.
2) Yes. we are.
3) First off, VI doesn't own EverQuest anymore, Sony Online Entertainment bought EverQuest from VI. SOE currently has three memory checking functions inside eqgame.exe, that will scan memory either on request from the server, or at predetermined times, and report the findings back to the server. We have detoured those memory checker functions, and report to the server exactly what it would see if your client memory were unmodified.

MQ is just as "safe" as it used to be (safer, in fact.. those memory checking functions have been around a lot longer than we thought, and we only noticed them when they started disconnecting users). However, "safe" is a relative term, the same old safety issues exist.. e.g. don't do anything stupid, no unattended macroing, be careful with using /target out of sight range, etc.

Doodman · Post by **Doodman** » Tue Jun 10, 2003 12:24 am

Well, then, in EverQuest style, let me say:

Woot! Gratz!

vzmule · Post by **vzmule** » Tue Jun 10, 2003 12:42 am

That's partially true. Verant Interactive was acquired by Sony Pictures Digital Entertainment (SPDE) of the Sony Corporation, forming their online gaming division, Sony Online Entertainment (SOE), which later was moved from Sony Pictures Digital Entertainment to being under Sony Computer Entertainment America Inc.

So, Sony didn't buy EQ from Verant...They bought Verant. hehe.

There, more info about it than you could ever possibly want to know.

I unfortunately own stock.

DreamKing · Post by **DreamKing** » Tue Jun 10, 2003 12:51 am

However, "safe" is a relative term, the same old safety issues exist.. e.g. don't do anything stupid, no unattended macroing, be careful with using /target out of sight range, etc.

Would there be a short list of stupid things not to do? Other than the obvious like running it unattended. I had used /target a few times before reading that it was detectable after which I stopped. Was wondering if there were other not-so-obvious things to look out for. Perhaps adding a short paragraph in the manual would be good.

Valerian · Post by **Valerian** » Tue Jun 10, 2003 8:58 am

well, the things not to do are mostly common sense.

do nothing that draws attention to you

if possible keep all macro output out of your chat windows (use the telnet server or something for macro output) since GMs can (possibly?) read text from your buffer... or you could be careless and send a /report LameKSingUser with macro-type output, which can then get you in trouble. (for those that don't know, /report now sends 20 lines starting at the top visible line in the window you're currently viewing)

Definately no unattended macroing of any kind, unless it's something that's not visible to anyone and in some out of the way locale... (standing around working sneak, or mend, or sense heading for example) even such as this may not be very safe, but just have a believable afk message up or something

for maximum safety, tell no-one. not even your closest friends... never know when something may slip from someone's mouth into the wrong ears "You say, 'ryeah, well MacroQuest RoXX0rZ'"

I'm sure others could think of more dumb things not to do, but that's all that comes to mind after a long night of work