[Help] MoveToClick interrupts itself, barely rotates (see video)

[roeliekt]

Hello there!

At the moment I'm working on a simple 'multiwow' bot (goal to 'automate' lvl 60 Onyxia for learning purposes, playing on vanilla 1.12.1). I was testing with 5-man for the time being, but switched to 10-man as all went fine with 5. ClickToMove was working fine with 5 man, but is bugged since I'm using 10 clients. Unfortunately rebooting does not fix the issue. Once CTM is bugged, it's bugged. Even if I close all the wow executable's and start a new client (with no injection/attaching whatsoever), it's not working as it should. I need to delete wow entirely and launch a fresh (newly installed) copy to get CTM working properly again.

When I use CTM, the marker appears in the world and the player starts walking. The problem is that it's walking straight forward, or only taking small turns in the direction of the CTM marker. Next to that the CTM method seems to get interrupted shortly after I try to move somewhere in front of me. It doesn't even finish its movement towards the marker.

For now I tried removing any config related files but unfortunately without any success. In the video below you can see my computer running a single wow client after I tried testing with 10 man before. As you can see in the video I am manually clicking, my program isn't even attached.



Is there anyone who had any experience with this sort of issues? My PC specs are fine I guess, I managed to multibox with 19 wow's before via PwnBoxer without any issues (at the moment I am testing with minimal other processes and software running).

Thanks for your time.

[Saridormi]

Are you calling the CTM function or just writing to the CTM struct directly?

[roeliekt]

In my bot I just write the CTM and flag values to the memory (as the flag i write 4). My addresses for 1.12.1 are:

CtmX = 0x7C6B74,
CtmY = 0xC4D890,
CtmZ = 0xC4D898,
CtmFlag = 0xC4D888,

But in my video I am just clicking in the world. Can the earlier applied memory writing have effect on the same executable launched afterwards? The bug survives through rebooting my PC.

[radegast]

Can the earlier applied memory writing have effect on the same executable launched afterwards?

No. If you did memory writing only, it can't be permanent.
Did you do any experiments with CTM or something else with exe patching?

[roeliekt]

Nope nothing at all, installing a new version of wow as we speak. I'll create another video showing how it happens later tonight when I get home.

[DarkLinux]

I patched the game so it would not do it, but some servers are scanning for it with Warden..

http://www.ownedcore.com/forums/worl...ml#post2963209 ([WoW] 1.12.1.5875 Info Dump Thread)

[Corthezz]

Cap framerate to 60 (aka enable vSync).
In general ctm is crap in vanilla. Go for another movement system.

[Ares14]

I noticed this problem when you try to write the Z axis above the ground / in the air. Then it will bug out and you need to click on the ground to "reset" it.

[roeliekt]

http://www.ownedcore.com/forums/worl...ml#post2963209 ([WoW] 1.12.1.5875 Info Dump Thread)

Cap framerate to 60 (aka enable vSync).

Awesome, combination of these 2 fixed it. Thanks a lot guys! +rep

EDIT: After applying the above methods and rebooting the client, MoveToClick works without doing these steps again (VS needs to be kept on ofc).