`spell_Area` Table

TrinityCore Development TrinityCore Code Discussion
1

Hi, I was following these topic http://www.trinityco…the-queldelarh/, and I figured out that you can’t properly solve the phassing issue related to these quest.

The problem is, that you start the phassing with two different quests, deppending if you are an Alliance or an Horde character (“Journey to the Sunwell”), but you end it with… 6 different quests!, deppending if you are Alliance, Horde-non Blood elf, Blood elf, and if your class is capable of wielding swords or not.

Starting phasing quests

24522 - Alliance players

24562 - Horde players

Ending phasing quests

24553 - Alliance, sword classes

24595 - Alliance, non-sword classes

24564 - Horde, sword classes (except blood-elves)

24598 - Horde, non-sword classes (except blood-elves)

24594 - Blood elf, sword classes

24596 - Blood elf, non-sword classes

Maybe there are other quest examples that have the same issue, I only know these case. My suggestion is to add another column to the spell_area table, called classmask or something like that, in order to fix these phasing properly (and as I said, other cases maybe)

Hope it can help and, and also hope I have posted on the correct section /emoticons/default_tongue.png

2

Wut? When you complete the quest for you class / race, it should set the proper phase.If the quests. If the quests are not grouped / linked / restricted to class / race properly, that is a different issue.

So – are you saying when you complete the quest, ANY of the quests, you aren’t in the proper phase?

– Brian

3

I think that I didn’t explain myself very well. The phassing starts with 2 quest that deppend on character’s race (horde or alliance)

But the phassing ends with 6 different quests, deppending on character’s race but also its class.

For example, alliance players start the phasing with quest 24522 (Journey to the Sunwell) and end the phassing with quest 24553 and 24595. So I can’t do this fix for that, and it isn’t a quest restriction issue.

[CODE]SET @PHASE := 70193;

DELETE FROM spell_area WHERE spell=@PHASE;
INSERT INTO spell_area (spell,area,quest_start,quest_start_active,quest_end,aura_spell,racemask,gender,autocast) VALUES
(@PHASE,4075,24522,1,24553,0,1101,2,1),
(@PHASE,4075,24522,1,24595,0,1101,2,1);[/SQL][/CODE]

As you can see I can add restrictions to races with the phassing with the racemask column, but it’s also needed a classmask field or something like that in order to make something like this

[SQL]SET @PHASE := 70193;

DELETE FROM spell_area WHERE spell=@PHASE;
INSERT INTO spell_area (spell,area,quest_start,quest_start_active,quest_end,aura_spell,racemask,classmask,gender,autocast) VALUES
(@PHASE,4075,24522,1,24553,0,1101,431,2,1),
(@PHASE,4075,24522,1,24595,0,1101,1104,2,1);[/SQL]

4

Wait, wait, you can set the class from quest template, that way it will display only the proper quest or none if the condition is false.

RequiredClasses

Classes required to get the quest. 0 means the quest is available for all classes. This field is a bitmask, you can combine class values. See ChrClasses.dbc

You practicly don’t need to limit the area, but the quest itself, if it is an ending. For example you are saying that there are 2 phase required for both factions and you can do that with spell_area, the quest itself variete in the specific phase mask endings. So why wouldn’t it be a quest issue? Maybe, I’m getting what you say wrong.