CHEGOK
-
Posts
6 -
Joined
-
Last visited
Never -
Donations
0.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Posts posted by CHEGOK
-
-
As a temporary hack you can disable the check alltogether
More simple hack-way:
@@ -3790,7 +3790,7 @@ SpellCastResult Spell::CheckCast(bool strict) target_friendly = m_caster->IsFriendlyTo(target); } - if(target_friendly) + if(target_friendly && m_spellInfo->Id != 34026) //Kill Command return SPELL_FAILED_BAD_TARGETS; explicit_target_mode = true;
But problem still exist in general.
-
Still actually.
My temp revert commit patch - http://pastebin.com/wsV6JW1P
-
What bug does the patch fix? What features does the patch add?
Fix Deep Wounds typo in comment Implement SPELL_ATTR_EX4_STACK_DOT_MODIFIER support. In 2.4.3 Deep Wounds still cause 20/40/60%
For which repository revision was the patch created?
Fixes in loot roll timer work and related cleanups.
Who has been writing this patch? Please include either forum user names or email addresses.
Me
diff --git a/src/game/Unit.cpp b/src/game/Unit.cpp index 63feb4a..7577f5a 100644 --- a/src/game/Unit.cpp +++ b/src/game/Unit.cpp @@ -6946,9 +6946,9 @@ bool Unit::HandleProcTriggerSpell(Unit *pVictim, uint32 damage, Aura* triggeredB switch (auraSpellInfo->Id) { - case 12834: basepoints0 = int32(weaponDamage * 16 / 100); break; - case 12849: basepoints0 = int32(weaponDamage * 32 / 100); break; - case 12867: basepoints0 = int32(weaponDamage * 48 / 100); break; + case 12834: basepoints0 = int32(weaponDamage * 20 / 100); break; + case 12849: basepoints0 = int32(weaponDamage * 40 / 100); break; + case 12867: basepoints0 = int32(weaponDamage * 60 / 100); break; // Impossible case default: sLog.outError("Unit::HandleProcTriggerSpell: DW unknown spell rank %u",auraSpellInfo->Id);
-
Nice, very nice, but...
Items enchants procs in 19 times more often =)
I think u need to drop this string:
for(int i = EQUIPMENT_SLOT_START; i < EQUIPMENT_SLOT_END; i++)
Variable i do nothing in the loop, but in the end increes proc chance.
-
So, is it a better formula then default mangos?
Developers, comment plz :huh:
[fixed][mangos-0.12][crash]After mover movements backport
in OldBug reports
Posted
Crash apearing after last backports in mangos 0.12 branch.
How to reproduce?
In Russian, maybe that would be more understandable for someone)
Plz fix that so fast as u can. Very important crash bug