TrinityCore / TrinityCore/TrinityCoreCustomChanges
autoequip good idea for gms testing things
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 83
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
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
Start by reading the linked TrinityCore community proposal and the repository wiki, including the documented custom-patch workflow. Clarify the intended auto-equip behavior for GM testing, identify the relevant game-server entry points, and define an observable test or acceptance condition before estimating implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100