Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Outputing packets depending on EntryFilters in txt

Open
#745 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking, tooling

Research direction

The issue mentions EntryFilter and txt output but does not identify files, tests, or an entry point. Locate the text-output path and how EntryFilter values are handled, then determine where unrelated packets should be excluded. Done means txt output contains only packets related to the specified EntryFilter, with coverage for the filtering behavior.

Written by the indexing model from the issue text.

Description

Spoke with ModoX on Discord, would be cool if the parser dropped all packets not relating to the specified EntryFilter in txt output.

Dominant language
C#
Stars
522
Forks
387
Avg merge
3d 6h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TrinityCore/WowPacketParser

All issues in TrinityCore/WowPacketParser

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.