From 755a83f634c7c87cc07f743e94d77c8c12356c32 Mon Sep 17 00:00:00 2001 From: Wyrserth Date: Tue, 9 Jul 2019 22:47:11 +0200 Subject: Core/Quest: remove arbitrary error logs related to breadcrumb quest chaining. There are complex cases where breadcrumb quests are mutually exclusive with other breadcrumbs leading to other quests, chaining them shouldn't generate log errors. (cherry picked from commit e6080116f9acb41b1c3d26468a679ff7e4b7c106) --- src/server/game/Globals/ObjectMgr.cpp | 2 -- 1 file changed, 2 deletions(-) (limited to 'src') diff --git a/src/server/game/Globals/ObjectMgr.cpp b/src/server/game/Globals/ObjectMgr.cpp index 1cb5d55af8f..4a81a16a9f6 100644 --- a/src/server/game/Globals/ObjectMgr.cpp +++ b/src/server/game/Globals/ObjectMgr.cpp @@ -5109,8 +5109,6 @@ void ObjectMgr::LoadQuests() } if (qinfo->_nextQuestID) TC_LOG_ERROR("sql.sql", "Quest %u is a breadcrumb, should not unlock quest %u", qinfo->_id, qinfo->_nextQuestID); - if (qinfo->_exclusiveGroup) - TC_LOG_ERROR("sql.sql", "Quest %u is a breadcrumb in exclusive group %i", qinfo->_id, qinfo->_exclusiveGroup); } if (qinfo->_exclusiveGroup) -- cgit v1.2.3