Options

Are Quick heals supposed to do this??

MrSanguiniMrSanguini Member Posts: 197 ★★
So, I was a hair deep into necropolis, and I ran out of heals. Decided to use quick heals to top up Kate with units. I tapped the button- nothing happened. Tapped again- nothing. So I tapped it a few more times, mostly out of frustration.

Then, after like 15 more seconds, the game decides to heal Kate. Again, and again, and again, and again. She's at full HP but the 'quick heal used' message pops up like 12 times in sequence. And of course, it charges me (in units) over 12 times. Wonderful.

Is this intended behavior? Because when I immediately went to open a ticket, Kabam closed it within seconds (with absolutely no response on the matter).

Comments

  • MrSakuragiMrSakuragi Member Posts: 6,821 ★★★★★
    There is no cap on using the quick heal and it won’t stop you from healing someone that doesn’t need it. So expected behavior there I guess. Lagging and the game catching up with inputs is unfortunate and I’d hope support would offer help and not just close the ticket.
  • Average_DesiAverage_Desi Member Posts: 2,734 ★★★★★
    Contact support
  • MrSakuragiMrSakuragi Member Posts: 6,821 ★★★★★

    Contact support

    He did… lol
  • SummonerNRSummonerNR Member, Guardian Posts: 14,664 Guardian
    edited April 2

    Contact support

    He did… lol
    “He” ? (not “you” or “I” ?)
    (thought it was OP saying “He did”. Didn’t notice you're actually different names)


    But, YES, has been mentioned many times up here that unfortunately happens to people.

    Seems like the 2nd time still processes it as if it were the first time (as far as where the health of champs is at), so it duplicates, triplicates, etc, etc the same cost.

    If the 2nd time would at least NOT happen until the first time has processed (aka, the 2nd processing doesn’t just queue up a “blind” quick heal, but it goes back out at the time of processing to see what the current state is at AT THAT TIME), then at least it would know to not process any more duplicates.
  • Average_DesiAverage_Desi Member Posts: 2,734 ★★★★★

    Contact support

    He did… lol
    Oh, I missed that.
  • MrSanguiniMrSanguini Member Posts: 197 ★★

    There is no cap on using the quick heal and it won’t stop you from healing someone that doesn’t need it. So expected behavior there I guess. Lagging and the game catching up with inputs is unfortunate and I’d hope support would offer help and not just close the ticket.

    That may be true, but my suspicion of it being unintended comes from the fact that you can’t quick heal a full HP champ. The button doesn’t even appear. So really this is working around what should be a fail safe for not accidentally wasting quick heal on a healthy champ.

    I’d love to hear it from Kabam themselves but like I said, closed ticket.
  • MrSanguiniMrSanguini Member Posts: 197 ★★

    Contact support

    He did… lol
    “He” ? (not “you” or “I” ?)
    (thought it was OP saying “He did”. Didn’t notice you're actually different names)


    But, YES, has been mentioned many times up here that unfortunately happens to people.

    Seems like the 2nd time still processes it as if it were the first time (as far as where the health of champs is at), so it duplicates, triplicates, etc, etc the same cost.

    If the 2nd time would at least NOT happen until the first time has processed (aka, the 2nd processing doesn’t just queue up a “blind” quick heal, but it goes back out at the time of processing to see what the current state is at AT THAT TIME), then at least it would know to not process any more duplicates.
    Sad way to lose 800 units
Sign In or Register to comment.