packets

alpines is correct. i am only sending data(a.k.a. keyboard & mouse events) WHEN there is a press/release.

and i like how you think alpines , about the lag and *kickback switch* but this game doesnt have that. so im good on that part.

also the reason why im doing this instead of memory bot is because anticheat is using heartbeat (XIGNCODE3) so no need to bypass and get detected when you can do stuff like this... :)

and i tested my idea already with 10 minute run. the only problem i had was that the Edit control was a very low limit so i will change the Edit into something else custom perhaps.... but it works 1:1 , because i have my main machine conected to internet via cable, and vmware machines running on the same network so there wont be any problem there...

but if you have any more/other ideas of what problems could be , Please , post them :) im open for all help and ideas

Sounds great, good luck with the development.

yeah hopefully i get around to finishing it this week, because GTA5 is coming 14th so FML from that day...

bad news. autoit isnt capable of multithreading , so making a program to control multiple game clients in different computers wont work... since i cannot get the keys to send over tcp simulteusly...
like send "W" "D" and "LEFTCLICK" together... too much for autoit :D

maybe someone knows similar program that can do this thing?

running same game different accounts one different pc in local network. and control them both with same kebyoard

Sure you can, there is no problem. The problem is in the way you're handling the packets.
Register a function via AdlibRegister which iterates the client array and stores the keys or receives the commands from the clients.

In your main loop you'll process these commands. Ezpz.

Or you could redirect the client to a second instance of your program which will only handle the commands from that client. This would be the most similar thing to multithreading (multiprocessing).

hm maybe you can provide an little example?

Well it's as basic as I said. For the first suggestion simply register a function which gathers all the packages from the clients. (I don't know how you're going to setup server/client so it's just an idea) So you won't miss any packet. In the main program / server loop you could process through these commands.

If you want to handle each connection with a seperate script so you've got multiprocessing then you have to redirect the incoming connection to the 2nd script.
That can be very easily done as accepting the connection. Sending something like "redirect to port 9090" and the server script runs a seperate instance on that port and the client which connected to the main server closes the connection and tries to open to the new one.

These are just basic ideas, I don't know how you want to setup everything so it's better if you think about it.