poedbg: External API for Packet Logging and more, C++, C#, Python

[maper]

Note: This project is no longer maintained. Source code attached.

Ask and ye shall receive, exiles. I have pulled the packet logger into its own standalone module and implemented an external API that you can use to communicate with it. It currently supports C++, C#, and Python, with many other languages possible.

Get Started

GitHub - m4p3r/poedbg: External packet logger and API for Path of Exile.

Source Code

See attachment.

Development

I've included the packet sending and receiving features to start. I will be expanding the capabilities of the API to include other things such as memory manipulation, hooking, and more. If you have suggestions, feel free to leave them in this thread.

[GameHelper]

I want to use that to implement
“Is flask drink request responded from the server or not”
This is greatly improve double drinking issues . Specially for instant flask... for now we manually use delay for those things.

Going to look at the code and work on this tomorrow.

[maper]

I want to use that to implement
“Is flask drink request responded from the server or not”
This is greatly improve double drinking issues . Specially for instant flask... for now we manually use delay for those things.

Going to look at the code and work on this tomorrow.

Packet 0x36 is sent up the the server when you initiate a flask drink, 0xf4 is received on the client when the server confirms that a flask drink has occurred (does not get sent if you're at full health or mana, etc.)

[GameHelper]

Packet 0x36 is sent up the the server when you initiate a flask drink, 0xf4 is received on the client when the server confirms that a flask drink has occurred (does not get sent if you're at full health or mana, etc.)

wow, ur love!

[ugabugaga]

Hi, excellent tool. Can you add some sort of filter or just logfile.

[amarat100]

First problem I encountered is packets which send in groups. For example, I often see 0x0122 packet received, BUT sometime get 0x0122 000a ....
This is two packets. One is 0x0122 and another is chat message. Sometimes I get 0x000a and at the end I see 0x0122.

I guess, it is how their UDP reliability works (just resend if not approved), because they don't use TCP for determenistic lockstep synchronization.
So, we can pretty reliably read "Send" packets, but there is problem in correctly deserialize "Received", because there can be multiple packets serialized one after another.

Also, some of game mechanics is lockstep predicted, so in many cases your game version simulates what is happening on server instead of constatly updating what server send or actualized.

[GameHelper]

when i close the debugger, Poe crash....can we make it such that debugger gets removed safely.

[maper]

when i close the debugger, Poe crash....can we make it such that debugger gets removed safely.

I will add an exposed function to "uninitialize" in the next update!

[maper]

I've updated it with the latest version, which now includes the "PoeDbgDestroy" function. This function will detach the internal debugger, un-set all hook locations, and free the memory and handles that the module was using. You can safely close your applications after calling this function.

[maper]

Updated this again. Added more status codes for better error handling, corrected a thread handle leaking and performance issue, as well as improved the sample C++ code to give an example of packet data printing and packet filtering.

Also included a slightly longer list of packet IDs as I look more at different packets.

// Packet definitions.
#define POE_C2S_HEARTBEAT 0x0d
#define POE_C2S_MOVE_BEGIN 0xd4
#define POE_C2S_MOVE_SUSTAIN 0xd6
#define POE_C2S_MOVE_END 0xd8
#define POE_C2S_FLASK_DRINK 0x36
#define POE_S2C_LOGIN 0x02
#define POE_S2C_CHARACTERS 0x04
#define POE_S2C_TRANSITION 0x05
#define POE_S2C_HEARTBEAT 0x22
#define POE_S2C_CHAT 0x0a
#define POE_S2C_ENTITY_POSITION_UPDATE 0xe5
#define POE_S2C_ENTITY_STATE_UPDATE 0x0e
#define POE_S2C_FLASK_DRINK_EFFECT 0xf4

Let me know if there are other features that would be helpful.

[xcrossover25x]

Are you able to tell if the client sends a packet to the server when you try to right-click off an active headhunter buff?

My problem is that Headhunter - Official Path of Exile Wiki will occasionally grant a buff that teleports you to nearby enemies automatically. This can be dangerous, but it is mostly very annoying. Attempting to right-click off a Headhunter buff does not work. I am just curious whether or not right-clicking the buff will even send a packet to the server, or if the client says "You know you can't right-click this, I'm not even going to send a packet"

And if the latter is true, what would happen if you attempted to send a packet to the server asking for the headhunter buff to be removed?

[amarat100]

Im 90% sure nothing will happen. Except it will be logged on server audit and if you happen to stumble into investigation team - it can be a proof of your malicious behavior. Do not send packets which are not possible in game finite-state-automata. So, you can't change state of the game in a way it will not permit - it will probably won't do a thing, and will be logged. Just like any FSA out there.

On the other hand, if you don't care about your own anticheat durability - you can encounter some very funny bugs and/or exploits. Possibility is low, though. I know it because the first question in poe-developer task for public API is probably "how to protect it from malicious behavior". Its just like vaaling unique/rare - it will probably crap the item, but in some rare cases you can get great benefit (if developer unconsiciously created a bug, but believed that it will never happen because client won't allow it).

Like noclip through walls, or brute-forcing recipes by not existing items in your inventory, or opening chests without need to move to them first, or pickuping items without cooldown. There is a lot of things that can be done, but most of them is probably already protected. Most of them is already protected by Deterministic LockStep algorithm, which basically run headless (without graphics and other unimportant things) copy of your client on server side

[maper]

I've added the source code for the poedbg.dll module as well in the repository.

[Beanjuice]

I'm having an issue where no data is being returned. In both the C# and python sample files, I can capture the in going and outgoing packets and their Id's and lengths come in correctly however when I examine the Data, its always empty (or at least a byte array of length 1 with just a 0 in it).

The C++ sample works fine. In C# the data type of Data is byte[], is it actually a pointer instead?

Any ideas?

Thanks.

[maper]

I'm having an issue where no data is being returned. In both the C# and python sample files, I can capture the in going and outgoing packets and their Id's and lengths come in correctly however when I examine the Data, its always empty (or at least a byte array of length 1 with just a 0 in it).

The C++ sample works fine. In C# the data type of Data is byte[], is it actually a pointer instead?

Any ideas?

Thanks.

You're right, there were problems with both the Python and C# code interpreting the packet data incorrectly.

I have fixed both versions and pushed the fixes to GitHub. Thanks for pointing that out.