From 642ed8a5d27734bee5ccafb3ae3646d2bee74659 Mon Sep 17 00:00:00 2001 From: Naios Date: Sat, 29 Jun 2013 15:44:32 +0200 Subject: Core/PhaseMgr: Fixed an updateleak that occured if the rewarded quest hadn't requirements * Fixed the range for phase ids in the phase_definition table * solves http://www.trinitycore.org/f/topic/8737-condition-quest-rewarded-dosnt-work-instantly/ --- src/server/game/Entities/Player/Player.cpp | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src') diff --git a/src/server/game/Entities/Player/Player.cpp b/src/server/game/Entities/Player/Player.cpp index 153f6c3da89..5f82f07234f 100644 --- a/src/server/game/Entities/Player/Player.cpp +++ b/src/server/game/Entities/Player/Player.cpp @@ -15396,6 +15396,10 @@ void Player::RewardQuest(Quest const* quest, uint32 reward, Object* questGiver, m_RewardedQuests.insert(quest_id); m_RewardedQuestsSave[quest_id] = true; + PhaseUpdateData phaseUdateData; + phaseUdateData.AddQuestUpdate(quest_id); + phaseMgr.NotifyConditionChanged(phaseUdateData); + // StoreNewItem, mail reward, etc. save data directly to the database // to prevent exploitable data desynchronisation we save the quest status to the database too // (to prevent rewarding this quest another time while rewards were already given out) -- cgit v1.2.3