Galan has had a major bug for at least the last 4 months/updates and no one is acknowledging it.
ArmoredGhost
Member Posts: 259 ★★★
When he is in harvest mode his sp2 is supposed to place 9 incinerates on the opponent (3 incinerates per each of the last 3 hits of sp2). Now however he has been placing only 7. This has been a problem for at least 4 months/updates now.
It might not sound like a lot but it is very relevant. First there's just the obvious missing damage. Those 2 incinerates have made the difference in BG for me quite a few times now. I've had the incinerates end just before they would have killed the opponent and then that leads to lost time as well as the chance to mess up and take some damage. I'm sure the same effect has happened on defense too.
Then there's also the despair mastery to consider. Those incinerates are important for blocking healing which is also very useful in BG specifically against champs with strong regens or even just the willpower mastery. If you have 3/3 points in despair mastery thats a difference of 105%-135% heal reduction (I am still a little unclear if despair does anything like reverse regen past 100%). More relevantly though, if someone only has 2/3 points in despair that's a difference between 70% and 90% regen reduction.
The main part I have issue with though is that each month since this bug's existence I have sent support tickets explaining this issue and yet it hasn't been added to the trello board for known issues. This is especially frustrating because bugs that are more recent and less relevant/important have been added (such as visual issues on Captain Marvel's sp3). This is borderline completely irrelevant whereas Galan's bugg is actually effecting his damage and utility.
Another aspect to this is that Sentry has a listed bug where he "loses his combo shield under 10 hits resulting in his indestructible not triggering as often as it should". This is certainly an important issue for sentry but the main difference between Galan and Sentry is that Sentry is very outdated and irrelevant in the current meta. No one uses him anywhere, no one ranks him up, or uses him for defense. On the other hand Galan has a presence everywhere in the contest. He's a very good defender, a very good attacker, very good for BG, Incursions, Arena, AW, AQ, and just normal everyday Questing. Thus, players will be feeling Galan's bug much more than Sentry's.
I want to be clear that I don't have any animosity towards the team at Kabam. I understand these are very complex issues and things can sometimes fall between the cracks. It's just a little frustrating after such a long time. So my question to Kabam is why has this gone on for such a long time without being acknowledged and added to the trello board? When I've sent the support tickets about this point I have been repeatedly told that this issue will be sent up the chain to the proper teams but clearly that hasn't happened. As it stands though I can't help but feel that Kabam wants to keep this quiet since Galan is such a strong champion and this is acting as a silent nerf (even though I know Kabam's official policy is that there will never be a silent nerf but this isn't exactly helping that case). All I'm asking at this point is for the bug to, at the very least, be listed on trello so I know it has been acknowledged and it may be addressed.
@Kabam Miike what say you?
It might not sound like a lot but it is very relevant. First there's just the obvious missing damage. Those 2 incinerates have made the difference in BG for me quite a few times now. I've had the incinerates end just before they would have killed the opponent and then that leads to lost time as well as the chance to mess up and take some damage. I'm sure the same effect has happened on defense too.
Then there's also the despair mastery to consider. Those incinerates are important for blocking healing which is also very useful in BG specifically against champs with strong regens or even just the willpower mastery. If you have 3/3 points in despair mastery thats a difference of 105%-135% heal reduction (I am still a little unclear if despair does anything like reverse regen past 100%). More relevantly though, if someone only has 2/3 points in despair that's a difference between 70% and 90% regen reduction.
The main part I have issue with though is that each month since this bug's existence I have sent support tickets explaining this issue and yet it hasn't been added to the trello board for known issues. This is especially frustrating because bugs that are more recent and less relevant/important have been added (such as visual issues on Captain Marvel's sp3). This is borderline completely irrelevant whereas Galan's bugg is actually effecting his damage and utility.
Another aspect to this is that Sentry has a listed bug where he "loses his combo shield under 10 hits resulting in his indestructible not triggering as often as it should". This is certainly an important issue for sentry but the main difference between Galan and Sentry is that Sentry is very outdated and irrelevant in the current meta. No one uses him anywhere, no one ranks him up, or uses him for defense. On the other hand Galan has a presence everywhere in the contest. He's a very good defender, a very good attacker, very good for BG, Incursions, Arena, AW, AQ, and just normal everyday Questing. Thus, players will be feeling Galan's bug much more than Sentry's.
I want to be clear that I don't have any animosity towards the team at Kabam. I understand these are very complex issues and things can sometimes fall between the cracks. It's just a little frustrating after such a long time. So my question to Kabam is why has this gone on for such a long time without being acknowledged and added to the trello board? When I've sent the support tickets about this point I have been repeatedly told that this issue will be sent up the chain to the proper teams but clearly that hasn't happened. As it stands though I can't help but feel that Kabam wants to keep this quiet since Galan is such a strong champion and this is acting as a silent nerf (even though I know Kabam's official policy is that there will never be a silent nerf but this isn't exactly helping that case). All I'm asking at this point is for the bug to, at the very least, be listed on trello so I know it has been acknowledged and it may be addressed.
@Kabam Miike what say you?
2
Comments