[Fix] Prince Malchezaar timer #5700

Closed
oMadMano opened this Issue Mar 13, 2012 · 5 comments

Comments

Projects
None yet
6 participants
@oMadMano

Prince Malchezaar the last encounter in Karazhan instance has a bug in phase 3 when he tries to summon the infernals

Here`s a solution for that and also a fix for the first infernal timing spawn

diff --git a/src/server/scripts/EasternKingdoms/Karazhan/boss_prince_malchezaar.cpp b/src/server/scripts/EasternKingdoms/Karazhan/boss_prince_malchezaar.cpp
index 35a9f85..8cf33f5 100644
--- a/src/server/scripts/EasternKingdoms/Karazhan/boss_prince_malchezaar.cpp
+++ b/src/server/scripts/EasternKingdoms/Karazhan/boss_prince_malchezaar.cpp
@@ -228,7 +228,7 @@ public:
             SWPainTimer = 20000;
             AmplifyDamageTimer = 5000;
             Cleave_Timer = 8000;
-            InfernalTimer = 45000;
+            InfernalTimer = 40000;
             InfernalCleanupTimer = 47000;
             AxesTargetSwitchTimer = urand(7500, 20000);
             SunderArmorTimer = urand(5000, 10000);

Good luck and have fun with it :)

@mweinelt

This comment has been minimized.

Show comment Hide comment
@mweinelt

mweinelt Mar 15, 2012

Contributor

How does codestyle fix a low fps issue? As far as I know conditional assignments are a standard in tc code.

Contributor

mweinelt commented Mar 15, 2012

How does codestyle fix a low fps issue? As far as I know conditional assignments are a standard in tc code.

@oMadMano

This comment has been minimized.

Show comment Hide comment
@oMadMano

oMadMano Mar 15, 2012

just try it and you will see we talk here about phase 3 infernal summon not phase 1 or 2 for some unkown reason in phase 3 fps goes down to 1-5 or so

just try it and you will see we talk here about phase 3 infernal summon not phase 1 or 2 for some unkown reason in phase 3 fps goes down to 1-5 or so

@misterwook

This comment has been minimized.

Show comment Hide comment
@misterwook

misterwook Mar 16, 2012

sounds more like a problem at your pc than this codestylefix

sounds more like a problem at your pc than this codestylefix

@jasperrietrae

This comment has been minimized.

Show comment Hide comment
@jasperrietrae

jasperrietrae Mar 17, 2012

Contributor

This is nothing but a codestyle change indeed. Does exactly the same as before..

Contributor

jasperrietrae commented Mar 17, 2012

This is nothing but a codestyle change indeed. Does exactly the same as before..

@FilipLukac

This comment has been minimized.

Show comment Hide comment
@FilipLukac

FilipLukac Mar 26, 2012

Lol

Lol

raczman pushed a commit to raczman/TrinityCore that referenced this issue Apr 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment