[mac][3.1.3] Moving via memory writes still possible?

[Tanaris4]

I've found this thread on changing movementFlags, but this just makes my character look like it's moving then disconnect:
http://www.mmowned.com/forums/wow-me...minimized.html

Thoughts on why, is it still possible to change these and have your character move? I don't see the movementForce offset existing anymore.

I've also seen the click to move, which I'm researching how to find on a mac now, but I like the movementFlags best thus far.

Thanks!

[Zeroi9]

Interesting, I dont know, but I want to find out more.

[Apoc]

BOOL __thiscall CGPlayer_C__ClickToMove(WoWObject *this, int clickType, WGUID *guid, WOWPOS *clickPos, float precision)

IMO

[ramey]

BOOL __thiscall CGPlayer_C__ClickToMove(WoWObject *this, int clickType, WGUID *guid, WOWPOS *clickPos, float precision)

IMO

typedef void (__cdecl * tClickToMove)( ClickPOS * pPos ); <struct> 
tClickToMove pClickToMove = 0xDEADBEEF;

pClickToMove( &pPos );

IMO

[Tanaris4]

typedef void (__cdecl * tClickToMove)( ClickPOS * pPos ); <struct> 
tClickToMove pClickToMove = 0xDEADBEEF;

pClickToMove( &pPos );

IMO

Yea I have this working on mac. But I'd like to use the other if possible (moreso was curious + wanted to know another method).

Offsets for mac:

// 3.1.3 valid
#define CLICK_TO_MOVE			((IS_X86) ? 0x0118691C : 0x0 )
#define CLICK_TO_MOVE_ACTION	((IS_X86) ? 0x11869F0 : 0x0 )

[Apoc]

typedef void (__cdecl * tClickToMove)( ClickPOS * pPos ); <struct> 
tClickToMove pClickToMove = 0xDEADBEEF;

pClickToMove( &pPos );

IMO

My version is bettar! It actually handles clicking on NPC/Objects. It lets WoW do all the 'thinking' behind the actual actions. As well as the sanity checks, and memory read/writes.

[Tanaris4]

My version is bettar! It actually handles clicking on NPC/Objects. It lets WoW do all the 'thinking' behind the actual actions. As well as the sanity checks, and memory read/writes.

Have you noticed that sometimes it doesn't actually move correctly? It will show the circle on your screen, but you just move forward + not to the location. Once I manually click on the screen, then it suddenly starts to work fine. NO clue why and I can't find a different offset that is set. Here is all I'm setting: (I saw another thread about having to set like 0.25, 0.5 and 14.0f in locations, which I've found, but are already set so re-writing it won't help)

- (void)setClickToMove:(Position*)position{
	float pos[3] = {0.0f, 0.0f, 0.0f};
	UInt32 move = 4;
	pos[0] = [position xPosition];
	pos[1] = [position yPosition];
	pos[2] = [position zPosition];
	
    [[controller wowMemoryAccess] saveDataForAddress: CLICK_TO_MOVE Buffer: (Byte *)&pos BufLength: sizeof(float)*3];
	[[controller wowMemoryAccess] saveDataForAddress: CLICK_TO_MOVE_ACTION Buffer: (Byte *)&move BufLength: sizeof(move)];
}

[Tanaris4]

Anyone noticed a LUA error being thrown when you use CTM memory writes to move?

It's a default Blizz "addon" that is doing it. It's around the "you have stopped following %s" part, probably since there is no player you were following.

[ramey]

Have you noticed that sometimes it doesn't actually move correctly? It will show the circle on your screen, but you just move forward + not to the location. Once I manually click on the screen, then it suddenly starts to work fine. NO clue why and I can't find a different offset that is set. Here is all I'm setting: (I saw another thread about having to set like 0.25, 0.5 and 14.0f in locations, which I've found, but are already set so re-writing it won't help)

- (void)setClickToMove:(Position*)position{
	float pos[3] = {0.0f, 0.0f, 0.0f};
	UInt32 move = 4;
	pos[0] = [position xPosition];
	pos[1] = [position yPosition];
	pos[2] = [position zPosition];
	
    [[controller wowMemoryAccess] saveDataForAddress: CLICK_TO_MOVE Buffer: (Byte *)&pos BufLength: sizeof(float)*3];
	[[controller wowMemoryAccess] saveDataForAddress: CLICK_TO_MOVE_ACTION Buffer: (Byte *)&move BufLength: sizeof(move)];
}

It's because you're writing to memory instead of calling a function which probably initializes some values for the first time before actually doing CTM.

I know for a fact it was discussed elsewhere and apparently fixed by doing memory writes..

Apoc, I don't mind much. I just use it for moving

[Tanaris4]

Yea I saw on another thread that you write 14.0f, 0.25f and 0.5f in 3 places, and I found these + write them, but still no success /cry

Not a big deal to right click before starting, I just worry about the n00bs using PG bitching about it.