Interact Problems

[luciferc]

When my bot Interacts it checks via Guid and then Interacts with it.

The problem is that wow sometimes crashes with no error what so ever on an interact.

Log #1
NoMorePasting.com
Log #2
NoMorePasting.com


So Basically it will Display when it finds a mine and what BaseAddr it Interacts W/.

Ex:
###### mine is an interact

/// <summary>
        /// Interact with a object
        /// </summary>
        /// <param name="obj">object to interact with</param>
        public void Interact(uint obj)
        {
            Process.EnterDebugMode(); 

            
            //get the adress of the call for vmt 36 (Interact)
            uint VMT36 = wow.ReadUInt((wow.ReadUInt(obj) + (36 * 4)));

            wow.Asm.AddLine("fs mov eax, [0x2C]");
            wow.Asm.AddLine("mov eax, [eax]");
            wow.Asm.AddLine("add eax, 8");
            wow.Asm.AddLine("mov dword [eax], {0}", ObjectManager.s_curMgr);
            wow.Asm.AddLine("mov ecx, {0}", obj);
            wow.Asm.AddLine("call {0}", VMT36); //read pointer to Interact method
            wow.Asm.AddLine("retn");


            wow.Asm.InjectAndExecute(codeCave);

            wow.Asm.Clear();
            //wow.FreeMemory(codeCave);  ''Uses the Same Memory Alloc for all ASM Code''
            Main_Window.logAddLine(obj + " mine");
        }

[Nesox]

That happens to me sometimes too :yuck:
dunno what the problem is tho

[luciferc]

Anyone have any ideas?

[hypnodok]

Probably another threading issue.

[luciferc]

Do you mean i have to many threads not checking what they are doing.

B/c i only have 1 thread doing looting as a whole and any loots must be passed thru its checks and then are looted (and it sleeps whilst it is looting so you can't double loot etc..).

[Shynd]

You have one thread and WoW has one (main) thread and they are both accessing WoW's TLS at the same time...

[lanman92]

I'm not sure bro, but I think you can avoid almost all threading issues by calling from WoW's main thread through detouring EndScene or something. You would have to FindPattern() it and I'm not so sure it would be easy to detour out-of-process. WoW does a lot of random stuff when you don't use it's main thread.

[MartyT]

How did ISXWoW manage it to call stuff?

[lanman92]

I'm pretty sure ISXWow hooks EndScene() and uses IPC or w/e to place their opcodes into the detoured EndScene(). Not sure if they use IPC or just do it straight from their DLL. Never really looked into ISX much.

[Nesox]

I'm pretty sure ISXWow hooks EndScene() and uses IPC or w/e to place their opcodes into the detoured EndScene(). Not sure if they use IPC or just do it straight from their DLL. Never really looked into ISX much.

that would be nice to set up so you can call functions from a injected dll from a c# application by hooking/detouring endscene with the dll, it would solve the problem with asyncwaiting != false when you try to call SetGlueScreen("charcreate") from the CharSelect glue

[luciferc]

So if the problem is with the looting when i interact with the bot if i am correct.

Because it has sleeps way over 3Seconds for a Mine so it never errors on that.

So maybe i will try to not touch it at all and see how long it can go.

[lanman92]

The problem is just with bad timing. The only realistic way to do this out of process is to write a C++ stub and inject it and detour something in the mainthread of WoW. Do your dirty work there. Have it uninject itself when it's done.

[Shynd]

Or, if you wanted, you could, instead of creating a new thread, hijack WoW's main thread using GetThreadContext and SetThreadContext. Look at Magic.SInject in the BlackMagic source; there should be a DLL injection method named something like InjectRedirectThread that outlines how to do such a thing. No idea if that would cause more crashes or less.

[lanman92]

Never thought about that. Similar to the way I inject DLLs. Grab context, change EIP, run my shit, set it back. Good idea. I think I'm gonna go that route...

EDIT: How can you make sure that you are grabbing the main thread? Is there a struct inside each thread that tells if it is the main thread of a process?

[Shynd]

Well, there's a few ways of doing it, actually. Firstly, in .NET, the main thread is almost always index zero in the Process.Threads collection. You could also use CreateToolhelp32Snapshot, if working with unmanaged code. Another way (there is ALWAYS another way) is to read the information from the process' PDB, ala Dll Injection (Appendix B, may not work in managed code, probably will have to inject an ASM stub into the process that takes care of it).