azerothcore / azerothcore-wotlk

Complete Open Source and Modular solution for MMO
http://www.azerothcore.org
GNU Affero General Public License v3.0
6.43k stars 2.58k forks source link

Quest: The Perenolde Tiara - Incorrect objective tracker statement. #6636

Closed Efymer closed 3 years ago

Efymer commented 3 years ago

Originally reported: https://github.com/chromiecraft/chromiecraft/issues/1031

WHAT CLIENT DO YOU PLAY ON?

FACTION
CONTENT PHASE:
CURRENT BEHAVIOUR:

After I obtain Perenolde Tiara quest item at the Alterac Mountains, the objective tracker states "Return to Count Remington Ridgewell at Northshire Valley in Elwynn Forest." I'm talking about my quest objective tracker, not my quest log, The quest log already has it correct.

EXPECTED BLIZZLIKE BEHAVIOUR:

Count Remington Ridgewell is at Stormwind Keep. The objective tracker text should say "Return to Count Remington Ridgewell in Stormwind." just as it does in the quest log.

SOURCE:

Sorry, I don't know if there exists a source for objective tracker text.

STEPS TO REPRODUCE THE PROBLEM:
  1. On an Alliance toon, get the quest from Count Remington Ridgewell in Stormwind Keep.
  2. Defeat the ogre for the Tiara.
  3. Have your quest in the objective tracker.
  4. Read it, it's different from what is written in the quest log.
EXTRA NOTES:

The quest item you need is https://wowgaming.altervista.org/aowow/?item=3684

AC HASH/COMMIT:

https://github.com/chromiecraft/azerothcore-wotlk/commit/cecbd604d3f57312165cc53f8ed40feae51ee45f

OPERATING SYSTEM:

Ubuntu 20.04

MODULES:
OTHER CUSTOMIZATIONS:

None.

SERVER:

ChromieCraft

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/99537407-quest-the-perenolde-tiara-incorrect-objective-tracker-statement?utm_campaign=plugin&utm_content=tracker%2F40032087&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F40032087&utm_medium=issues&utm_source=github).
Efymer commented 3 years ago

Adding to the issue: