Mark_GGG

It's not an increase, it sets it to specific value (unless the aggro radius is already higher than that value). Setting it to that value twice doesn't change anything.

Every time a player uses Death Mark, my dark power grows.

Making Revenants (and a lot of other spectrable monsters) aggressive doesn't change anything - their aggro radius is already higher than the aggressive value (and we made sure aggressive doesn't set the aggro radius to the new value if it would be lower, since that would be very counterintuitive). That doesn't mean the support will be useless, as it does other things as well, but the aggressive property simply isn't useful for them.

I suspect in terms of spectre builds, Death Mark Support will be the bigger gamechanger.

Stats are what actually do things, and you can only have one total value for each stat - all sources of the same stat add together. Mods are basically a wrapper around a set of stats and associated values. One mod can give values to multiple stats. Stats can also be gained in other ways, such as from passive skills.

Think of your character as a chef, serving a variety of different meals of hot fresh DPS to any customers in range. The stats would be raw ingredients - necessary to actually make any of the meals, and which ones you have largely determine which meals you can make. Mods are like the delivery trucks that bring you ingredients - sometimes one truck will bring you multiple ingerdients in a single load, and sometimes mutliple trucks will bring the same ingredient, but once they've been unloaded from the trucks into your kitchen, you don't remember or care which truck a particular tomato came from, you care about the total number of tomatoes in your kitchen. Stats ar...

The thing that allows them to be a different colour is that stats from crafted mods are put into a different container of stats, which then needs described separately. The stats in the item's base container are all described as a set, then the colour is changed and the stats in the crafted stats container are described as a second set. This is also why if a regular mod and a crafted mod give the same stat, they don't sum together.

If they were in the same container they couldn't be a different colour, because they wouldn't be distinguishable from other stats. A design requirement for the crafted mods was that you could see which stats came from those mods, which means they had to be separate.

What happens to a specific passive skill depends both on the jewel seed value and which passive it is. If a new passive is introduced in radius of a jewel socket, then the jewel will change that in a new way. If a passive is removed from the tree or the jewel radius, the jewel will obviously no longer change that passive. Neither of those changes can affect what happens to any other passives.

If a passive is reworked into something new, but internally is still the same one, it will still be modified the same way.

This is correct. The base item view displays the stats, and stat descriptions are ordered by what kind of stats they are.

The advanced mod display describes mods, rather than stats, and they're ordered by the type of mod they are.

When describing the stats it only has the total list of stats - it doesn't have any information about where those stats come from, so what modifiers they're from isn't something that can be part of that (for several other reasons as well - stats can come from multiple sources, for example).

That is not what reduced means in PoE. Reduced and Less work the same way if there is only one modifier - they are only different in how they interact when you have multiple reduced/less modifiers.

It is relevant that Blind is less, because there is at least one other modifier to hit chance in the game for it to stack with, but unless such a second modifier is in play, they will achieve the same thing.

Subtracting directly from the chance would be described as "-x%".

There is no concept of local damage conversion, and adding it would introduce a huge amount of complexity and unintuitive interactions to the system, and remove part of the point of using conversion mechanics in the first place (modifiers to both types applying - because a theoretical local conversion would be entirely on the weapon and only affected by local modifiers, and the player just gets the resulting totals for each damage type).

Practically, 100%, but technically neither. You cannot evade, so no chance to evade/chance to hit value ever gets calculated in the first place.

This is distinct from just having no Evasion Rating, which would not prevent you from being able to evade, but would mean the calculated chance to evade would usually be 0%. In that case the enemy chance to hit is 100%, and if they're blinded then that would affect that chance, which inhernetly brings up your chance to evade.

That is not correct. Those are restrictions to what kinds of values those modifiers will apply to.

For example, the damage of your Fireball spell is Fire Damage, but not attack damage and not bow damage. "increased fire damage" would apply to it, but "increased attack damage" or "increased bow damage" would not.

But if you also have Burning Arrow, that skill will deal (by default) physical damage and fire damage (converted from physical). The physical damage is attack damage and bow damage, so both those modifiers would apply to that value (additive with each other), but the fire damage modifier would not. The fire damage would be affected by all three, so all three would apply additively to the value of fire damage dealt.

The rules is not "all increased modifiers are additive with each other" - as a trivial example, increases to armour are not additive with increases to, say, fire damage, because they are applying to different things. The rule is that all "increased" (and "reduced") modifiers to the same value are additive with each other.

The damage of a weapon item, and the damage of a player using that weapon, are not the same value.

A local stat granting increased damage to a weapon is addtive with other modifiers to the damage of the weapon - multiple such modifiers on the same item stack additively. They are all affecting the base physical damage the weapon has from it's base type. The final result of applying all such modifiers provides the total damage of the weapon, which is displayed above the mods (as noted elsewhere in the thread, if a weapon's physical damage is modified it's value will be displayed in blue to show this, while elemental and chaos damag...

Shatter would not prevent this. Shatter destroys things after hitting them, if they are then dead. It thus happens after anything that is processed at the time the thing dies.

This is all correct

Physical Damage taken from attacks: This stat is gained from some equipment, and applies after armor, but before reduced/less sources. Not sure why, because flat damage reduced is monumentally more valuable if it's lopped off the last step, and it's not like this -X damage stat is too strong.

Because that's how all modifiers are applied in PoE. flat additions to the base are applied before percentage modifiers. Otherwise +life bonuses wouldn't benefit from % increased life bonuses, etc. So in PoE, additions and subtractions apply before multiplications. My high school maths teachers would probably be very disappointed in me if they knew.

There is only one exception to this, being the "+/-x to Total Mana Cost of Skills" modifier, which specifies it applies to the total value, and thus applies after other modifiers. It is an abberation, and deserves to be shunned for it's mockery of the rules of the game....

Armour provides an amount of Physical Damage Reduction against each hit dependant on your armour value and the amount of physical damage in the hit. Additional Physical Damage Reduction is just that - additional to the base physical damage reduction provided by your armour.

This is entirely separate from "reduced Physical Damage taken", which is applied afterwards and additive with other increases or reductions to damage taken.

The player is causing the explosions. The shrine granted a buff to the player that gives them a stat causing things they kill to explode.

PoE seems to very slowly lure enemies towards you after you've cleared an area

For the record, this does not actually happen.

Monsters very far from the player(s) are asleep and cannot do anything.

Monsters which are close enough to the player to be awake, but cannot see the player will wander at random, which can sometimes bring them close enough to see the player, or may move them far enough away that they're put to sleep, and pause until the player gets closer again. They are not lured, and they are no more likely to wander towards the player than away.

Several on-death explosions can occur at once, yes. However, in this case, these stats are both supplying a chance for the same explosion, not two different ones. Just like how a hit can inflict multiple ailments, but two sources of chance to freeze will add together, not roll separately to inflict two separate freezes, these two stats are chance to cause the same explosion, so the chance adds together. Other, different explosions will have independant chances to occur, and multiple such explosions can occur.

Obliteration and Profane Bloom have definitely never worked the way you imply here. Both stats are providing a chance for the same thing - they add the chance together, just like multiple sources of chance to freeze.

If you have stats causing different kinds of on-death explosions, those are separate, and roll their chances (if they have them) separately, and multiple such different explosions occur. But in this specific case, the OP is asking about two stats that are providing a chance for the same explosion (25% of life as chaos).

Agony Crawler does not cause explosions. The Gloom Shrine on the player does.