Hulk Ragnarok's "Face me" bug! [with detailed proof]!

KarinshiKarinshi Posts: 111
edited February 12 in Bugs and Known Issues
x155fu6vsvd9.jpg
nme3tuh3jdch.jpg
nr2i07m7b996.jpg

As you can see, I'm regaining back only 40% of the damage taken instead of 80% ( I have recovery max "+15%")

edit: Other side notes ::
* this is sig 8 Gulk at 5/50 vs sig 200 Magik 5/65
* although I'm sure this is not important but I will share it anyway : I'm using iPad mini 4 with iOS 11.2.5 using latest version of the game "17.0.2"
* here is the whole video of the fight that I take photos from : https://youtube.com/watch?v=lhE51xKQrqA&feature=youtu.be skip to 0:30
* this is in Dual (same thing happened in war https://youtube.com/watch?v=J3ejcoiS9Bo )

Comments

  • Redwulf67Redwulf67 Posts: 42
    edited February 12
    Seems wierd.
  • taojay1taojay1 Posts: 284
    So you are referring to the recoil damage only, right
  • KarinshiKarinshi Posts: 111
    yes, the bug is related to recoil damage
  • I'm not sure you can call that a bug. The wording of the description is ambiguous at best as it really doesn't explicitly state ALL damage taken, just damage. It also doesn't explicitly state which damage type you recover from. Call me pedantic, but the choice of wording matters as I interpreted it to mean you only recovered from the damage over time and not ALL damage taken while under face me. I don't use recoil so I never knew you regened some of the health back if you did, and I don't see him regen from all damage over time debuffs either (coldsnap can be considered both passive and active, as he does nothing to gain it at the start of the fight, but be awakened).

    Hyperion still has a description that states he has a cosmic overcharge that doesn't actually exist, in his description, so I take those descriptions with a salt block (a grain is way too small). The written descriptions on a lot of these abilities are really poorly worded and I doubt they will ever go back and clarify the ones that are ambiguous like this. Just another example of poor quality control.
  • KarinshiKarinshi Posts: 111
    I'm not sure you can call that a bug. The wording of the description is ambiguous at best as it really doesn't explicitly state ALL damage taken, just damage. It also doesn't explicitly state which damage type you recover from. Call me pedantic, but the choice of wording matters as I interpreted it to mean you only recovered from the damage over time and not ALL damage taken while under face me. I don't use recoil so I never knew you regened some of the health back if you did, and I don't see him regen from all damage over time debuffs either (coldsnap can be considered both passive and active, as he does nothing to gain it at the start of the fight, but be awakened).

    Hyperion still has a description that states he has a cosmic overcharge that doesn't actually exist, in his description, so I take those descriptions with a salt block (a grain is way too small). The written descriptions on a lot of these abilities are really poorly worded and I doubt they will ever go back and clarify the ones that are ambiguous like this. Just another example of poor quality control.

    do you know that I can take sp3 while under DOT effect, and I can recover back 80% of it? this is clearly a bug related to suicide mastery, probably mathematics error while programing
  • Hey everyone!

    I've passed this along to the rest of the team. Once it's looked over more and I have a further update, I'll be back to share what I know. :)
  • buffajrbuffajr Posts: 62
    Karinshi wrote: »
    yes, the bug is related to recoil damage
    Why would you bring this up to anyone?
  • bloodyCainbloodyCain Posts: 151
    It is a bug. If we wanna say that Recoil doesn't consider as "Damage Taken" when Face Me is active, then he should recover 40% in the first place.
    It's clearly a bug. Damage Taken = Damage that you take = All damage.
    Great details in explaining it, @Karinshi. Nice
  • KarinshiKarinshi Posts: 111
    buffajr wrote: »
    Karinshi wrote: »
    yes, the bug is related to recoil damage
    Why would you bring this up to anyone?

    so that they can fixit, duh?
  • KarinshiKarinshi Posts: 111
    bloodyCain wrote: »
    It is a bug. If we wanna say that Recoil doesn't consider as "Damage Taken" when Face Me is active, then he should recover 40% in the first place.
    It's clearly a bug. Damage Taken = Damage that you take = All damage.
    Great details in explaining it, @Karinshi. Nice

    thanks for sharing your opinion, glade someone is acknowledge it, hopefully it will be fixed soon
  • KarinshiKarinshi Posts: 111
    Hey everyone!

    I've passed this along to the rest of the team. Once it's looked over more and I have a further update, I'll be back to share what I know. :)

    Thanks, please share any further updates regarding this bug as soon as possible
  • @Karinshi Winner for best detailed explanation and proof of concept.
  • KarinshiKarinshi Posts: 111
    @Karinshi Winner for best detailed explanation and proof of concept.

    thank you ;-)
  • bloodyCainbloodyCain Posts: 151
    bloodyCain wrote: »
    It is a bug. If we wanna say that Recoil doesn't consider as "Damage Taken" when Face Me is active, then he should recover 40% in the first place.
    It's clearly a bug. Damage Taken = Damage that you take = All damage.
    Great details in explaining it, @Karinshi. Nice

    correction: then he shouldn't recover 40% in the first place.
  • KarinshiKarinshi Posts: 111
    bloodyCain wrote: »
    bloodyCain wrote: »
    It is a bug. If we wanna say that Recoil doesn't consider as "Damage Taken" when Face Me is active, then he should recover 40% in the first place.
    It's clearly a bug. Damage Taken = Damage that you take = All damage.
    Great details in explaining it, @Karinshi. Nice

    correction: then he shouldn't recover 40% in the first place.

    re read the OP again, and hmmmm, again, until you see what was my point !!
    thanks for your opinion anyway ;)
  • KarinshiKarinshi Posts: 111
    Any update regarding this bug from Kabam team?
  • It's being investigated for a fix. No further update at the time.
  • SnaggleSnaggle Posts: 162
    It's being investigated for a fix. No further update at the time.

    "being investigated"
  • KarinshiKarinshi Posts: 111
    It's being investigated for a fix. No further update at the time.

    thanks for your replay, please keep us updated when there is any news regarding this
Sign In or Register to comment.