Jump to content

kamillys

Members
  • Posts

    23
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by kamillys

  1. Actually, aura 262 allows to igore some conditions, like combat, stance(warrior's Warbringer&Juggernaut and Sudden Death) or other states. Currently this aura is ignored, but IMO it's bad idea to implement it as "Finger of Frost aura", because it's more universal aura. I thought this aura is only for warrior, but mage's FoF also uses it.

    Client side sees execute as usable, but server doesn't allow to cast it because enemy has more than 20% hp. IMO clients gets info from server in case of charge spell. I don't know what about FoF.

  2. for CoH maybe should be done in different part, but at least Poison Bolt Volley and Curse of the Plaguebringer should be done here, because targets are random.

    Glyph for CoH is also supported, because there is

    Unit::AuraList const& mod = m_caster->GetAurasByType(SPELL_AURA_MOD_MAX_AFFECTED_TARGETS);

    and other part for it.

    ==EDIT==

    Yes, CoH shall be done like Wild Growth, because my patch forces to affect only nearest targets. In case of damaging spells it should be done like my patch. As of http://www.wowhead.com/?npc=15953 says: "Faerlina will launch a Poison Bolt Volley, hitting the 3 closest to her players" and some things cannot be done in SD2. It is possible to manually remove but this makes no sense. Although description of spell 28796 is bad :P

  3. What bug does the patch fix? What features does the patch add?

    Patch fixes number of targets for 4 spells: Curse of the Plaguebringer, Poison Bolt Volley and their heroic versions. It limits to 3 targets(as Wowhead says).

    For which repository revision was the patch created?

    damnit... 8280 as my DB says? Don't Remember

    Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread.

    No/I didn't search.

    Who has been writing this patch? Please include either forum user names or email addresses.

    My idea how to fix and I wrote it.

    diff --git a/src/game/Spell.cpp b/src/game/Spell.cpp
    index 2d894fb..f97a6dd 100644
    --- a/src/game/Spell.cpp
    +++ b/src/game/Spell.cpp
    @@ -1426,6 +1426,16 @@ void Spell::SetTargetMap(uint32 i,uint32 cur,UnitList& TagUnitMap)
            default:
                break;
        }
    +    switch(m_spellInfo->Id)
    +    {
    +        case 29213: // Curse of the Plaguebringer
    +        case 54835: // Curse of the Plaguebringer (H)
    +        case 28796: // Poison Bolt Volley
    +        case 54098: // Poison Bolt Volley (H)
    +                unMaxTargets = 3;
    +        default:
    +            break;
    +    }
    
        Unit::AuraList const& mod = m_caster->GetAurasByType(SPELL_AURA_MOD_MAX_AFFECTED_TARGETS);
        for(Unit::AuraList::const_iterator m = mod.begin(); m != mod.end(); ++m)
    

    It can be done for every "custom" spell, including Circle of Healing etc.... I'm working on CoH, soon will be posted in new thread if not here.

    ==EDIT==

    Addition for CoH(I don't have players for test it, but should work)

            //Circle of Healing + ranks
           case 34861: //1
           case 34863: //2
           case 34864: //3
           case 34865: //4
           case 34866: //5
           case 34868: //6
           case 34869: //7
                   unMaxTargets = 5;
    

  4. There is bug in calculating damage: if some magic damage reductions (like spell 50267) is GREATER than normally damage done by spell, this spell causes a lots of damage. Propably it's declaration problem: if result is smaller than 0 it incerases by 216xxxxxxx(don't remember exacly dmg :P) damage.

    Example: Necrosis causes 100 dmg. Spell 50267 reduces by 146. Result should be 0, but is smaller than 0, but UINT is UNSIGNED! See wikipedia.org.

  5. Some seals have coeffs in C++ code. Keep on mind that.

    Judgements are spells in MaNGOS, at least IMO. Spells have bigger chance to miss.

    "Although a Judgement cannot be dodged, parried, blocked, or "deflected", it has the same chance to miss its target as a melee attack." From wowwiki.com

    SoV/SoC 5-stack effect: Furthermore, in patch 3.2, if the target already has a 5-stack of Seal of Vengeance debuffs, each subsequent melee swing made while this seal is in effect will inflict 33% of the attacker's Weapon Damage as Holy damage to the target (twice this amount if the melee swing crits). This extra holy damage cannot miss, be dodged, or be parried.

    So it's added in 3.2. In 3.1.3 there is no that effect.

  6. it's bug and very simple to fix, only to correct 0.15 to 0.25. In next revs it should be fixed. If somebody really needs a patch, because he/she can't find in Unit.cpp //Judgements of the wise and correct, I'll make it tommorow. It's 1 am in Poland and my brain is disabled :)

  7. Check CD in DB, probably there are some mistakes(5 min instead of 3?). My server is currently compiling(what-a-nice Gentoo :P), it will take too long if I would check it.

    Ghoul's stamina is scaling with owner's stamina, but i'm not sure is it correct because ghoul w/o Master of Ghouls has more hp than ghoul with talent. Please also check int and spirit. Armor is scaling as I remember.

  8. There are patches for Raise Dead, but cooldown is not working. Loading screen resets cooldown (on clear fresh-builded MaNGOS+UDB with no custom patches). Earlier(on 3.0.9) cooldown was OK. Any ideas how to fix CD on Raise Dead? It's only thing missing, except that DK's strength and agility(stamina is working, but needs to be checked) doesn't aeffect Ghoul, propably should be fixed in DB.

    You can use scripts from this thread with little changes, they are working. Ghoul with Master of Ghouls is summoning by typing .cast 52150 in game, for 2min Ghoul there is simple fix in this thread.

    Sorry if my English was bad :P

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use