TrinityCore / TrinityCore/WowPacketParser
Moving from a text-based to an XML-based output representation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 522
- Forks
- 387
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 4
Description
Hi all,
since I wanted to work on the topic discussed on Trinitycore - Tool for Scripters/DB devs , I think that a first preparation step needed is to format the output in a more efficient and machine-readable way.
XML seems to be a good candidate since it is tree based (and therefore efficiently explorable) and can be compressed really well (ever heard about EXI)?
I'm doing some experiments on my fork, any ideas about this?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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
Start by reviewing the linked TrinityCore discussion and the XML experiments mentioned in the author's fork. The issue names no file, entry point, test, or acceptance criteria; completion would require an agreed machine-readable XML output design and corresponding implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100