MacroQuest64

Just wondering,

how safe is this? Can Verant see the modified commands? can they see that we are running macroquest?

I got a couple of warnings on my account already, and try to prevent getting more of them.

There are 3 things to consider:
1. Do they detect programs hooking into the client?
Nope, or all EQW users would have been banned a long time ago.

2. What happens when you type a /command?
The client processes the command. If it's a known command, it acts upon it and then continues. If it isn't a known command, the client asks the server what to do with it. Since MacroQuest makes all of it's commands known to the command interpreter (they look just like normal commands to the client), the server never sees them.

3. Can they see?
Most GMs to have eyes, and if they see you do that same action for 60 hours in a row, they might get suspicious. On the other hand, I have a char that has over 100 hrs of cheese making without an noticable GM activity.

Salutations,
One must remember to make sure MacroQuest is running, otherwise verant will know you are using

[quote="Plazmic"]
3. Can they see?
Most GMs to have eyes, and if they see you do that same action for 60 hours in a row, they might get suspicious. On the other hand, I have a char that has over 100 hrs of cheese making without an noticable GM activity.[/quote]

Cheese-making Macro? Is that included (not as i can see) or will u post it here? :)

// Yocal

cheese.mac ...
I accidentally yanked it from one of the builds (6-12 i think) but put it back in after.

EQW != MacroQuest...

EQW does only hijack the dinput/DX8. Macroquest actually _hacks_ the EQ Client (for /whot and so on...). That _is_ detectable, and people have been banned for using those hacks.

Question is, why not create a version that doesn't touch the client memory (no write, just read, reinject via dinput8), and is thus a bit more limited in functionality, but a whole lot safer to use? I'd be very glad to lose /whot and /help if I can use the program without fear :)

Cheers

MacroQuest does not _hack_ the EQ Client... /whot and other enhanced commands are all internal to MacroQuest, the original commands are still exactly where the client thinks they are (click who on the lower right side of the screen and it will use the original who command).

EQW hijacks dinput/dx8 and looks for a couple keystrokes along with tampering with the mouse button states.

MacroQuest hijacks dinput/command list and inserts a couple keystrokes and mouse clicks.

EQW doesnt write in the allocated memory space of EQ.
MQ does, from a quick view over the sourcecode at least to output some text to the user window (why not to a separate window, most folks use eqw anyway :) - I also recon you write the "Target" directly into memory instead of injecting the keysequence "/target blablah" to EQ. Most of the other stuff (mousclicking, keyboard strokes) can be done via dinput injecting, which is what you do, as far as I have seen.

I think I'll have some time in the near future to go over the sourcecode in more detail soon. Other than the memory write stuff - my deepest respect for this, the sourcecode is very good and structured.

BTW, /sendkey down ctrl doesn't work here... :) neither with nor without eqw.

Cheers

Try a quick check of EQW's imports... ReadProcessMemory and WriteProcessMemory are there...
The client's memory space is where the dinput function pointers are stored. EQW overwrites them, which is exactly what you claim it doesn't do (writing to the client's memory space)

If /sendkey down ctrl didn't work, none of the tradeskill macros would work...

They don't for me - at least not the way it should be...I have to /macro bla, then the amout selector (at 20) pops up at the frist item, I have to press CTRL, move the slider to 1, and then click ok, and from then on it works, as long as I keep CTRL pressed myself...strange I know, and I have no idea why it behaves like that...

I'd like to carry this on in a PM if possible.

gimme a sec

Salutations,
I would prefer if you post the technical stuff on how mq injects eqlib.dll into eq on the forum, for future reference of some kind (search feature!)

Allocate memory in eqgame client space.
copy a function from macroquest.exe into that space
create a remote thread in eqgame running that function.
that function loads eqlib and starts running InsertCommands.