Olion

https://github.com/mangoszero/server/pull/51

I apologize for the bug I've introduced here about 2 months ago. The slot ID issue is gone with this revert, but quest loot from the original report is to be tested still.

It should not be relevant for other cores.

I'm aware of that. You could try to remove the two spell assotiations reported here, from the table, and check all the 3 ranks.

Otherwise, you can ignore it safely.

Have you tested it on the latest core?

This disables the HP regeneration to the boss. The 40% of the full health is set by the SD3 script "boss_murmur" at reset, i.e. at spawn and evade.

On the staging battle. Many SD3 scripts are extremely primitive (Murmur is unlucky too), just like the simplest combat EventAI. It looks like the battle must be there, and it would be nice to have it. However, a full instance recovery requires a laborious work of the both sides, testers and dev(s), together. The game balance must be restored above all. For example, I wonder why the present Murmur lacks an enrage spell to be casted usually at ~10th (or whatever) minute of the battle.

Briefly, I'm not ready yet to create separate cosmetic patches for instance encounters. I consider it possible only since the substantial part of the encounters will be fixed.

Changed Status to Awaiting Feedback

Changed Implemented Version to 22.1

Changed Milestone to 24

Must be this, though an extensive testing is required. Especially the case of a mob having spells of different schools.

The combat movement system looks unsatisfactory in the whole.

Could you give here few examples of such creatures? To check a possible fix.

https://github.com/mangosone/database/pull/74

The core update "Allow player demorph to DB script. Fire arrival event for the last node of player taxi path on CMSG_MOVE_SPLINE_DONE" is needed also for this to work.

Yes, I have it checked, not good. WIP.

We need:

• an exact description of the Mangos core you're using (which means the core and DB version and, for a repack, the repack origin)
• a stack trace for the crash

Without the info, we just cannot do anything.

5 hours ago, saltyteabag said:

it will probably be a pretty involved fix

Indeed. This is because blizz relied on the gameobject casting in this encounter. The 5 spells involved do not complicate it further, so the simplest fix is evident. Just have to invent the Zeppelin Power Core's (shining blue crystals) behaviour based on the quest text.

Could you provide a video to this quest? It involves also Zeppelin Power Core GO (186396), so the question is how many are there such GOs and what they do (spawn/despawn) besides adding the Energized! aura to the nearby players.

One can barely do anything helpful without the stack trace.

Also, nobody is able to fix a code without reading it. The fragment cited above does not belong to contemporary Mangos (Zero, One, Two), it is rather a part of the TrinityCore.