what wrong with my ClickToMove code?

[sandra11]

my bot works very well before patch 6.2.0 20253,but now this line doesn't work at all

                if (Memory.Read<uint>(Memory.BaseAddress + CTM_Base + CTM_Push) == 0x0000000D)

i get wrong offsit?but they are the same as the Info Dump Thread.
i would appreciate if anyone can help me


it's some of the code below,ClickToMove function don't have any problem

        private static uint CGUnit_C__InitializeTrackingState = 0x41fb57;
        private static uint CTM_Base = 0xE3AE28;
        private static uint CTM_Push = 0x1C;

        private void RunPoints(string str)
        {
            string[] wayPoints = str.Split('\n');
            string[] points;

            for (int i=0;i<wayPoints.Length;i++)            
            {
                if (Memory.Read<uint>(Memory.BaseAddress + CTM_Base + CTM_Push) == 0x0000000D)
                {
                    points = wayPoints[i].Split(':');
                    ClickToMove(Convert.ToSingle(points[0]), Convert.ToSingle(points[1]), Convert.ToSingle(points[2]), 0, 0x4, 2.5f);                    
                    System.Threading.Thread.Sleep(30);
                }
            }
        }

        public static void ClickToMove(Single x, Single y, Single z, UInt64 guid, Int32 action, Single precision)
        {
            UInt32 Pos_Codecave = Memory.AllocateMemory(0x4 * 3);
            UInt32 GUID_Codecave = Memory.AllocateMemory(0x8);
            UInt32 Precision_Codecave = Memory.AllocateMemory(0x4);

            Memory.Write<UInt64>(GUID_Codecave, guid);
            Memory.Write<float>(Precision_Codecave, precision);

            Memory.Write<float>(Pos_Codecave, x);
            Memory.Write<float>(Pos_Codecave + 0x4, y);
            Memory.Write<float>(Pos_Codecave + 0x8, z);

            string[] asm = new string[]
            {
                "mov edx, [" + Precision_Codecave + "]",
                "push edx",

                "call " + ((uint)Memory.BaseAddress + (uint)ClntObjMgrGetActivePlayerObj),
                "mov ecx, eax",
                
                "push " + Pos_Codecave,
                "push " + GUID_Codecave,
                "push " + action,

                "call " + ((uint)Memory.BaseAddress + (uint)CGUnit_C__InitializeTrackingState),
                "retn",
            };

            InjectAndExecute(asm);

            Memory.FreeMemory(Pos_Codecave);
            Memory.FreeMemory(GUID_Codecave);
            Memory.FreeMemory(Precision_Codecave);
        }

[Renyei]

32-bit? The CTM base I'm using is 0x00E3AE20.

[sandra11]

perfectly!

32-bit? The CTM base I'm using is 0x00E3AE20.

[reliasn]

The ClickToMove base may be different for some people so I apologize for not posting how I handle it. Anyways, it's like this:

CTM_Base = 0xE3AE28,
CTM_Type = CTM_Base + 0x14,
CTM_GUID = CTM_Type + 0x4,
CTM_X = CTM_Base + 0x80,
CTM_Y = CTM_X + 0x4,
CTM_Z = CTM_Y + 0x4,

Honestly, I have no idea where exactly the CTM struct starts nor what should be really considered as its "base". I will take a look at the leaked Mac build to see if I can find anything useful.

[Renyei]

The ClickToMove base may be different for some people

Uhhhhhm, no?

[Jadd]

Uhhhhhm, no?

Uhhhhhm, why? If it were me, I wouldn't use a base at all. Click-to-move info is not stored as a struct. "CTM_Base" is just a made up name. So yes, "CTM_Base" may be different depending on the person. For instance:

CTM_Base = 0xE3AE28,
CTM_Type = CTM_Base + 0x14,
CTM_X = CTM_Base + 0x80,

Is the same as:

CTM_Base = 0xE3AE20,
CTM_Type = CTM_Base + 0x1C,
CTM_X = CTM_Base + 0x88,

If you're stupid enough to argue over what some made up name refers to, I would argue that you should call the variables by their actual names:

s_trackingTurn                 = 0x00E3AE20 -- (Renyei's "CTM_Base")
s_trackingDistThresholdSquared = 0x00E3AE28 -- (reliasn's "CTM_Base")
s_trackingType                 = 0x00E3AE3C -- ("CTM_Type")
s_trackingTarget               = 0x00E3AE40 -- ("CTM_GUID")
s_trackingPos                  = 0x00E3AEA8 -- (C3Vector starting at "CTM_X")

CTM_Base? Who's stupid idea was that? /thread

[reliasn]

CTM_Base? Who's stupid idea was that? /thread

In my case, I blame whoever named some function in my IDB to "GetClickToMoveStruct" (0x31461F for 32-bit 20253) which returns dword_E3AE20 (s_trackingTurn). That's where I got the "struct" idea from before really looking at the leaked Mac build. This function is actually CGUnit_C::GetTrackingTurn(), but someone else came up with this nice "Struct" name

Anyways, I will stop using this "CTM_Base" as it doesn't make any sense lol... Thanks once again for the clarifying this, Jadd.

[Torpedoes]

I hope you guys arn't just writing code to test your offsets. You should be starting with Cheat Engine and actually getting CTM working there. Once you figured out the data structures you can convert that to code very easily. Also, I also have no idea why you're injecting assembly there, last time I experimented with CTM all I had to do was write a couple values in the CTM structure, you're opening yourself up to a nice ban if you start changing / injecting actual code. Though in reality Blizzard can also change the CTM activation value, I think it was 14 when I tested it, they can change that to 15 and ban the people writing 14.