I don't want to have to recast my auras in every zone

UPDATE: Spent some of the morning talking to Jonathan about this - we're now confidant in getting the aura snapshotting fix in for 1.2.0, and we've fleshed out plans for the minion snapshotting fix some more as well.

"

Michaelangel007 wrote:

"

Mark_GGG wrote:

It's unfortunately a very technically challenging bug to solve. ...
We could fix pretty much all instances of aura snapshotting at the cost of a day or so's work, a little extra processing, and making auras never be able to transition between areas. That last part isn't worth the cost.

Huh?? You already have something like this ... excuse the lack of proper forum support for code/preformatting ....

enum Auras {
. AURA_ANGER = (1 << 0),
. AURA_CLARITY = (1 << 1),
. AURA_DETERMINATION = (1 << 2),
. AURA_DISCIPLINE = (1 << 3),
. AURA_GRACE = (1 << 4),
. AURA_HASTE = (1 << 5),
. AURA_HATRED = (1 << 6),
. AURA_PURITY_ELEMENTS = (1 << 7),
. AURA_PURITY_FIRE = (1 << 8),
. AURA_PURITY_ICE = (1 << 9),
. AURA_PURITY_LIGHTNING = (1 << 10),
. AURA_VITALITY = (1 << 12),
. AURA_WRATH = (1 << 13)
};

class Player
{
. ...
. int32 bAurasPreviouslyOn;
. int32 bAurasActive; // bit-flags of auras currently active
};

Player::OnZoneLeave()
{
. bAurasPreviouslyOn = bAurasActive;
}

Player::OnZoneEnter()
{
. if( bAurasActive != bAurasPreviouslyOn )
. ....
}

I'm not sure why you'd think auras are some form of bitset, particularly given that a character could have any number of different versions of the same aura with different levels, quality and supports. I'm afraid the only part of that code which remotely resembles anything in the game is that "class Player" exists as a class. I'm not saying this to be harsh or put you down, so I apologise if it comes off like that, but no, we don't have anything like that in the code, and your assumptions about how the code works are significantly off-base.

"

Legatus1982 wrote:

I don't understand Mark, what is so difficult about running a check on buffs every time gear is swapped?

The part where you abstract all the actual problem away as "running a check" without defining any details of what that means. That part.

"

Legatus1982 wrote:

I can right click and remove the buff myself. I could, in fact, probably fix your problem using autohotkey to right click the buff icon whenever I remove a piece of gear. (Would require manually activating the hotkey script but it would work).

So you're going to have to forgive me for being unable to come up with a reason why the programmers can't take 20 seconds to right click the buff icons for anything that isn't RF or BR whenever gear is swapped.

I already said in my post we could solve all aura snapshotting by preventing auras from ever transitioning between areas, but that the massive quality-of-life cost of that to all players was too much for the benefit. You're correct that we could solve it also by having all auras turn off any time you change your gear in any way (which happens a lot more than I suspect you reaslise). But that would be even worse for player QoL.

The correct solution is not to remove everyone's auras all the time. It's to be able to replace them, on the fly, with up-to-date versions, in response to stat changes. That is, as I mentioned, technically challenging, for the reasons I explained.

"

SilentOppressor wrote:

Will this upcoming change prevent RedMana 'snapshotting'? Basically if you cast two auras with RedMana and then remove the gem, will it uncast them both?

The auras will no longer have blood magic, so they'll no longer reserve mana.
Ideally, they'd switch to reserving mana, and fall off if they don't fit there because too much mana is already reserved. Actual behaviour may depend on the details of the solution, so they may just always fall off, to switch to mana and an arbitrary set of auras are removed (not necessarily those ones) until your mana reserves are back under 100% of mana (this is the default behaviour for overreserving).