TrinityCore / TrinityCore/TrinityCore
Some bug extrator
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.8k
- Forks
- 6.4k
- Avg merge
- 3d 16m
- Merged PRs (30d)
- 6
Description
Description:
maybe this bug is mine only. I have a last client wow 820 and the classic wow installed in it, in this case I can not extract maps and db.2
Checked on a clean client wow 820 without the classic wow this error is not observed
CHANGEME Description of the problem or issue here.
Current behaviour:
CHANGEME Tell us what happens.
If this is a crash, post the crashlog (upload to https://gist.github.com/).
Expected behaviour:
CHANGEME Tell us what should happen instead.
Steps to reproduce the problem:
- CHANGEME Step 1 include entries of affected creatures / items / quests with a link to the relevant wowhead page.
- Step 2
- Step 3
**Branch(es):master
**TC rev. hash/commit:https://github.com/TrinityCore/TrinityCore/commit/3df2e379eff98eba2c86bc6823cde1def6213afa
CHANGEME Copy the result of server debug command (if you need to run it from client get prat addon)
Operating system: CHANGEME OS
Contributor guide
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
No source file, test, or extractor entry point is named. First reproduce the failure with WoW 8.2.0 installed alongside Classic WoW, compare it with a clean client, and identify the relevant extraction output; done means maps and db.2 extract successfully in the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 12/100