and stating it explicitly would make Herald of Ash awkward to read in a way that could add to confusion
As suggested in this very post, "your overkill damage" instead of "the overkill damage" would make it clear on a careful reading and add zero confusion.
Y'all have a bad habit of declaring "impossible to word" when there are available wordings there with a little thought.
(It's actually part of a larger trend where y'all claim that it's impossible to make interface changes that make things clearer despite many, many player-provided examples on this sub showing the opposite. Hire a UX person for the love of god, please.)
As suggested in this very post, "your overkill damage" instead of "the overkill damage" would make it clear on a careful reading and add zero confusion.
That would absolutely add confusion for some players.
"While you have this buff, if you kill an enemy, other enemies near them will be burned based on your overkill damage."
"your" is really awkward there, and makes the "your overkill damage" part sound like some keyword phrase which is a property of the player character rather than part of the killing event. It feels weird to specify the overkill damage is "yours" there, and not entirely intuitive that overkill damage conceptualy is "yours" when it's fundamentally defined more by the enemy it's happening to than you being what dealt it.
That doesn't mean the current wording is perfect or no improvements are possible, but they have to be carefully considered, and the text is serving it's...
Read moreHerald of Ash requires you deal a killing blow, not just kill. This isn't stated explicitly because it's implicit in the fact that it requires overkill damage, which is only possible from a killing blow, and stating it explicitly would make Herald of Ash awkward to read in a way that could add to confusion. This might get re-examined at some point, but care would have to be taken not to sacrifice clarity for new players reading Herald of Ash and trying to understand just that skill, to aid clarity around a specific very niche interaction with a unique item most players will never see.
Hey Mark can boneshatter self damage crit if you are wearing a legacy reckless defense which has the line +x % additional Chance to receive a Critical Strike
No, it would need to force a crit, not rely on the chance - the crit roll for that damage is zero.
This actually means it will always crit in this case, which is not intended, and it will be changed to make a crit roll such that it can interact with stuff adding a crit chance in an intuitive and sensible way in future.
Whatever method you use to collect the data is flawed then -- I think perhaps some people are giving you fabricated data and just copy/pasting from previous notes that they used or something. Are you incentivizing this data collection somehow? Because it's not accurate and the jewels do in fact change from league to league... as stated by GGG themselves (yes, this information comes directly from the devs so it's NOT up for debate).
You have definitely misunderstood something, as what you are claiming is incorrect.
The system by which the modifications to the tree are determined by the seed has intentionally not been changed since it was introduced, so that the items can continue to function the same way. The Historic jewels actually even have an internal "version" value which was included so that if we ever needed to make such changes, we could have them only apply to new gems and distinguish them in some way by describing the version stat, but we haven't had to actually use that so far.
As noted above, changes to the tree do change the results (and some potential changes to the tree might not be obvious or visible to players, but those would be rare), because the passive skills themselves are inherently one of the inputs. But outside of that, the results of a historic jewel don't change unless it's seed does.
In fact there's a minor bug in the code for making those modifications which...
Read morewhich might actually be true. But it does not say, whether the debuff is assigned a hit.
Maybe /u/Mark_GGG can answer this: Is the explosion caused by the fuse debuff of exploding arrow counted as a hit by the player (i.e., do on hit effects like raiders generic "frenzy charge on hit" trigger?) or a hit by the debuff? If the answer is "player", is this because a debuff is not an entity that can be assigned a hit?
Maybe /u/Mark_GGG can answer this: Is the explosion caused by the fuse debuff of exploding arrow counted as a hit by the player
Yes
If the answer is "player", is this because a debuff is not an entity that can be assigned a hit?
Not really - a debuff is fundamentally not a game object and can't hit things, but even if it could that wouldn't be what's happening here. The damage is directly caused by your skill which you used.
...
Read more
devtrackers.gg
