[Quest] Going Bearback

First of all, I’m not an expert in working with TrinityCore’s DB, I’ve just begun working and learning about DB developing for this DB, so I might say stupid stuff.

I’m also using the latest update pack as well as core updates. (Unless I messed something when updating)

This quest is bugged, in a way that when a player casts Flaming Arrow, that sets Ablaze aura/debuff, on the following mobs: Nifelem Frost Giant and Frostworg, it doesn’t count for the quest.

I noticed that the DB had wrong npc ids, so I updated them to their correct npc IDs:


UPDATE quest_template SET ReqCreatureOrGOId1='29358' WHERE entry='12851' AND title='Going Bearback';

UPDATE quest_template SET ReqCreatureOrGOId2='29351' WHERE entry='12851' AND title='Going Bearback';

But it still didn’t work.

Then I tried something else, I added Flaming Arrow spell and later on I added the Ablaze debuff to the ‘RequiredSpellCast’ column and it didn’t work too.

As I said, I lack experience in DB developing, so I’m kinda lost in here, do you guys know what the problem might be? Or if this is actually a DB problem and not a spell/core problem? If it is a DB issue, which tables do I need to edit or look at?

Thanks in advance.

changing ReqCreatureOrGOIdX is hack because it’s wdb field.

But I checked both wowhead and in-game creature IDs and they matched, the previous creature IDs weren’t even proper IDs, there were no creatures with such IDs

Just want to clear what I said above.

The creature IDs set on the database before my update weren’t legit IDs, there were no NPCs with those IDs, not even on wowhead nor in-game. I changed the IDs based on in-game IDs (by using the .npc info on the mobs) as well as checking wowhead.

Sorry for the double post, I can’t edit my previous the post for some reason…

From sniff I can tell you that http://old.wowhead.com/npc=29358 casts http://old.wowhead.com/spell=58183 when hit by http://old.wowhead.com/spell=54683.

And http://old.wowhead.com/npc=29351 casts http://old.wowhead.com/spell=58184 when hit by http://old.wowhead.com/spell=54683.

Well, modifying missing data, if you sure is correct is still a fix, just a wasted one. ;} But for example, someone may not want to wait official WDB to get updated and use it. /in case of huge and important update, ofc tc won’t care about this, but still let’s say we have latest WDB parsed, then editing won’t hurt, if the data is correct? Since 12340 is 3.3.5a and this would mean the data comes from something after core latest patch update. For example I will soon post almost full Midsummer Festival with tons of stuff and a lot of official information that is wrong in our WDB, then what, wrong gos types etc, missing datas.

Well, modifying missing data, if you sure is correct is still a fix, just a wasted one. ;} But for example, someone may not want to wait official WDB to get updated and use it. /in case of huge and important update, ofc tc won’t care about this, but still let’s say we have latest WDB parsed, then editing won’t hurt, if the data is correct? Since 12340 is 3.3.5a and this would mean the data comes from something after core latest patch update. For example I will soon post almost full Midsummer Festival with tons of stuff and a lot of official information that is wrong in our WDB, then what, wrong gos types etc, missing datas.

Quest template is 100% wdb blizzlike because i forced wow 3.3.5a on retail to cache every quest and item.

I can prove you that it isn’t for Midsummer Festival. Like my point was there were different periods in 3.3.5a and some things got revamped like this. In 2009 it got completely changed. There is one other thing there is data for something and not for another that must have the same like it. Tbh, I didn’t find any requirements that were wrong, more like descriptions and few disables that shouldn’t be the way they are and few that should be. /method 1/ Otherwise I agree with you.