[Classic] 1.13.2.32089 - WoW Close randomly

[NoxiaZ]

Hi,

Anyone experienced that WoW close randomly when cheat engine is attached or sometimes if its just open, or when the bot is reading memory and clicking on screen? Anyone figured out why this is happening, and what can be done to prevent?
Sometimes it takes hours before it close, sometimes only minutes.

[mazer]

regarding CE, this is the debugger detection:
https://www.ownedcore.com/forums/wor...bugging-2.html (How to Work Around Anti-Debugging)

suggestions are here:
- rename all occurences of "cheat engine" in the binary
- remove icon from CE
- rename folder

there is a lua script for CE here, that will do some renaming for you on startup. (cant find it atm)

for only mem reading and/or clicking etc i did not encounter any problems

[NoxiaZ]

regarding CE, this is the debugger detection:
https://www.ownedcore.com/forums/wor...bugging-2.html (How to Work Around Anti-Debugging)

suggestions are here:
- rename all occurences of "cheat engine" in the binary
- remove icon from CE
- rename folder

there is a lua script for CE here, that will do some renaming for you on startup. (cant find it atm)

for only mem reading and/or clicking etc i did not encounter any problems

I have renamed CE, changed folder etc. - But it still happens, but it takes sometimes hours before closing.

The same goes for when the bot is running (and only bot no CE), and bot only read memory, move mouse, click on screen, and sending key strokes.

[mazer]

what memory library are use using? you may want to check how you access the module.

fe:

OpenProcess(Mode, 1, (uint)this.ProcessToRead.Id);

mode should be 0x10 for "read"

[NoxiaZ]

what memory library are use using? you may want to check how you access the module.

fe:

OpenProcess(Mode, 1, (uint)this.ProcessToRead.Id);

mode should be 0x10 for "read"

I just used the handle i got from GetProcessesByName
Like this:

var handle = Process.GetProcessesByName("WoW")[0].Handle;
ReadProcessMemory(handle, ......);

But i changed the code to use openprcess now, to see if that works, with only access to read ofc.

hopefully it helps - Thank you.

[NoxiaZ]

It seems to have no effect to use openprecess instead.

public const int PROCESS_WM_READ = 0x0010;

MemoryHandle = (IntPtr)ReadMemory.OpenProcess(ReadMemory.PROCESS_WM_READ, false, process.Id);

[ChrisIsMe]

Do you have other things open? Ida also causes wow to crash/close..

I have never had a crash with full access permission in my memory stuff.

[NoxiaZ]

Do you have other things open? Ida also causes wow to crash/close..

I have never had a crash with full access permission in my memory stuff.

I have nothing open, beside Visual Studio and the Bot program. - But seems i fixed the problem, it seems to be the mount of click with the mouse, maybe too many request to the user32 ClientToScreen method that was the reason for the crash/close (There was nothing in event viewer, so i expect it to be a close).
It seems to be running fine now.

[mazer]

I have nothing open, beside Visual Studio and the Bot program. - But seems i fixed the problem, it seems to be the mount of click with the mouse, maybe too many request to the user32 ClientToScreen method that was the reason for the crash/close (There was nothing in event viewer, so i expect it to be a close).
It seems to be running fine now.

how many clicks you do? i just use click for looting / skinning / interacting with objects.
on the other hand i call ClientToScreen very oftern for W2S and the external overlay i use without any problems

[NoxiaZ]

how many clicks you do? i just use click for looting / skinning / interacting with objects.
on the other hand i call ClientToScreen very oftern for W2S and the external overlay i use without any problems

When targeting a mob, it clicked a lot more then actually needed - Fixing the way it click and how long it should wait for the game to respond on the "action" helped.