Interact Issues VMT

[HeroXx]

Hello everyone

I have been slogging away at my little harvest bot and everything is looking good apart from the final piece - harvesting!

I am unable to get this working, I have double checked all values being passed to it and the offsets and they all look fine, I don't get a crash or anything.

private void moveToHarvest(uint obj)
        {
            uint codeCave = wow.AllocateMemory();
            uint VMT44 = wow.ReadUInt(wow.ReadUInt(obj) + (44 * 4));
            wow.Asm.Clear();
            wow.Asm.AddLine("fs mov eax, [0x2C]");
            wow.Asm.AddLine("mov eax, [eax]");
            wow.Asm.AddLine("add eax, 0x10");
            wow.Asm.AddLine("mov dword [eax], {0}", ObjectManager.CurrentManager);
            wow.Asm.AddLine("mov ecx, {0}", obj);
            wow.Asm.AddLine("call {0}", VMT44);
            wow.Asm.AddLine("retn");
            wow.Asm.InjectAndExecute(codeCave);
            wow.FreeMemory(codeCave);
        }

Any help is greatly appreciated.

[Cromon]

Aint Interact just.. err.. interacting with the object and not moving to it? Im not sure, its a long time i used injected code...

[HeroXx]

That's what I thought although I have another function handling the movement to the node, after it reaches the node (3.6 distance) the harvest function is called. I know the function name is a little misleading.

[Evieh]

Because interact is 45 not 44.

[HeroXx]

Thanks for the update on the offset there, unfortunately I am still getting no interaction.

[Evieh]

Ehh, I'm not familiar with code cave injections but last time I checked you should suspend the main thread then resume it after injecting.

[HeroXx]

private void moveToHarvest(uint obj)
        {
            uint codeCave = wow.AllocateMemory();
            uint VMT45 = wow.ReadUInt(wow.ReadUInt(obj) + (45 * 4));
            wow.Asm.Clear();
            wow.Asm.AddLine("fs mov eax, [0x2C]");
            wow.Asm.AddLine("mov eax, [eax]");
            wow.Asm.AddLine("add eax, 0x10");
            wow.Asm.AddLine("mov dword [eax], {0}", ObjectManager.CurrentManager);
            wow.Asm.AddLine("mov ecx, {0}", obj);
            wow.Asm.AddLine("call {0}", VMT45);
            wow.Asm.AddLine("retn");
            wow.SuspendThread();
            wow.Asm.InjectAndExecute(codeCave);
            wow.FreeMemory(codeCave);
            wow.ResumeThread();
        }

Still no joy.

Edit: And exactly like last time, I take a second to look over the code and see 0x10 For anyone interested in the solution, "add eax, 0x10" should be "add eax, 0x08".

Cheers for the help everyone.

[amadmonk]

BTW, if you have click-to-move enabled, interact should, in many cases, trigger a click-to-move. Meaning that you often don't require a separate move and interact step.

It's still not a bad idea to ensure you're in range before attempting actions, though

[JuJuBoSc]

And call it from another thread will lead you to a crash, go hook something and call it from main thread.

[HeroXx]

And call it from another thread will lead you to a crash, go hook something and call it from main thread.

Beyond my learning at the moment but thanks for the advice

[Evieh]

Beyond my learning at the moment but thanks for the advice

It shouldn't crash if you're suspending the main thread and resuming after it has finished executing the injected code, I also recommend doing everything through the main thread and you might as well go fully injected then (dll injection) it will also save you from having to do crap like this.

[HeroXx]

While I've got a thread open, has anyone got any of the following offsets:

DX_DEVICE
DX_DEVICE_IDX
ENDSCENE_IDX

They don't look like they are very popular.

[Cheatz0]

It shouldn't crash if you're suspending the main thread and resuming after it has finished executing the injected code, I also recommend doing everything through the main thread and you might as well go fully injected then (dll injection) it will also save you from having to do crap like this.

But it will, eventually, crash due to race conditions.

[HeroXx]

So it is crashing as previously stated.

Can this be solved out of process?

[JuJuBoSc]

You're already injecting so you're in process, why just don't detour the EndScene or something else, you're doing some ASM here, so we assume you understand it