As seen in this thread alone, players will sometimes have very different experiences with the same fight. For example, my Battlegroup had zero issues with her and mowed right through with revives to spare - yet another Battlegroup in my same Alliance has been struggling hard.
Regardless of my own experience, I already brought the situation to the team and voiced the negative experience of the fight many have faced.
I’m not in charge of the tuning of the fight, so I can’t sit here and tell you what will happen in the future, especially at 2am on a Monday... but we want you to have fun playing our game - that’s a top priority for us.
We all knows it’s not a big or a mistake . It’s just Kabam pulling its usual bs hoping that there would be dumb enough to spend money on potions . Then as soon as they see that even the usually submissive Kabam community can’t stand this bs they would suddenly “fix “ the problem. Ugh hate this corporate bs so much . Just do a goddamn good game
It is might not be bug, but it is extremely poorly design.
With the fiscal from the last Raid (which actually did not properly resolved), we now have this.
It would be good if Kabam development team actually test their content before release (at least the bug stuffs like AW, Raid and Eng game content), instead of using the players asguinea pig.
It is good that some players doesn't have problen with this fights, but it is also clear that many other are really struggled with this fight, because it is unbalanced.
We all want to enjoy the game too, but as players not beta tester. It is getting hard yo enjoy the game when thing like this keep happening. I don't we have had a Raid run without bug yet.
They really can't do anything right these days lol and some are still under the impression that the game is in a good state 💀
There is a difference between real bug consider that’s. The shield is reduced it just stil to high that’s two different things.
I wasn't talking about bugs... Regardless of it being a bug or just bad design on their part doesn't change the fact that this year has been plagued by both bugs and bad design (starting with that unkillable Absorbing Man in the first WoW fight lol).
Played as best as I can, completed all tasks as fasted as I can, maintain my Degen and Buff, didn't get a single hit, did the full available time and only got 2% off.
Not sure how Kabam think this is alright content to release.
Just couldn't get the shield down until maybe 20 seconds left. By then it was a case of just trying to get as much damage done as poss. Wasnt very successful at that either. Not sure I'm doing it right.
They are not . This is not a mistake, this is absolutely deliberate. This is typical corporate bs that try to squeeze every cent out of gamers . I bet the actual programmers told them that this was a bad idea but the managers ignored them
I just hope the bugs and screwups keep coming. It’s really not fun at all anymore. I’ve been wanting to leave this game for a while. This last month may help me actually do it. Poor design, poor decisions with compensation for their errors, bugs that cannot or will not be fixed, uninspiring defense-only champs,… the list goes on and on… Keep it up Kabam. I appreciate it.
As seen in this thread alone, players will sometimes have very different experiences with the same fight. For example, my Battlegroup had zero issues with her and mowed right through with revives to spare - yet another Battlegroup in my same Alliance has been struggling hard.
Regardless of my own experience, I already brought the situation to the team and voiced the negative experience of the fight many have faced.
I’m not in charge of the tuning of the fight, so I can’t sit here and tell you what will happen in the future, especially at 2am on a Monday... but we want you to have fun playing our game - that’s a top priority for us.
At a bare minimum she needs to be unawakened in the future. Adding another 10% to that shield whenever you miss is too much. It takes away time from dealing damage because you're either adding to the shield or you're wasting time waiting to be able to hit into her block to trigger the timer or just waiting for her to go back to normal so you can hit again.
Hey folks, the Invisible Woman fight is working properly. I brought this to the team for deeper investigation earlier today.
Her shield is normally based off of 10% of her health, but this version in RAIDS is actually tuned down to 2%.
Since you need to remove her shield before noticing any meaningful damage, it’s going to seem like you may not be doing anything to her. Once you build charges with your teammates, the shield goes down a LOT faster - and you’ll see the giant numbers that you’re used to.
That being said, these fights are open to tuning & balancing, so it certainly might be changed based off of feedback - but as of now, the fight is not “bugged” and the shield is reduced.
There is no way anyone in Kabam actually tested this fight. There's just 0% chance for it. We've seen some of you play this game and this fight would take atleast those guys 100 revives to go through. Why are there champs tagged for raids who are completely and utterly useless against 1/3 mini's?? Wigra is totally countered by IW so why would anyone use her in Raids if she's unusable in 33% of the fights in the path? What is the logic??
Looking at my current raid map, here is the problem... Final Hood - 134m health Final Prowler - 173m health Final IW - 171m health
To hit cap with Hood, we need to deal 16m damage. To hit cap with Prowler, we need to deal 20.5m damage. To hit cap with IW, we need to hit 20.5m, plus 3m for every time through the shield. Most commonly, summoners need to go through the shield twice, so that's an extra 6m in an average fight. I've got through it 3 times on multiple fights, so that's an extra 9m damage.
So to deal cap against IW, players need to deal 50-80% more damage than they do against Hood and 15-45% more damage than they do against Prowler. In a timed mode, that is a significant increase in damage required to make the most of a fight.
She may be tuned down and working according to design, but that 2% shield is requiring as much as almost 50% more damage.
188 hits with lady deathstrike at full charges and very little damage done. Didn’t even get her shield down. Working as intended for you to have to spend to beat and shrinks the pool of usable champs to just a few. Terrible idea.
Oh and maybe Crucible (but that reusing old contents, so any issue would of been fixed while back), and Necropolis (but I think there was a bug with Grandmaster when it was first released, correct me if I wrong), oh and...no..nope, so just BG Off Season.
If I find anymore I will let you know, but don't hold your breath 🤣🤣🤣.
Hey folks, the Invisible Woman fight is working properly. I brought this to the team for deeper investigation earlier today.
Her shield is normally based off of 10% of her health, but this version in RAIDS is actually tuned down to 2%.
Since you need to remove her shield before noticing any meaningful damage, it’s going to seem like you may not be doing anything to her. Once you build charges with your teammates, the shield goes down a LOT faster - and you’ll see the giant numbers that you’re used to.
That being said, these fights are open to tuning & balancing, so it certainly might be changed based off of feedback - but as of now, the fight is not “bugged” and the shield is reduced.
So what are they going to do for people who didn't luckily pick 1 of the 3 champs that actually work like normal?? Nothing?? So me and my 2 path mates even if we used all 14 revives for the week will not be able to even get through the Invisible Woman fight seeing as how even with 15 charges we r getting 1% total damage. 2% if we r lucky. So do nothing and say it's tuned properly when it obviously is not at all, and what we don't get to finish our Raid map because of obvious lack of play testing on your end??? Sounds like a normal Kabam plan to me.
I did 4 fights timed out on each one takes over half the allotted time to take down her shield and ive barely hit a million points surely this isn’t working as intended
6* R5 ascended Omega Sentinel with 15 role charges... Hardly could get off 5% for 3 minutes. There is probably something I do incorrectly, but removing the shield is a crazy thing and requires a lot of time!
So basically what I've gathered from this thread is everything is working as intended and you really only have a few options you can use to do sufficient damage. So why do you make so many bad options available to use? Is it so you can torture us to figure out what champs work well and drain us of resources? You should be better!
Looking at my current raid map, here is the problem... Final Hood - 134m health Final Prowler - 173m health Final IW - 171m health
To hit cap with Hood, we need to deal 16m damage. To hit cap with Prowler, we need to deal 20.5m damage. To hit cap with IW, we need to hit 20.5m, plus 3m for every time through the shield. Most commonly, summoners need to go through the shield twice, so that's an extra 6m in an average fight. I've got through it 3 times on multiple fights, so that's an extra 9m damage.
So to deal cap against IW, players need to deal 50-80% more damage than they do against Hood and 15-45% more damage than they do against Prowler. In a timed mode, that is a significant increase in damage required to make the most of a fight.
She may be tuned down and working according to design, but that 2% shield is requiring as much as almost 50% more damage.
Hear hear! Exactly..... And then leads to the small minority of the pool that can achieve such OP damage caps, especially after they've scrapped the ones most people had figured as the most reliable.
So basically what I've gathered from this thread is everything is working as intended and you really only have a few options you can use to do sufficient damage. So why do you make so many bad options available to use? Is it so you can torture us to figure out what champs work well and drain us of resources? You should be better!
They could've weeded out the bad champions from the pool you know if they actually tested any of them smh
instead they remove the good ones tested by the community for them.
I worked out the issue. She gains 10% of her shield when you miss an attack, so basically you can't knock her down unless you have a vigilance buff. I had only 30 seconds left after her shield was down, and when I threw an SP2 She gained her shield back instantly.
Working as intended? I really hope that is not the Kabam position, because that would mean they willfully created a hard stop. I dread to think how it will go for those that have her as a boss on nodes that require a knockdown...
Comments
For example, my Battlegroup had zero issues with her and mowed right through with revives to spare - yet another Battlegroup in my same Alliance has been struggling hard.
Regardless of my own experience, I already brought the situation to the team and voiced the negative experience of the fight many have faced.
I’m not in charge of the tuning of the fight, so I can’t sit here and tell you what will happen in the future, especially at 2am on a Monday... but we want you to have fun playing our game - that’s a top priority for us.
It is might not be bug, but it is extremely poorly design.
With the fiscal from the last Raid (which actually did not properly resolved), we now have this.
It would be good if Kabam development team actually test their content before release (at least the bug stuffs like AW, Raid and Eng game content), instead of using the players asguinea pig.
It is good that some players doesn't have problen with this fights, but it is also clear that many other are really struggled with this fight, because it is unbalanced.
We all want to enjoy the game too, but as players not beta tester. It is getting hard yo enjoy the game when thing like this keep happening. I don't we have had a Raid run without bug yet.
Played as best as I can, completed all tasks as fasted as I can, maintain my Degen and Buff, didn't get a single hit, did the full available time and only got 2% off.
Not sure how Kabam think this is alright content to release.
Wigra is totally countered by IW so why would anyone use her in Raids if she's unusable in 33% of the fights in the path? What is the logic??
Final Hood - 134m health
Final Prowler - 173m health
Final IW - 171m health
To hit cap with Hood, we need to deal 16m damage.
To hit cap with Prowler, we need to deal 20.5m damage.
To hit cap with IW, we need to hit 20.5m, plus 3m for every time through the shield. Most commonly, summoners need to go through the shield twice, so that's an extra 6m in an average fight. I've got through it 3 times on multiple fights, so that's an extra 9m damage.
So to deal cap against IW, players need to deal 50-80% more damage than they do against Hood and 15-45% more damage than they do against Prowler.
In a timed mode, that is a significant increase in damage required to make the most of a fight.
She may be tuned down and working according to design, but that 2% shield is requiring as much as almost 50% more damage.
188 hits with lady deathstrike at full charges and very little damage done. Didn’t even get her shield down. Working as intended for you to have to spend to beat and shrinks the pool of usable champs to just a few. Terrible idea.
BG Off Season, as stated in my post
https://forums.playcontestofchampions.com/en/discussion/377659/bg-off-season#latest
Oh and maybe Crucible (but that reusing old contents, so any issue would of been fixed while back), and Necropolis (but I think there was a bug with Grandmaster when it was first released, correct me if I wrong), oh and...no..nope, so just BG Off Season.
If I find anymore I will let you know, but don't hold your breath 🤣🤣🤣.
Is this a bug or a feature Kabam? "yes"
instead they remove the good ones tested by the community for them.
Working as intended? I really hope that is not the Kabam position, because that would mean they willfully created a hard stop. I dread to think how it will go for those that have her as a boss on nodes that require a knockdown...
Just look at that cooldown. It's basically impossible to do any meaningful damage...