TrinityCore / TrinityCore/WowPacketParser
Outputing packets depending on EntryFilters in txt
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 522
- Forks
- 387
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 4
Description
Spoke with ModoX on Discord, would be cool if the parser dropped all packets not relating to the specified EntryFilter in txt output.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- csharp
- Domain
- networking, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100