TrinityCore / TrinityCore/TrinityCore
[master] Missing World Quests system implementation.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.8k
- Forks
- 6.4k
- Avg merge
- 3d 16m
- Merged PRs (30d)
- 6
Description
Description: Description in title. In pre-7.1 after some Khadgar quest you were getting access to WQs, aura that was given as reward for that quest not even castable/learnable now. So we need:
- Player FLAG/AURA that give access to world quests with level 110 so player could see the boxes and WQs on the map, and client could send update requests.
- Recheck C/SMSG_WORLD_QUEST_UPDATE opcode handling. Seems like SMSG reply sended only once in a 5 minutes on retail.
- WQs server cycle table in DB.
- Hidden questlog for WQs, there could be more than 90+ WQs at the same time, old pre 7.0 invastions scenario steps marked as WQs are in sniffs too (could be daily cooldown for loot).
- Hidden bag for not usable questitems.
Current behaviour: No flags, old spell not working, WQs not appear on level 110 and looks like client is not requesting this data.
Expected behaviour: As soon as you hit level 110 WQs should appear. Their rotation include around 3-8 quests per single legion location and few vanilla locations,
Steps to reproduce the problem:
- Use .levelup to reach 110.
- Nothing happens.
Branch(es):
master
TC rev. hash/commit: 92420ba
TDB version: 703.00
Operating system: Win 10 x64 Pro
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 tracing the C/SMSG_WORLD_QUEST_UPDATE opcode handling and the level-110 access flag or aura described in the issue. The work is complete only when world quests appear after reaching level 110, rotations are represented in the database, and hidden quest-log and bag behavior is implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, databases, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100