"Phantasm's" affix is for two modifiers?

I am using poedb.tw and found out that "Phantasm's" has two items attached to it

Phantasm's 60 (68–79)% increased Evasion Rating
Phantasm's 79 +(301–375) to Evasion Rating +(73–80) to maximum Energy Shield

https://poedb.tw/us/Body_Armours_dex (#% increased Evasion Rating )
https://poedb.tw/us/Body_Armours_dex_int (# to Evasion Rating # to maximum Energy Shield )

I thought affix name is unique, if it is not unique, what's the point?

I am doing HasExplicitMod in filters and want use one but not other.

"

Mmmoooz wrote:

I thought affix name is unique

Where is the bug????

Both one hand and two hand T1 physical damage mods are known as "Flaring", they have different internal use ids

Two different modifiers do different things but have the same name.

As a side-effect, you can't easily filter out another cause both are within one item class. For now, you should list all interesting es/eva base types and filter just them by explicits.

"

MonaHuna wrote:

Two different modifiers do different things but have the same name.

As a side-effect, you can't easily filter out another cause both are within one item class. For now, you should list all interesting es/eva base types and filter just them by explicits.

you know every Shaper prefix has the same name right?

"

neohongkong wrote:

"

MonaHuna wrote:

Two different modifiers do different things but have the same name.

As a side-effect, you can't easily filter out another cause both are within one item class. For now, you should list all interesting es/eva base types and filter just them by explicits.

you know every Shaper prefix has the same name right?

For "specialty" mods, like Shaper/Elder/etc influence, it's normal. For basic mods, it's not.

I can't think of another instance of basic item mods that share the same name but do two completely different things. Different value ranges on different item classes, such as Flaring +phys on 1h vs +phys 2h, yes. Totally different functions, in OP's case with Phantasm's %increased evasion on DEX bases vs +eva/+ES on DEX/INT bases, no.

It's definitely not normal. Not a bug exactly, but an oversight on GGG's part.

"

aggromagnet wrote:

"

neohongkong wrote:

"

MonaHuna wrote:

Two different modifiers do different things but have the same name.

As a side-effect, you can't easily filter out another cause both are within one item class. For now, you should list all interesting es/eva base types and filter just them by explicits.

you know every Shaper prefix has the same name right?

For "specialty" mods, like Shaper/Elder/etc influence, it's normal. For basic mods, it's not.

I can't think of another instance of basic item mods that share the same name but do two completely different things. Different value ranges on different item classes, such as Flaring +phys on 1h vs +phys 2h, yes. Totally different functions, in OP's case with Phantasm's %increased evasion on DEX bases vs +eva/+ES on DEX/INT bases, no.

It's definitely not normal. Not a bug exactly, but an oversight on GGG's part.

It will be the matter of feedback section.......


And since the two mods are not actually from the same base (body armor dex and body armor dex-int) . Unless you use recombinator , they cannot appear on the same item. Item filter issue is another thing.




And just find another example:

Mammoth's (39-42)% increased Armour, (16-17)% increased Stun and Block Recovery

Mammoth's(39-42)% increased Armour and Evasion, (16-17)% increased Stun and Block Recovery

So that it is not a lone exception

I honestly don't think you're making even the slightest attempt at understanding the discrepancies (there are more than one) between the two Phantasm's mods. But that's ok, it's not very relevant for the OP that you do.

Help and Discussion was also the appropriate place to post first, since OP didn't know what was going on.

But yeah, @OP, Feedback is probably a good place to go with this now. I'd just be very clear about exactly what you're seeing and how/why it's a problem for you (or anyone else trying to filter by that mod). You can get around the problem by being giving your filter a bit more depth for this, but it does involve a lot more steps that you shouldn't have to take.

"

aggromagnet wrote:

I honestly don't think you're making even the slightest attempt at understanding the discrepancies (there are more than one) between the two Phantasm's mods. But that's ok, it's not very relevant for the OP that you do.

Help and Discussion was also the appropriate place to post first, since OP didn't know what was going on.

But yeah, @OP, Feedback is probably a good place to go with this now. I'd just be very clear about exactly what you're seeing and how/why it's a problem for you (or anyone else trying to filter by that mod). You can get around the problem by being giving your filter a bit more depth for this, but it does involve a lot more steps that you shouldn't have to take.

Go feedback section and post a full list of mod that have the same name and your idea on new name......

Yikes, dude. Moving on...

Yeah, move on......yet screaming for change without formulate a formal proposal to GGG via feedback section and this thread is wiped by support staffer out of bug report section to aka recycle bin section of the forum


Flaring and Mammoth's can both be explained by it is both T1 mod and "similar" function


But when you suggest GGG should not recycle the name of Phantasm's for the new t1 mod that introduce not really long ago, you really really need to provide full picture to GGG that how many these cases exist. Or just accept that naming mod is hard and they did recycled the mod name but the two mods can't be on the same base (unless you consider all body armor are the same, not having dex/int/str/hybrid variants)