Howard the Duck Purple Can't Cast Twice?(merged)[Devs Aware]

orbitalint
orbitalint Posts: 511 Critical Contributor
Hi there,

Just finished up the Crash today (3/29/17) and was trying to accelerate the win with my low level Howard but it refused to cast the purple twice. It kept saying it didn't have enough valid targets and there were plenty more purple tiles create them on. I'm assuming because he was already invisible that it wouldn't do it but I feel like you used to be able to keep spamming purple to increase the number of tiles and do more damage.

I submitted a ticket as well and screenshots are below.

My Howard is level 127 at 0/2/3.

Current Board - http://imgur.com/a/4kRFn
Power - http://imgur.com/a/6OWeN
Error - http://imgur.com/a/hD1QS

Comments

  • firethorne
    firethorne Posts: 1,505 Chairperson of the Boards
    Got the same. I was able to cast it again once my last invisibility tile had been matched, so that is the reason. If this is the intended behavior, then the skill text should be updated to include some "If none exist" type language.
  • Jaedenkaal
    Jaedenkaal Posts: 3,357 Chairperson of the Boards
    Today I noticed that Howard the Duck is not able to use Duck Duck Loose when he is already invisible. An error message pops up that says "there are no valid targets for this ability" or somesuch, although there were plenty of basic purple tiles lying around.

    The power description does not support this functionality, and I believe it did not always work this way; I recall being able to fire it multiple times while invisible.

    Thanks.
  • orbitalint
    orbitalint Posts: 511 Critical Contributor
    Ditto, posted the same here if mods want to merge.

    viewtopic.php?f=9&t=62460
  • Dayv
    Dayv Posts: 4,449 Chairperson of the Boards
    Merged two threads reporting this.
  • Tombstone
    Tombstone ADMINISTRATORS Posts: 1,208 Chairperson of the Boards
    Hi everyone, thank you all for bringing this issue to our attention! Letting you all know that the developers are aware of this issue occurring and that they are currently working on a fix for a future build.