I'm actually already writing a tutorial on how to do this. The DLL would then forward these packets to your VB program, write them to a file, or something.
This makes the game call a function inside your DLL instead of the Winsock DLL. It intercepts them by overwriting the program's code at runtime using WriteProcessMemory. If it's using TCP, then you need to intercept the send() and recv() functions. That's if the game is using the UDP protocol, which most do. The DLL needs to intercept calls to the Winsock's sendto() and recvfrom() functions. You need to have a DLL injected inside the game. If somethings wrong w/ my code please dont hesitate to correct it. Should i attach my program to the process 1st?Ĭan someone help me on how to attach my program to that certain process? thanks.Īnyways, if you can tell me something better / better code that would be great. thanks.īy Clicking my command1 my program will send a packet to the game,īut when i send it i get no errors. Now i want to make a program that has a button, when clicked sends packet and opens my storage. i get results and it really opens my storage.
When i use WPE/RPE w/ this packet and send it. Winsock1.GetData temp, vbString, bytesTotalĮnd Sub0A 00 0A 19 5E BF F1 51 18 2E -> the packet that opens storage. Private Sub Winsock1_DataArrival(ByVal bytesTotal As Long) Private Sub Form_Unload(Cancel As Integer)
0 kommentar(er)
