Auto-enable CTM Functionality without user input.

[LegacyAX]

hey all,

Hope this isnt a re-post but I personally havent seen anyone post it...

anyway, what I mean by auto-enable CTM is, if you are/have used CTM then you know that the user needs to first enable CTM in order for the function to work correctly, honestly I think thats pretty annoying, plus add the fact that alot of noobs don't ever READ instructions, so this is what I do so that as soon as my bot starts, it does a simple memory write that enables CTM functionality even if the user doesnt have CTM enabled via interface menu.

ClickMoveStart = 0x0128183C;

Just simply write the value "13.9626340866089"(float) to ClickMoveStart at run time. Easy yet very effective.


But for you paranoid people out there that refuse to use memory editing if you dont already know there IS a way to enable CTM without using memory...

Just have your bot type the following command at run time..

"/console AutoInteract 1"

Hope this helps some people using this functionality. Enjoy.

-L_AX

Note: if this is a re-post you can just delete :/ thx

[Tanaris4]

Just FYI that value you are writing is scale

[Apoc]

[g_pCGinputCntrlActive]+0x4 |= 0x400000 <-- Will do the same thing

g_pCGinputCntrlActive = 0x012054E4

[LegacyAX]

Thanks apoc, for adding anouther method.

[Tanaris4]

[g_pCGinputCntrlActive]+0x4 |= 0x400000 <-- Will do the same thing

g_pCGinputCntrlActive = 0x012054E4

how did you find this?

[furang]

I guess by changing ctm status in settings and catching memwrite

[lanman92]

My guess would be by placing a bp on the start of the ctm functions. Run till return and see where the call came from and where it checks if it should go.

[vulcanaoc]

Wishing this threads existence was justifiable ...in vain

[Apoc]

No, actually, it was just reversing CGInput_C__ToggleControlBit.

g_pCGinputCntrlActive is the CGInput_C class, and +0x4 is the input flags...

[UnknOwned]

ClickMoveStart = 0x0128183C;

Just simply write the value "13.9626340866089"(float) to ClickMoveStart at run time. Easy yet very effective.

I think the original values are going to the extremes.
You can set it to 40 or 10 and you will get some "somewhat" same result, hence the scaling

[g_pCGinputCntrlActive]+0x4 |= 0x400000 <-- Will do the same thing

g_pCGinputCntrlActive = 0x012054E4

But its not needed for it to work.
Btw, in your documentation of the MovementDirections flag, you do not mention 0x10000, you know what that is?

[Apoc]

I think the original values are going to the extremes.
You can set it to 40 or 10 and you will get some "somewhat" same result, hence the scaling




But its not needed for it to work.
Btw, in your documentation of the MovementDirections flag, you do not mention 0x10000, you know what that is?

Not a damned clue. Cba to find out atm either. (IIRC, 0x200000 was the auto-follow flag)