HackPacketCheck.txt

Per-opcode anti-cheat packet rules. For each incoming packet, the server looks up the row keyed by opcode (and optional subcode), validates the encryption flag, then applies a two-threshold rate limiter: log-and-reject at MinCount, disconnect at MaxCount.

File Location#

Data/Hack/HackPacketCheck.txt

Loaded once at GameServer startup. Changes require a restart.

Format#

Plain text, whitespace-delimited, one packet rule per row. Comment lines start with //. File ends with end.

//Index   Value   Encrypt   MaxDelay   MinCount   MaxCount   //Comment
0         *       0         2000       3          5          //Chat message - anti spam
19        *       0         150        25         40         //Skill attack

Columns#

Rate-Limit Math#

For each packet arrival:

1. If the opcode has no row in this file, log an "unknown packet" hack entry and disconnect.
2. If Encrypt is 0 or 1 and the packet's actual encryption does not match, log and disconnect.
3. Serial check (always on, independent of this file): if the packet's serial is invalid, log and disconnect.
4. If the current time is past the window (MaxDelay ms since the first packet of the window), reset the counter and timestamp.
5. Increment the counter. If it now exceeds MinCount, log and reject the packet. If it also exceeds MaxCount, additionally disconnect.
6. Otherwise accept the packet.

Example: Index=0, MaxDelay=2000, MinCount=3, MaxCount=5 accepts the first 3 chat packets per 2-second window, drops the 4th and 5th with a hack log entry, and disconnects on the 6th.

Packet Categories#

The shipped file groups opcodes by function. Categories are cosmetic comments only; the engine treats every row independently.

Examples#

0         *       0         2000       3          5          //Chat message

19        *       0         150        25         40         //Skill attack

3         *       1         0          0          0          //Character create

77        *       0         0          0          0          //Default sub
77        0       1         0          0          0          //Sub 0 requires encryption
77        1       1         0          0          0          //Sub 1 requires encryption

243       *       *         0          0          0          //0xF3 Special handler

Relationship to Common.dat Hack Settings#

Common.dat Hack Settings govern behavioral anti-cheat (attack speed reporting, potion spam tracking, combo timing, serial seeds). This file governs packet-level rate limits and the encryption/plaintext contract.

Movement speed hacking is handled by always-on detectors (not configurable via either file).

Cross-File Dependencies#

Common Issues#

• Legit players randomly disconnected during combat - MaxCount too low on opcode 19 (skill attack) or 20 (normal attack); raise in small increments.
• All packets for an opcode rejected after adding a row - row uses Encrypt=0 while the client sends that opcode encrypted, or vice versa. Set Encrypt=* to disable the check.
• Opcode disconnects immediately with "unknown" in hack log - opcode has no row at all. Every handled opcode must have at least one entry (wildcard row is fine).
• Chat spam not blocked - opcode 0 row has MaxDelay=0 or both count thresholds too high. Combine with Filter.txt for word-level filtering.
• Encrypt=1 packets always rejected - encryption blobs missing or corrupt in Data/Hack/, or the client build does not encrypt this opcode.
• Warnings flood the log with no useful signal - MinCount set too low; raise it to reduce noise while keeping MaxCount at the disconnect threshold.
• File edits ignored - a row has fewer than 6 columns; the parser aborts on the malformed row (error popup at startup). Check the server console for the script error line number.
• Different players hit limits at different times - rate window is per-player, measured from their own most recent window reset. There are no shared/global limits in this file.