Macroquest

[Rogean]

Having it loaded will automatically inject itself into any EQ Client it finds that its compatible with. If it injects, we will detect it, and theres no excuse; I'll inject your face with a ban.

[Ferok]

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

I'll inject your face

Hello, new signature!

[Loke]

Originally Posted by Crone [You must be logged in to view images. Log in or Register.]

If you have no idea how the program works, or what it does, why are you using it?

You use things everyday that you don't know how they work. This is a ridiculous statement. There is a difference between knowing how to work something and knowing how something works...

I used macroquest a few times on live towards the end when I really just didn't care (mostly mayong server, since let's be honestly, that server was a joke)... I have no idea how the program works, and honestly probably only know how to use it to 1/10th of it's capacity.. but that doesn't mean it didn't make my life way easier and enable me to do things that I wouldn't have been able to do as efficiently without it.

As far as all the people hating on this guy, simmer down. The guy should be commended for going through the trouble of educating himself so as to follow the rules of P99. I bet 1/2 of the people on P99 have either used, or knowingly benefited from someone using MQ... hell there are people in this thread that fit that bill. Personally, I've got no problem with MQ as long as it's not being used on P99, and props to you Danny for taking the effort to make sure you're following the rules.

My advice would be to just ensure MQ isn't running prior to launching EQ. I'm pretty sure MQ would need to be actively running for it to be detected; although you might wanna wait for Rogean to reply as he'd surely have the definitive answer.

[Hasbinbad]

Originally Posted by Loke [You must be logged in to view images. Log in or Register.]

You use things everyday that you don't know how they work. This is a ridiculous statement. There is a difference between knowing how to work something and knowing how something works..

True the fuck out of that!! You (hopefully) use soap every day, but do any of you know the first thing about bubble science? It's a hugely complex discipline, which requires a solid understanding of physics, chemistry, and mathematics to even begin to comprehend the basics.

One of my favorite sayings, from some comedian (paraphrased):

I'll drop you off alone in the jungle with a knife, and see how long it takes you to send me an email.

[guineapig]

Originally Posted by Ferok [You must be logged in to view images. Log in or Register.]

Hello, new signature!

You beat me to it!.

[azeth]

Can someone post an SS of what macroquest shows you btw? I've never really looked into/seen what benefit/cheat it provides the user.

edit: i believe im thinking of ShowEQ(?) that shows you loot tables and mob health etc. Macroquest is the /command program right?

[atvaata]

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

Having it loaded will automatically inject itself into any EQ Client it finds that its compatible with. If it injects, we will detect it, and theres no excuse; I'll inject your face with a ban.

inject me with your manlyness.

[Rogean]

/unload doesn't prevent it from injecting into new clients when they are opened; you would need to exit it from the taskbar.

[atvaata]

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

/unload doesn't prevent it from injecting into new clients when they are opened; you would need to exit it from the taskbar.

damnit rogean you spoiled my victory.

[Itchybottom]

What sucks about MacroQuest2, despite what Rogean has claimed, is that it isn't really detectable. There are certain behaviors on clients that make MacroQuest2 stand out (depending on what plug-ins are being utilized, actions per minute, all of that jazz), but there isn't some magical process monitoring going on here. Nor does an established connection, or a connection being made from the EverQuest client differ from a regular client for the most part. The exception however is when you start detouring memory addresses, such as run speed and have that locked during a zone event. That's not MacroQuest2 specific though, that can be done with any cheat toolset.

Hackers log entires will be target distance, client initiated zone requests, large movement requests, and sending OP_SpawnAppearance packets. It's pure gut instinct banning someone on an EQEMU server otherwise.

With that said, I really wish I never released my ProjectEQ build and have often times contemplated adding disable checks for various servers. However, more communities have sprung up that provide source code and compiles for EQEMU specifically, and they would in turn just use someone else's compile.

I'm open to ideas on how to prevent MacroQuest2 on EQEMU. I've already stated in another thread what MQ2 can and can't handle buffer wise, that the client is oblivious to. I've been wanting MQ2 gone since late 2007 after people on ProjectEQ started running 24+ characters and causing zone crashes. Third-party injection tools are really the first line of defense against this, but users like me have trust issues without source code available to such a beast, or at least enough time to set break points in a debugger and trace the stack to figure out what the hell said third-party application is doing on my PC. Maybe a binary diff and patch for eqgame.exe could be released, that changes some of the memory regions and behavior in client? That'd knock out nearly 99% of the people that use MacroQuest2, because their offsets would no longer function. That amount of code caves though... Good lord.

And to clarify, I don't mean just changing offsets, I mean changing the way certain aspects of the client function, and changing it server side to reflect the population value of data.