Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I set up an island with a materializer to summon a Shrooman Brute then let a Fanhare and a summoned Sprout loose on it for about 10-15mins - even after seeing the Shrooman poisoned over and over it never triggered.
I checked to make sure it was actually working with a Druida ring and a Stormbringer - sure enough after a sec or 2, sheet crit chance shot up like it should.
So, no, summons nor pets trigger Ivy's.
EDIT: I sent in a bug report to them referencing this thread, we'll see what they say about it.
So it should be possible.... wonder why it's not working.
So it seems the game is coded for you to get the bonus when you apply the poisoned, not against poison targets generally.
I guess it makes sense, but I'd rather they improved the wording a bit.
if after a monster is poisoned you see no more non crits....
I'd still like it if the pet, the summon, and the player was counted the same so that a summon poisoning a monster would trigger the ivy set to increase my own crit chance.
Same Shrooman Brute trick, Fanhare and Sprout. I thought it was working for minions at first, damn RNGesus throwing the minion 4 crits in a row on occasion. Then I reset minion skills for 0% crit chance and nada... no sheet increases and no visual evidence of crits.
Didn't think it would affect them tbh, but worth checking these things eh?
But I'm slightly too lazy to post it as a bug on the website, heh.