You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Brazier of Invocation summons Mor Grayhoof who should attack players with several spells.
At the moment there is something the spawns, but nobody can see it. The log tells, something unknown is hitting you with 1-2 damage.
Effect 0: Id 76 (SPELL_EFFECT_SUMMON_OBJECT_WILD)
BasePoints = 1
Targets (22, 32) (TARGET_CASTER_COORDINATES, TARGET_MINION)
EffectMiscValueA = 181051
Radius (Id 15) 3.00
Effect 1: Id 3 (SPELL_EFFECT_DUMMY)
BasePoints = 1
Targets (38, 0) (TARGET_SCRIPT, TARGET_NONE)
Effect 2: NO EFFECT
From my research I can see that the GO doesn't do anything special (probably it's only used for visual) and then there is the Dummy spell that has a script target that should handle the summon.
Note: for the ACID part, I believe the other trigger NPCs for T0.5 quests are already scripted, so we would have to only adapt their script to Mor Grayhoof's NPC trigger.
Well, I remember that we might actually have a problem here.
Some (if not all) of these creatures are spawned in a dungeon, hence we shouldn't be allowed to summon them more than once per session.
We can do this either by SD2, or by despawning the trigger that is the target of the spell.
You have a point here.
We need to check before if players were allowed several tries: do we despawn the trigger at first summon (only one try per session allowed) or once the summoned NPC is defeated (only one kill per session allowed)?
I don't exactly remember what was the right config, but it should be easy to find out on wowwiki or other guides about obtaining T0.5 set. I research it, if you want.
After a bit of research, I found out that the NPCs could be engaged several times in one session:
If you fail to kill Lord Valthalak, he will remain in the middle of the Beast's room until the instance is reset. The Brazier has unlimited charges, so you can of course return another time with a stronger party if you are unsuccessful. (wowwiki)
The summoning items for the other summoned NPCs has a 10 min cooldown, so I assume that only Lord Valthalak remains spawned and that summoned other NPCs like Mor Grayhoof, Isalien and so on, despawn on evade but can be resummoned within the same session. This means that all the triggers NPCs should be despawned on summoned NPCs' death to prevent another summoning (or similar mechanics).
Summarized:
NPC Name
NPCs triggers
Summoned NPCs:
Mor Grayhoof
16044
16080
Isalien
16045
16097
Jarien & Sothos
16046
16101 & 16102
Kormok
16047
16118
Lord Valthalak
16048
16042
I think we could have despawned all triggers by dbscripts_on_creature_death with a specific check in the Jarien & Sothos fight to ensured that the other NPC is already dead.
Thus:
ACID: abilities/summoning
DB: spell targeting, triggers despawn
You could summon more than one boss simultaneously, if you do so. And even if you despawn the trigger right after the spellhit, you can summon the boss twice, because the ACID handling is always a bit delayed.
I would not rely on a trigger_creature, I'd use encounter_states.
Summon the npc by dbscripts_on_spell
Despawn the trigger by dbscripts_on_spell
Set the trigger respawn time as 1 day + set the trigger to bind the party to the instance.
Set the summoned as active object + despawn only on death.
Remove summoning script from ACID. Keep only the boss script.
This should fix everything.
—
Reply to this email directly or view it on GitHub.
Activity
xfurry commentedon Jul 8, 2015
Spell 27203 has the following:
From my research I can see that the GO doesn't do anything special (probably it's only used for visual) and then there is the Dummy spell that has a script target that should handle the summon.
I don't really understand what is the issue.
Is the whole summon event not working, or the summoned npc isn't scripted?
++ @cala and @Tobschinski as they might know more.
Tobschinski commentedon Jul 8, 2015
Just had a look:
The invisible trigger creature will attack you if you use the brazier.
Mor Grayhoof isn't summoned.
Mor Grayhoof isn't scripted.
xfurry commentedon Jul 8, 2015
Ok, then we need to do this:
Tobschinski commentedon Jul 8, 2015
Just for the record, there are more braziers and spells used to summon t0.5 bosses.
Spells: 27184 - 27190 - 27191 - 27201 - 27202 - 27203 - 27517
cala commentedon Jul 9, 2015
I need to have a better look at this, but from what I remember that sounds ok to me.
cala commentedon Jul 9, 2015
Note: for the ACID part, I believe the other trigger NPCs for T0.5 quests are already scripted, so we would have to only adapt their script to Mor Grayhoof's NPC trigger.
xfurry commentedon Jul 9, 2015
Well, I remember that we might actually have a problem here.
Some (if not all) of these creatures are spawned in a dungeon, hence we shouldn't be allowed to summon them more than once per session.
We can do this either by SD2, or by despawning the trigger that is the target of the spell.
cala commentedon Jul 9, 2015
You have a point here.
We need to check before if players were allowed several tries: do we despawn the trigger at first summon (only one try per session allowed) or once the summoned NPC is defeated (only one kill per session allowed)?
I don't exactly remember what was the right config, but it should be easy to find out on wowwiki or other guides about obtaining T0.5 set. I research it, if you want.
xfurry commentedon Jul 9, 2015
This will be great!
cala commentedon Jul 13, 2015
After a bit of research, I found out that the NPCs could be engaged several times in one session:
The summoning items for the other summoned NPCs has a 10 min cooldown, so I assume that only Lord Valthalak remains spawned and that summoned other NPCs like Mor Grayhoof, Isalien and so on, despawn on evade but can be resummoned within the same session. This means that all the triggers NPCs should be despawned on summoned NPCs' death to prevent another summoning (or similar mechanics).
Summarized:
I think we could have despawned all triggers by dbscripts_on_creature_death with a specific check in the Jarien & Sothos fight to ensured that the other NPC is already dead.
Thus:
ACID: abilities/summoning
DB: spell targeting, triggers despawn
Tobschinski commentedon Jul 13, 2015
You could summon more than one boss simultaneously, if you do so. And even if you despawn the trigger right after the spellhit, you can summon the boss twice, because the ACID handling is always a bit delayed.
I would not rely on a trigger_creature, I'd use encounter_states.
xfurry commentedon Jul 17, 2015
I would do the following (for all creatures):
This should fix everything.
cala commentedon Jul 19, 2015
Sounds good to me. Since this is mostly DB stuff, I will do it once I finished reworking BRD.
cala commentedon Jun 23, 2016
Or maybe later, sorry... 😕
Lumber-Jack-2 commentedon Jun 23, 2016
no stress :D