Dire Maul Fixes

[scotty0100]

Ironbark the Redeemed wasn't spawning after Zanzil's death.

The door after the final boss (Alzzin) wasn't opening after his death.

INSERT INTO dbscripts_on_creature_death (id, delay, command, datalong, datalong2, buddy_entry, search_radius, data_flags, dataint, dataint2, dataint3, dataint4, x, y, z, o, comments) VALUES
(11492, 0, 11, 14813, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 'Open Crumble Wall after Alzzin's Death'),
(11490, 0, 18, 0, 0, 11491, 138118, 1, 0, 0, 0, 0, 0, 0, 0, 0, 'Despawn Old Ironbark after Zanzil's Death'),
(11490, 0, 10, 14241, 0, 0, 0, 0, 0, 0, 0, 0, -72.171898, -283.252014, -57.749699, 4.084070, 'Spawn ironbark the redeemed after Zanzils death');

[Schmoozerd]

no, none of these fixes is proper i think.
See https://github.com/scriptdev2/scriptdev2/blob/master/scripts/kalimdor/dire_maul/instance_dire_maul.cpp

I cannot tell what is going on directly, but the door after alzzin is supported with sd2.

case TYPE_ALZZIN: // This Encounter is expected to be handled within Acid (reason handling at 50% hp)
..
DoUseDoorOrButton(GO_CRUMBLE_WALL);

Maybe there is some mismatch with zanzil and zevrim?

case TYPE_ZEVRIM:
...
pIronbark->UpdateEntry(NPC_IRONBARK_REDEEMED);

[cala]

I was thinking the same. Maybe something in the database is wrong/missing and prevent SD2 from working as intended?
Now that version 1.2.0 is released, I will have a better look on DM and UBRS/LBRS that had many reports lately.

[scotty0100]

Apologies, I should have looked in further into SD2. However, on the topic of dire maul fixes then, I'll add them to here if I see anything that doesn't look right. I'm looking at old dire maul instance run videos and comparing them to cMangos core.

First one I noticed so far is Guard Fengus at the moment stands over the box; however on retail he seems to wonder around the platform and then seems to charge the center if the box gets looted.

Source 1: https://www.youtube.com/watch?feature=player_detailpage&v=KVyqLWOWPZ0#t=356
Source 2: https://www.youtube.com/watch?feature=player_detailpage&v=iSumJg7dm1c#t=140
Source 3: https://www.youtube.com/watch?feature=player_detailpage&v=aOb8qB8G4x4#t=348

On source 2 it looks like he is avoidable also. So maybe can have him charge to the location rather than to the player.

Will continue to add dire maul issues here if that's OK 👍

EDIT: I don't think he charges when the box is looted actually, looking at source 2 again he is just walking slowly, it's just because the video is sped up it looks faster, I think he just paths across there as well.

[scotty0100]

Lethtendris & Pimgib pathing around the campfire. Source: http://www.youtube.com/watch?feature=player_detailpage&v=hdU-IWdLZ54#t=131

Currently they stand still.

[scotty0100]

Fairly big bug in Dire Maul also; after killing King Gordok and speaking to Mizzle the Crafty, you can spawn an unlimited amount of chests by keep going back and talking to him.

Would you rather me separate these bugs in new issues or this OK?

[scotty0100]

Knot Thimblejack's Cache is currently located underneath Immolthar. I believe it should spawn next to Knot after you complete the "Free Knot" quest.

[cala]

Thank you for all these reports. I prefer you open separate issues, it is easier to keep track of it.
There is also a big report already opened about Dire Maul: #77

I tested yesterday the first ones: I confirm Ironbark/Zevrim/Alzzin events work as intented with SD2. The only errors I noticed were Alzzin using only partially its ACID script (to be checked further).

Many creature movements/patrols are missing in DM, flags are not OK or positions wrong. I'm slowly working on everyone of these. Thank you. 👍

[cala]

Lethtendris & Pimgib pathing around the campfire. Currently they stand still.

Is fixed by 3871dac

[cala]

First one I noticed so far is Guard Fengus at the moment stands over the box; however on retail he seems to wonder around the platform and then seems to charge the center if the box gets looted.

Fixed in 9dfad04

[cala]

Mizzle and Gordok's cache are fixed by 94a05ca

[cala]

All sub issues described in this thread are now fixed. Thanks everyone.