Skip to content

Commit 07fcf57

Browse files
authored
Update README.md
1 parent d2c2e48 commit 07fcf57

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# PRO_Packet_Inspector
2-
A simple function hooker which will print out all the on going packets of PRO Client.
2+
A simple function hooker which will print out all the on going packets of PRO Client. And only works with 32 Bit version of PRO.
33

44
# Build
55
Visual Studio 2017 is enough to build this. (Make sure you got all the SDKs)
@@ -13,7 +13,7 @@ You'll need Cheate Engine (this is the easiest tool).
1313
You may see something like this:
1414
[![Example 1](https://i.imgur.com/Vbi4zFS.png)](https://i.imgur.com/Vbi4zFS.png)
1515
Ignore all the `DSSock.ProcessCommands` things and notice `GameAssembly.dll + 1480A3` for this case.
16-
And the offset will be 0x1480A0 for ProcessCommands function. How can you know for your case? It's simple just substract all the bytes which are lebelled with `DSSock.ProcessCommands`, for my case it's 3 bytes:
16+
And the offset is 0x1480A0 for ProcessCommands function in my case. How can you know for your case? It's simple just substract all the bytes which are lebelled with `DSSock.ProcessCommands`, for my case it's 3 bytes:
1717
[![Example 2](https://i.imgur.com/SdAifWw.png)](https://i.imgur.com/SdAifWw.png)
1818
So, 0x1480A3 - 3 = 0x1480A0, and don't forget to substract the bytes from the first encountered `GameAssembly.dll + offset` offset after ignoring all the bytes lebelled with `DSSock.ProcessCommands`.
1919
Follow the same for `SendPacket` function.

0 commit comments

Comments
 (0)