World of Warcraft Packet Parser
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-23 09:52:37 +02:00
.github/workflows Update to net 10 2026-04-25 12:21:49 +02:00
scripts Convert WPP to NET Core 3.1 (#530) 2020-03-11 21:25:47 +01:00
SQL Update object_names to 10.1.5 2023-07-13 11:21:43 +02:00
WowPacketParser Add build 12.1.0.69933 2026-09-23 09:52:37 +02:00
WowPacketParser.Proto Update deps 2026-08-12 19:41:54 +02:00
WowPacketParser.Tests Update deps 2026-08-12 19:41:54 +02:00
WowPacketParserModule.BattleNet.V37165 Clean up project references 2026-03-29 00:08:28 +01:00
WowPacketParserModule.Substructures Support 12.1.0 2026-08-26 21:47:12 +02:00
WowPacketParserModule.V1_13_2_31446 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V2_4_3_8606 Add 2.4.3 SMSG_ATTACKER_STATE_UPDATE handler 2026-09-04 20:10:00 +02:00
WowPacketParserModule.V2_5_1_38707 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V3_4_0_45166 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V4_3_4_15595 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V4_4_0_54481 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V5_3_0_16981 Fix copypasta 2026-08-30 01:22:32 +02:00
WowPacketParserModule.V5_4_0_17359 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V5_4_1_17538 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V5_4_2_17658 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V5_4_7_17898 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V5_4_8_18291 Fix naming consistency for monster move waypoints 2026-08-30 01:21:22 +02:00
WowPacketParserModule.V5_5_0_61735 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V6_0_2_19033 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V7_0_3_22248 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V8_0_1_27101 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V9_0_1_36216 Rename ScaleCurve structure to OverrideCurve 2026-08-31 17:02:09 +02:00
WowPacketParserModule.V10_0_0_46181 Fix a bunch of misplaced ResetBitReader calls in updatefield parsers 2026-09-13 20:50:38 +02:00
WowPacketParserModule.V11_0_0_55666 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
WowPacketParserModule.V12_0_0_65390 Fix SQL update output for StaticFlags (#1004) 2026-09-17 21:12:24 +02:00
.gitignore Handle 'V4_4_0_53627' (#835) 2024-03-12 17:09:07 +01:00
appveyor.yml Fix appveyor build 2026-06-20 18:49:14 +02:00
COPYING Move COPYING file to root dir 2016-04-01 02:31:44 +01:00
default.props Update to net 10 2026-04-25 12:21:49 +02:00
docker-entrypoint.sh Add better docker support and documentation (#739) 2022-12-27 01:00:55 +01:00
Dockerfile Clean up remaining net 9 references 2026-04-25 16:42:42 +02:00
README.md Update db2 reader lib version 2026-04-25 16:53:25 +02:00
WowPacketParser.slnx Update to net 10 2026-04-25 12:21:49 +02:00

WowPacketParser (WPP)

GitHub license Build Status AppVeyor

Usage

  • Compile WowPacketParser using Visual Studio 2026 (with .NET 10.0 SDK) or .NET 10.0 SDK. Alternatively you can download compiled binaries from the links below.
  • Edit WowPacketParser.dll.config to fit your needs.
  • Drag one or more files (.pkt or .bin) to WowPacketParser.exe.
  • Command line usage: WowPacketParser.exe [--ConfigFile path --Option1 value1 ...] filetoparse1 ...
Databases

Optionally, WPP can connect to two kinds of MySQL databases: world from TrinityCore and its own database, WPP. This can be enabled by setting <add key="DBEnabled" value="true" /> in the .config file. Remember to set <add key="TargetedDatabase" value="1"/> in accordance with the targeted version of the core.

The world database is used when creating SQL files after parsing to produce the minimum number of changes needed to update the database. For example, if only the faction of a creature that appears in the sniff needs to be updated, the produced SQL files will contain an UPDATE query, instead of a full INSERT to the table creature_template. WPP does not modify this database directly, all the tentative changes will be written to the output SQL files.

The WPP database is used to feed additional data that WPP may use while parsing. For example, in the output text files, the spell name can be displayed next to spell ids:

ServerToClient: SMSG_SPELL_START (0x2BB8) Length: 96 ConnIdx: 0 Time: 01/01/2016 00:22:33.235 Number: 701
(Cast) CasterGUID: Full: 0x03691F00000000000000000000000001 Player/0 R3558/S0 Map: 0 Low: 1
(Cast) SpellID: 2479 (Honorless Target)
(Cast) CastFlags: 15

This is available for a lot of other named entities (achievements, creatures, quests, etc.). The SQL files required for this database is in the SQL directory. create_WPP.sql creates the database and wpp_data_objectnames.sql has some data to fill the database.

Nightly Builds

.NET 10.0 SDK or .NET 10.0 Runtime is needed!

Download .NET 10.0 here!

Windows
Linux (Ubuntu)
macOS (Arm64)

Docker (experimental)

It is possible run WPP on Docker using the trinitycore/wpp image.

To build image:

DOCKER_BUILDKIT=1 docker build . -t trinitycore/wpp

To configure:

Copy WowPacketParser/App.config as template and edit as your needs.

To run:

docker run -it --rm -v /place/where/sniffs/are/kept:/sniffs -v /full/path/App.config:/app/WowPacketParser.dll.config trinitycore/wpp /sniffs/sniffname.pkt

/place/where/sniffs/are/kept should your local directory containing the .pkt file and sniffname.pkt the file to be parsed.

Output (.txt/.sql) of the parser will be added to /place/where/sniffs/are/kept.

WowPacketParser

License: GPLv3

Read file COPYING.

Third Party

The third party libraries have their own way of addressing authorship, and the authorship of commits importing/ updating a third party library reflects who did the importing instead of who wrote the code within the commit.

NuGet libraries:

Copyright information of third party libraries provided through NuGet can be obtained by checking https://www.nuget.org/

Provided third party libraries:

DBFileReaderLib, 2019-2026 wowdev, located at https://github.com/wowdev/DBCD