MacroQuest64

I recently had an account banned for "The use of the third party program: Macroquest" Note: I never once ran a macro. The only functions I used were /target and /face - I always used it conservetively, never talked about it, never used it around other people. The account was banned a week after the last use of Macroquest.
Use at your own risk

I wonder if Gotar lives i nthe San Diego area? =)

har har, just trying to help out, they positively have a way to detect MQ w/o seeing a macro running with the current "gm sending you tells when your afk" theory

If your not doing anything and are afk what do they have on you? you were probably banned for being an idiot and doing an AFK macro.

He said he never once used a macro just /face and /target sometimes.

Just over the last little while ive had zone alarm pop ups asking me if I want to run eqgame.exe as a server when I start EQ, I always just say no, I dunno why it would want to run as a server.

thank you ex for pointing that out for him :P

Gotar wrote:I recently had an account banned for "The use of the third party program: Macroquest" Note: I never once ran a macro. The only functions I used were /target and /face - I always used it conservetively, never talked about it, never used it around other people. The account was banned a week after the last use of Macroquest.
Use at your own risk

This has always been use at your own risk, sorry they found out but we are all aware of the risk.

Being you only use target and face you probly could debate it pretty easily.

I dont buy it. I run certain macros for 12 hours at a time and have for months ... never had a problem. I three box using custom macros to assist me. Works great with new UI and I never need a /click to make things work. I never play unattended and have run into GMs and guides from time to time and not once has there been a problem. I also am into ShowEQ and have a real good handle on the server client communications going on. I see no way that they can detect MQ or anyother program and I know for certain that no process information is sent to the servers from the client. MQ uses the information sent to the client in a different way .. it changes the client funtionality. Nothing extra is sent from the client to the server unless I have totaly missed something in the thousands of packet captures I have done.

This looks like a bogus scare tactic to me.

To the person worried about the 'eq as a server' thing from zonealarm:

When you run macroquest, it injects a DLL into EQ's process space, starting a thread for that DLL to execute it's stuff. As far as the computer is concerned, when macroquest attempts to start up it's irc server, and when macroquest does ANYTHING else, it's really eqgame.exe doing it through one of it's threads.

In other words, the message your getting is because MQ wants to act as a telnet server. If you want to check and make sure, look in your eqgame.ini and you'll find a port there for the telnet server. Next time it pops up asking about eq wanting to be a server, check the port it's trying to communicate on and I'll bet you money it's the same as what's listed in your eqgame.ini

To the person saying there's no way to detect MQ: I'm sorry my friend, but we've had numerous discussions on this topic ... and while we believe that Verant hasn't implemented any of the legal means of detecting MQ, it doesn't mean that it isn't possible to *legally* detect the use of MQ, without us knowing about it. In fact, I know of at least one method that would be very easy, not that I'm willing to detail in a public forum exactly how it might be done. No sense in giving them ideas ;)

-Phantal

If you use /target to target a mob that you couldn't possibly see then you increase the risk of being detected. Although SoE are not monitoring absolutly everything if a player /petitioned you for something (might not even be MQ related) they could have easily set up logging on your char. They would only need a couple of instances of you targeting a mob outside your visible radius to know your doing something that contravenes (sp?) the EULA.

I've had an account banned for mem hacking once.

However, they just said I was banned for use of a 3rd party product. They didn't say the product name. I think this is a bogus scare tactic.

Your missing my point. I am not saying that SoE can not detect MQ. I am saying that the client is not sending system process information to the server. SoE is not pulling extra data from the client in an effort to detect 3rd party software. If someone gets banned for using MQ, its because they did something ingame that is not possable using an unmodified client. MQ needs a safe(er) mode that would disable out of range or not in line of sight target selection.

MQ does not need a safe(er) mode. You can use the /target command with a distance specified. So if you think that is a problem then just find out the max distance you can normally target and use that as a parameter.

Thats how I use /target ... just an idea.

bet he was doing /face alot while sitting or fd hahaha