The State of MacroQuest - 2/24/03

lifewolf · Post by **lifewolf** » Fri Feb 28, 2003 11:00 am

Fixing those ghettofully without using detours and about 85% of the MQ source would be easy for any moderate to advanced coder. Im not sure that I wish to contribute anymore, though, as it seems Plaz died and left and left a less-inteligent mamal as myself in charge..

kaz · Post by **kaz** » Fri Feb 28, 2003 2:44 pm

lifewolf · Post by **lifewolf** » Fri Feb 28, 2003 5:26 pm

kaz wrote:the only way to fix these without using detours would be for instance to write a 2nd program with its own interface window that you typed into and that tried to read eq's memory and show you what you wanted.

Yeah that

kaz wrote:the problem there is that mq reads all that data while in a detour so its access is sync'd but if you tried to access that data from say a 2nd program you'd have memory consistancy issues to deal with.

Freeze, or deathly lag out EQ for the second or so the memory reading takes... Like GrabIt for D2 except you would need to find an external way to do it since it also uses hooks and DLL Injection.

Plus I doubt that would ammount to more than a 1% innacuracy anyway, and if it did, you could write it to pull information 3, 5, 7,.. times from memory without lagging EQ, sort it, and remove the minority of matches (like ID 317 being a monster the first two times and a corpse the last 5) .....

L124RD · Post by **L124RD** » Fri Feb 28, 2003 9:32 pm

Salutations,

Lifewolf wrote:all custom mq commands rely on the use of detours

true, but that has nothing to do with the SMURFING CODE! the detour injection happens where you can easily figure out and add one line of code to make your command a part of MQ and then simply understanding the way the structs are together so you can make it do things. same with adding variables. If you wanted to make it still work in MQ then that can be said as easy (i htink maybe) as well, simply type in yer /command then hit a character code that doesn't exist in font (alt+b) I don't know hwo EQ handles it but there is apossiblility there is now a 0x01 after /command, so the 2nd party app searches for the text in teh box and fins /command + 0x01 and vwalla, you have a "working" mq thing. *sighs*

Edit: That concept sucks ass, thats how I would have done it pre-MQ back when I tried to hack my friends account with a trainer I wrote in visual basic (censor: i'm an idiot; please ignore me)

roguish · Post by **roguish** » Sat Mar 01, 2003 8:05 pm

A long time ago I wrote some COM like objects for Macroquest when it was the only game in town. I had written two versions

1. One version was a memory sniffer that read loc of char and then sent that to Xylobot via UDP. Xylobot then attempted to turn the character to the right orientation or move the character to the right position. It was nowhere near as elegant as /face and UP UP etc., but it worked ok for MELEE.

2. Another was a rewrite of ShowEQ that did the same thing by UDP to Xylo.

In those days I was interested in melee movement. These days, frankly, all I need are health values. I would like as well the ID of the target, etc., but realize that is beyond this at this juncture.

So, a memory sniffer that found and sent to Xylobot the following would be beneficial:

1. Health and mana of target and group members
2. Loc of group members health/mana
3. Health of pet(s)

Otherwise many other things are programmable in Xylo. However, I do recall the movement was nowhere near as smooth there as it is in MQ... expect a bumby ride if you are wanting to do melee movement.