Jump to content

ZPS

Members
  • Posts

    15
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by ZPS

  1. Add one more select flag to SelectAttackingTarget. SELECT_FLAG_NOT_IN_MELEE_RANGE - is used when you want to select ranged targets (which are not in melee range).

    diff --git a/src/game/Creature.cpp b/src/game/Creature.cpp

    index 8929bf8..4c09923 100644

    --- a/src/game/Creature.cpp

    +++ b/src/game/Creature.cpp

    @@ -2078,6 +2078,9 @@ bool Creature::MeetsSelectAttackingRequirement(Unit* pTarget, SpellEntry const*

    if (selectFlags & SELECT_FLAG_IN_MELEE_RANGE && !CanReachWithMeleeAttack(pTarget))

    return false;

    + if (selectFlags & SELECT_FLAG_NOT_IN_MELEE_RANGE && CanReachWithMeleeAttack(pTarget))

    + return false;

    +

    if (selectFlags & SELECT_FLAG_IN_LOS && !IsWithinLOSInMap(pTarget))

    return false;

    diff --git a/src/game/Creature.h b/src/game/Creature.h

    index 96a4a65..38ecf84 100644

    --- a/src/game/Creature.h

    +++ b/src/game/Creature.h

    @@ -316,13 +316,14 @@ enum AttackingTarget

    enum SelectFlags

    {

    - SELECT_FLAG_IN_LOS = 0x001, // Default Selection Requirement for Spell-targets

    - SELECT_FLAG_PLAYER = 0x002,

    - SELECT_FLAG_POWER_MANA = 0x004, // For Energy based spells, like manaburn

    - SELECT_FLAG_POWER_RAGE = 0x008,

    - SELECT_FLAG_POWER_ENERGY = 0x010,

    - SELECT_FLAG_POWER_RUNIC = 0x020,

    - SELECT_FLAG_IN_MELEE_RANGE = 0x040,

    + SELECT_FLAG_IN_LOS = 0x001, // Default Selection Requirement for Spell-targets

    + SELECT_FLAG_PLAYER = 0x002,

    + SELECT_FLAG_POWER_MANA = 0x004, // For Energy based spells, like manaburn

    + SELECT_FLAG_POWER_RAGE = 0x008,

    + SELECT_FLAG_POWER_ENERGY = 0x010,

    + SELECT_FLAG_POWER_RUNIC = 0x020,

    + SELECT_FLAG_IN_MELEE_RANGE = 0x040,

    + SELECT_FLAG_NOT_IN_MELEE_RANGE = 0x080,

    };

    // Vendors

    P.S.: Btw, tag "[ code ]" is awful...

  2. can anyone confirm a few persistent issues with this patch?

    1. grouping with a hunter / warlock / class with summoned 'pet' standing on a different map to the rest of the group causes client critical errors

    2. server crashes - http://paste2.org/p/937668 (this may have been fixed)

    they seem to be the 2 problems that need urgent attention... If someone with the knowledge can step in and show us noobs what to do and organise us towards a goal i may let them have my babies.

    Patch against server crash:

    ----------------------------- src/game/Vehicle.cpp -----------------------------
    index 3fc4aef..6e69ce2 100644
    @@ -637,6 +637,9 @@ void Vehicle::Dismiss()
    
    void Vehicle::RellocatePassengers(Map *map)
    {
    +    if (m_Seats.empty())
    +        return;
    +
        for(SeatMap::iterator itr = m_Seats.begin(); itr != m_Seats.end(); ++itr)
        {
            if(itr->second.flags & SEAT_FULL)
    

  3. How to prohibit one faction rated arenas now (horde vs horde and ally vs ally)? Before [7336] (Implemented new BattleGroundQueue invitation system) I used this patch:

    diff --git a/src/game/BattleGroundMgr.cpp b/src/game/BattleGroundMgr.cpp
    index a582f38..bfd0ae6 100644
    --- a/src/game/BattleGroundMgr.cpp
    +++ b/src/game/BattleGroundMgr.cpp
    @@ -828,7 +828,7 @@ void BattleGroundQueue::Update(uint32 bgTypeId, uint32 queue_id, uint8 arenatype
        // there weren't enough players for a "normal" match
        // if arena, enable horde versus horde or alliance versus alliance teams here
    
    -    else if(bg_template->isArena())
    +    else if(!isRated && bg_template->isArena())
        {
            bool bOneSideHordeTeam1 = false, bOneSideHordeTeam2 = false;
            bool bOneSideAllyTeam1 = false, bOneSideAllyTeam2 = false; 
    

    But this part of code was removed, and now I can't understand where and what checkI should set.

    Please, help me. Thanks.

×
×
  • 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