Vivien's Invocation not working correctly [Fix in 3.6]

Azerack
Azerack Posts: 501 Critical Contributor
I have tried multiple times both in TG and ToZ with 3 different creatures in library and found..

1. It will not always give you three DIFFERENT creatures, but theoretically the top 3 in your library.
2. It will not always damage the first opponent creature, ignoring that part and just adding the creature to the battleground.

2.a - If it DID damage the first creature, the next creature added via Invocation, even if a stacked version of the first creature, will not damage the first opponent creature. This always happens, so far.

This is one of greens most useful cast and damage w/out targeting. Please fix this soon!

Additional note: 
2.b - Just had a situation where Invocation DID damage the first target and, contrary to 2a. the next two naturally cast from my hand that stacked that creature ALSO did damage to the opponent's first creature as if cast by Invocation. 

//Edited Title - Tombstone

Comments

  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    Thank you for the report. I've gone ahead and passed this information along to the team for review. 
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    edited June 2019
    Tombstone said:
    Thank you for the report. I've gone ahead and passed this information along to the team for review. 
    Quick update:  after some testing I think I figured it out.

    1:  Invocation will only see the next three creatures in your library, not next 3 DIFFERENT creatures like it used to (like it says on the card)

    2:  The damage dealt by Invocation is equal to the power of the creature AFTER it is put on the battlefield, not the creature's base power like it was before (note that this was slightly bugged before with creatures that buff themselves on ETB and that was what the team was trying to fix with this update.  Instead they made it worse)

    3:  If you have a creature out and use invocation to fetch a DIFFERENT creature that is not already on the field it will deal no damage.  As best as I can tell damage is dealt in all other cases (including when reinforcing your second or third creature), but obviously I haven't tried it in every possible scenario, because that's not my job.

    Hope this helps!
  • Azerack
    Azerack Posts: 501 Critical Contributor
    Mburn7 said:
    Tombstone said:
    Thank you for the report. I've gone ahead and passed this information along to the team for review. 
    Quick update:  after some testing I think I figured it out.

    1:  Invocation will only see the next three creatures in your library, not next 3 DIFFERENT creatures like it used to (like it says on the card)
    - This is what I discovered, as well.

    2:  The damage dealt by Invocation is equal to the power of the creature AFTER it is put on the battlefield, not the creature's base power like it was before (note that this was slightly bugged before with creatures that buff themselves on ETB and that was what the team was trying to fix with this update.  Instead they made it worse) - ONLY if if actually deals damage. Not all creatures deal damage, For instance, I summon Zacama or Ghalta, no damage, Gisath, however, DID get a damage proc. Verdant Sun's Avatar also no damage. One play when Ghalta was out he DID proc damage, though (see 2.b, above). It's not 100% that creatures will deal ANY damage, though, as the proc just doesn't occur.

    3:  If you have a creature out and use invocation to fetch a DIFFERENT creature that is not already on the field it will deal no damage.  As best as I can tell damage is dealt in all other cases (including when reinforcing your second or third creature), but obviously I haven't tried it in every possible scenario, because that's not my job.
    - See my 2 and 2.a above.

    Hope this helps!
    Appreciate the extra info, but unfortunately it's not even as consistent as you encountered. 
  • Monkeynutts
    Monkeynutts Posts: 566 Critical Contributor
    2 of 3 times casted today the creature did not deal damage to opposing creature as it has previously.

    How are thing that have never been broken now broken....
  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    Hi everyone just as an update, this issue is scheduled to be fixed in the upcoming 3.6 update. 
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Tombstone said:
    Hi everyone just as an update, this issue is scheduled to be fixed in the upcoming 3.6 update. 
    Can you confirm which issue will be fixed?  The inconsistent damaging, the incorrect fetching (next 3 instead of next 3 different), the inability to cast without an opponent creature out, or all of the above?
  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    As of now I can confirm the fetching issue will be corrected with 3.6.

    Are you all still currently encountering issues with this card dealing the damage equal to the selected creature's power?  

  • soultwist
    soultwist Posts: 325 Mover and Shaker
    Right now it deals the amount of damage printed on the card selected.  Only other problem I am having is the opponent needs to have a creature or the card wont cast at all.
  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Tombstone said:
    As of now I can confirm the fetching issue will be corrected with 3.6.

    Are you all still currently encountering issues with this card dealing the damage equal to the selected creature's power?  

    I have not had any more issues with that. Was it fixed already?  I don't remember seeing an announcement or anything. 

    What about the issue where the spell cannot be cast if your opponent does not have any creatures out?