MacroQuest64

Im honestly impressed by what you have accomplished to do with MacroQuest, finding out the memory offsets must have been a bitch.

Speaking of memory offsets - $char(mana,xxx) would be awesome to have.

Anyway, id like to point out some possible security Risks when running MacroQuest (Stuff that could get you banned that is)
Please correct me if im wrong.

1. running tasks
Upon starting EQ, VI had some code implemented to send a list of running threads to them to see if people are using 3rd party programs while playing.
I know they stopped doing so because it upset a lot of players, but its not said that they wont activate it again.

2. chat messages
When you petition, or whenever a gm wants to - he can get a dump off your current chat window. Seeing all the Macroquest messages there - even only the enchanced /who list could be deadly to your character.
If i see it right, the macroquest messages go the same way as normal chat - so a gm will see those as well !

other than these, i cant think of any problems when running MacroQuest with well written scripts and with one eye on your screen.

keep up the good work :)

Singh

Macroquest seems to be very very safe. It is as safe as EQW which if Verant could find out about there would close to a thousand or so bannings :). Also I am still new with Macroquest but I think it only changes stuff like the /who list on your side. It will not show up to anyone esle. It actually changes what EQ is showing you client side. Similar to ShowEQ....but not really. So if a GM would to get your chat log they would see what the server is sending you. They would not see what macroquest is picking up from the server (passivly) and just "enjecting" into your client. It woulld be the same as if you had a whole different window that would just show that data. Plasmic just made it easier and put it into the EQ program. I think that is how it works correct me if I am wrong.

It takes a lot more then using something then Macroquest to get banned. I would know :) I have been banned before......but only for offset hacking... With macroquest though there isnt really that big of a need to offset hack other then just on test account for fun

Again someone who knows a little more about the program correct me if I am wrong.

Everguide

yes, VI currently has no way of detecting what threads are running on your machine.
In the past, they already sent thread information to their servers though - and they can reactivate it again whenever they want.
This goes for eqw as well of course. Doesnt apply to showEQ obviously.

reg. the chat messages, it was officially stated that gms see your chatbox text on request or when you petition.
To the best of my knowledge this also applies to MacroQuest messages and all text altered by MQ.

Of course i might be wrong on that subject - but a quick look at the source tells me that MQ messages use the same queue as EQ messages.

well, hope im wrong. Just wanted to bring this up.

Singh

You are correct, if a GM uses the command, he can see your chatwindow and note everything it says, including MacroQuest stuff. Therefore be carefull when /petitioning, /reporting, giving out screen shots, or dealing with GMs.

However, MQ Does *not* change any memory offsets/addresses, it's simply a DLL injector, with some added sniffing/reading to know some things. Doesn't change a single offset.

As far as scanning tasklists... this is both illegal and detectable... The illegal part is a debate that has been going on since they tried it, but I guarantee if I ever caught them doing that, I would take it to court. What I am actively running on my computer is *MY* business. Just like what I'm watching on TV is not my next-door-neighbor or my Plumbers business. If I was listening to the radio, 97.3FM, and some other station put a device outside my house scanning frequencies to see what radio stations I listen to, I would take them to court as well.

And besides that, they not only must change their EULA first, they will probably add it to the patch message as well, giving everyone ample warning before scanning tasklists.
Plus, I have programs running at all times that monitor *exactly* what my computer is doing, if they scanned my tasklist, I guarantee I would know about it. In fact, if I even take a screenshot in game, it pops up with a warning saying a file was created, and what it put into the file (a dump of my DirectX screen), therefore I'd know if EQ did anything unusual almost immediately.

- Icon