that doesnt make much senseto me. when you would do this the straightforward way you would be affected by the curse anyway (with %range), so there must be an additional check in there that this type of ability only applies to yourself with -100% range.
It's the other way around. The default case is that a buff/debuff affects the thing it's on - there's only a check for aura flags that would prevent that if it has a nonzero radius to affect other things in.
This will definitely be fixed, but I don't know when.
Actually it does. The only difference between an aura and an untimed buff is that untimed buffs have an aura radius of 0.
So by hitting a radius of 0 you are now a target for your aura.
I bet If you somehow gave base aura radius to your aura targets, they'd start projecting the aura too.
Yeah, this is correct. An aura is just a buff/debuff with a radius - it can also have flags limiting which things in that radius it can affect, but not having the radius means it's just a buff/debuff, not an aura, so the flags don't do anything.
I bet If you somehow gave base aura radius to your aura targets, they'd start projecting the aura too.
This can definitely not happen. The buff/debuff from being affected by an aura cannot itself be an aura, because the two cases use some of the same variables to store different data.
devtrackers.gg