Fake hardware input?

[Reconsider]

Hello!

I have just now got my bot up and running, external using ctm to move, loot, skin, mine, etc.
I send input for casting skills using PostMessage.

First of all, BIG thanks to everyone contributing on this forum for all the wonderful information

This works fine BUT.

After maybe 10 minutes or so I get DC. I have read around some on forum and figured that this is probably due to input-check via Warden(?) because no real input is made only CTM and PostMessage. Unfortunently I was unable to find any information as to how to fake this input..

My question is now how do I do to make faked hardware input so that the game won't disconnect me?


Best regards,

[amadmonk]

Write a driver?

Use SendInput instead of PostMessage (course, this disables background botting)?

[Reconsider]

Write a driver?

Use SendInput instead of PostMessage (course, this disables background botting)?

Yes, and I like my background botting

Writing a driver wouldn't help for background botting either, right?

[amadmonk]

No, if you had a driver you could bypass the normal focus queues and send "real" input to arbitrary message queues (read: arbitrary windows, regardless of focus).

However, this is not a task for the faint of heart...

[Reconsider]

No, if you had a driver you could bypass the normal focus queues and send "real" input to arbitrary message queues (read: arbitrary windows, regardless of focus).

However, this is not a task for the faint of heart...

Unfortunently I don't think I have enough experience with driver-development (only made one for interrupt hooking) so this might not be good alternative

Would hooking DirectInput (GetDeviceData) work you think? Because that would probably be how WoW gets input from hardware (considering I see it imports DInput8.dll)


Edit; Got some old code for DInput hook from some other MMORPG's, gonna put it together to do random mouse-movement every few minutes or so (random interval ofc.) and see if this helps from disconnecting. Would a hook via vTable safe? Else I'll put hardware breakpoint I guess

[L33ch]

o.O

Intresting...
Would... a mouse driver be able to send "real" messages to a window too ?

Sidenote: Haven't had any dc's at all with postmessage so far btw... :S


Gonna check what it takes to write a driver...

[Reconsider]

Sidenote: Haven't had any dc's at all with postmessage so far btw... :S

Depends on how you give mouse-input I think..
Do you use CTM or what mouse input you give?

[L33ch]

ohw, ah, Running my WoW + bot in VMware atm....
the window has full focus all of the time, mouse movement is done in my program, clicks are done with mous_event:


[DllImport("user32.dll",CharSet=CharSet.Auto, CallingConvention=CallingConvention.StdCall)]
public static extern void mouse_event(long dwFlags, long dx, long dy, long cButtons, long dwExtraInfo);


buuuuttt... if i could create a driver that made another mousepointer that could be sent to a minimized wow window with messages that would be better, cos i noticed vm's are kinda taking a lot of performance.


Could start doing it like gamelash though...:
http://my.mmoabc.com/article/vietdie....html?login=no

I only have 5 accounts though, sooo.... yeah

TLDR:

"If you count the number of PCs, you'll get 47. My girlfriend controls 23 and I control 23. The other one is a server. All but 2 of those pcs are diskless. It got to the point that updating 46 pcs just took too long, the hard drives added to the electric bill and generated heat, so I found a good PXE solution that works great."

[leather]

write into the address 0x00AE2B7C with 'current time' 0x00843FD0

[lanman92]

I'm actually working on making a 'simple' driver to change your cursor location in WoW. I'll probably end up posting it when it's finished.

[Reconsider]

write into the address 0x00AE2B7C with 'current time' 0x00843FD0

Hm..
0x00AE2B7C seems to hold a value that changes whenever I give the game input, yes.

But 0x00843FD0 seems to be stuck, right now at 440143243 which is about twice the value at 0x00AE2B7C (26994845)..

Are you sure about this?


Edit; 0x00AE2B7C is current tick count + about 500 it seems, so copying GetTickCount to there every once in a while might work

[MaiN]

0x843FD0 is a function.

[Reconsider]

Ah, I didn't even look at the memory page ;P

Anyway, this actually seems to work.. either that or there was something bad in my code before..

uint realInputTime = Memory.ReadUInt(0x00AE2B7C);
if (GetTickCount() >= fakeInputTime)
{
	if(fakeInputTime != 0)
		Memory.Write(0x00AE2B7C, fakeInputTime);
	fakeInputTime = GetTickCount() + (uint)random.Next(1000, 2000);
}

Have to use GetTickCount() + atleast 500, else it seems to crash.. feels safest to me to use 1000
Thanks alot to leather ofcourse!

[Cypher]

Ah, I didn't even look at the memory page ;P

Anyway, this actually seems to work.. either that or there was something bad in my code before..

uint realInputTime = Memory.ReadUInt(0x00AE2B7C);
if (GetTickCount() >= fakeInputTime)
{
	if(fakeInputTime != 0)
		Memory.Write(0x00AE2B7C, fakeInputTime);
	fakeInputTime = GetTickCount() + (uint)random.Next(1000, 2000);
}

Have to use GetTickCount() + atleast 500, else it seems to crash.. feels safest to me to use 1000
Thanks alot to leather ofcourse!

You can't use GetTickCount if you want your input times to be reliable. When WoW starts up it chooses what timing method to use, and it's not guaranteed to be GetTickCount unless you use a CVar forcer.

Use OsGetAsyncTimeMs instead, it's a WoW engine function, and it should be posted somewhere in the address dumps.

[Apoc]

You can't use GetTickCount if you want your input times to be reliable. When WoW starts up it chooses what timing method to use, and it's not guaranteed to be GetTickCount unless you use a CVar forcer.

Use OsGetAsyncTimeMs instead, it's a WoW engine function, and it should be posted somewhere in the address dumps.

It's usually labeled as PerformanceCounter or PerformanceCount. One of the two.