So Used See & Bane in GAC. Bane has Unique Omi. After he died, SEE was able to be ability blocked. The language in the Omi description is a bit confusing, but most seem to agree the way it reads is that all of the ability persists after his defeat (not just gac portion). I'll submit a bug report. Anyone else experience?

Yeah doesn't make sense. Either the entire unique should be persisting, or it's a completely useless (and misleading) sentence.

If it is Working As Intended, then the line in his Omicron about the effects persisting should be removed. Other characters with self-buffing Unique abilities don’t lose their own boosts when they are defeated and revived (for example, all of Asajj’s ramping). That’s how Uniques work. There’s no point in calling out that it persists when the Omicron only affects Bane anyway (and also both Bane and SEE lead block allied revives).And I think it should persist. It won’t affect the Bane+1 comps much, because Bane is usually the survivor, and it helps Bane actually be a direct upgrade to Wat as a SEE lifter, because Wat’s techs are persisting buffs.

I think what they're saying is that the the stat boosts for the remaining ally on death get applied even the killed unit is Bane.But that still does not make sense, because A)Fives doesn't have that language and his boosts to others persist after death, and B)That text you quoted about the other ally is in a pre-omicron block as part of a list with all the other effects. So they either need to get rid of that line, mass rewrite the whole thing, or actually fix it.

Basically,Either its not working WAI or its WAI but text description needs to be updated to reflect it and the current text does a poor job of describing how its suppose to work

It is bugged or support has no idea what they are talking aboutNone of this matters if Bane is defeated When Bane or other ally is defeated: The remaining ally gains 5% Critical Damage, Offense and Potency plus an additional 15% of these stats per the defeated character's Relic Amplifier level until the end of battleWhile in Grand Arenas: At the start of battle if there is only one other non-Summon ally present and they are Sith:- Bane gains 75% Mastery, Max Health, and Max Protection- Whenever an enemy is defeated, Bane gains 10% Max Health, Max Protection, and Offense (stacking) until the end of battle- At the start of battle, Bane takes a bonus turnSo the statement: These effects persist if Bane is defeatedDoesn't matter for that entire portion of his abilitySo that only leaves they gain an additional 2% Ultimate Charge, and the following effects occur for Bane and other Sith ally:- Immune to Ability Block, Cooldown Increase, Healing Immunity, Stun, and Turn Meter reduction- Gain 75% Max Health- Gain 75% Max Protection until the first time they are defeated- Ignore Taunt effects- At the start of their turn, recover 35% Protection and dispel all debuffs on themselves

Darth Bane Unique Omicron Not Working Fully in GAC

SnuggeSnuggles
Rising Novice
10 months ago
So Bane as a lead with another random Sith can beat Leia but CG will nerf the mechanic that lets Bane replace Wat as a SEE lifter? Which clearly was the intended and communicated behavior from CG. Bane will still be a great character but it’s just strange to do a character rollout in this way.
perfidius44
Rising Newcomer
10 months ago
"HumbleMumble;c-2460982" wrote:
So Bane as a lead with another random Sith can beat Leia but CG will nerf the mechanic that lets Bane replace Wat as a SEE lifter? Which clearly was the intended and communicated behavior from CG. Bane will still be a great character but it’s just strange to do a character rollout in this way.

According to the post, the thing they’re removing from the skill description was never in the game.
So it’s not a nerf, it’s a clarification on how the skill actually works.
Gawejn1000
10 months ago
"Starslayer;c-2460985" wrote:
"HumbleMumble;c-2460982" wrote:
So Bane as a lead with another random Sith can beat Leia but CG will nerf the mechanic that lets Bane replace Wat as a SEE lifter? Which clearly was the intended and communicated behavior from CG. Bane will still be a great character but it’s just strange to do a character rollout in this way.

According to the post, the thing they’re removing from the skill description was never in the game.
So it’s not a nerf, it’s a clarification on how the skill actually works.

Bane was advertised as a replacement for wat. Techs from Wat persist thru his defeat. Bane doesnt work that way. Players assumed based on information received from cg that bane would give kind of similar functions as wat. But it is just half cooked dish. Yes, Bane is great, but it seems Wat would still be with See. But the idea was to remove Wat from using with See. At least Bane was presented this way.
Gawejn1000
10 months ago
"mariogsh;c-2460954" wrote:
"Gawejn;c-2460953" wrote:
"MasterSeedy;c-2460952" wrote:
I really hoped that see plus bane would be good against jmk in gac.

SEE/Bane is insanely good against almost anything.

However, Sith Lords are JMK's speciality. You would also be upset if SEE/Bane had no counter. JMK is the only squad that I know kills him. Yes, I want the descriptions to be accurate, but so long as they correct the wording, the way things function with Bane & SEE is fine.

See can beat jmk. But not with bane. And bane suposse to be his lifter. That was the idea i think to introduce bane. Not to use bane with r9 sith assasin to solo other teams and see would go still with wat.
Bane was presented as replacement for wat.
See could beat almost everything before bane. With wat.

SEE can DEFINITELY beat JMK with Bane
I've done it on arena, as long as CAT does not instant kill Bane, which on GAC is not going to happen because of the bonus turn and CD increase

The only thing is that the omicron was supposed to counter that little issue on GAC, but now is not happening lol
Still, I'm counting on that it is very much possible to still do so
I've not encountered a JMK this first round, so no way to test it, and even so, I don't have the omicron on the special for the 2 turn CD, so quite hard for that as well, but will see

SEE could beat jmk in gac if cat would use her insta kill on SEE. Otherwise Bane is too slow to keep jmk on cooldown reduction despite omicron.
Maybe if see would be enough fast charge his ult to kill cat before she kills bane ....
Whatelse73
Seasoned Veteran
10 months ago
"Gawejn;c-2460989" wrote:
"mariogsh;c-2460954" wrote:
"Gawejn;c-2460953" wrote:
"MasterSeedy;c-2460952" wrote:
I really hoped that see plus bane would be good against jmk in gac.

SEE/Bane is insanely good against almost anything.

However, Sith Lords are JMK's speciality. You would also be upset if SEE/Bane had no counter. JMK is the only squad that I know kills him. Yes, I want the descriptions to be accurate, but so long as they correct the wording, the way things function with Bane & SEE is fine.

See can beat jmk. But not with bane. And bane suposse to be his lifter. That was the idea i think to introduce bane. Not to use bane with r9 sith assasin to solo other teams and see would go still with wat.
Bane was presented as replacement for wat.
See could beat almost everything before bane. With wat.

SEE can DEFINITELY beat JMK with Bane
I've done it on arena, as long as CAT does not instant kill Bane, which on GAC is not going to happen because of the bonus turn and CD increase

The only thing is that the omicron was supposed to counter that little issue on GAC, but now is not happening lol
Still, I'm counting on that it is very much possible to still do so
I've not encountered a JMK this first round, so no way to test it, and even so, I don't have the omicron on the special for the 2 turn CD, so quite hard for that as well, but will see

SEE could beat jmk in gac if cat would use her insta kill on SEE. Otherwise Bane is too slow to keep jmk on cooldown reduction despite omicron.
Maybe if see would be enough fast charge his ult to kill cat before she kills bane ....

And maybe if CG tested their releases BEFORE they released them, they'd see these kinds of issues before players found them for CG?

If JMK gets to ult, SEE is going down either way because the whole team ignores protection and will mass attack him to nothingness. But I don't care that Bane can't beat JMK, it's the other counters he's supposed to deal with I'm concerned about not working anymore based on what CG told us about how his kit was released as compared to what it appears they're doing. (And the other bugs that seem to be present with the character.)

Again, CG leadership needs to put more resources into testing things before we get them.
SnuggeSnuggles
Rising Novice
10 months ago
"Starslayer;c-2460985" wrote:
"HumbleMumble;c-2460982" wrote:
So Bane as a lead with another random Sith can beat Leia but CG will nerf the mechanic that lets Bane replace Wat as a SEE lifter? Which clearly was the intended and communicated behavior from CG. Bane will still be a great character but it’s just strange to do a character rollout in this way.

According to the post, the thing they’re removing from the skill description was never in the game.
So it’s not a nerf, it’s a clarification on how the skill actually works.

Ah I see, so instead of fixing the bug they change the description. That’s one way of solving the problem.
Persimius
Seasoned Scout
10 months ago
"Durumana;c-2460940" wrote:
Removing the "These effects persist if Bane is defeated." line warrants a refund of the omicron. It is false advertising. I should not be expected to read code on swgoh.gg to assess whether an ability is worth investing an omicron in.

Yeah, that line is why I applied it. I did testing in arena and it beat the teams I wanted it to beat just fine without it. Would not have bothered wasting the super scarce materials for no tangible benefit.
crzydroid
Retired Hero
10 months ago
"Starslayer;c-2460985" wrote:
"HumbleMumble;c-2460982" wrote:
So Bane as a lead with another random Sith can beat Leia but CG will nerf the mechanic that lets Bane replace Wat as a SEE lifter? Which clearly was the intended and communicated behavior from CG. Bane will still be a great character but it’s just strange to do a character rollout in this way.

According to the post, the thing they’re removing from the skill description was never in the game.
So it’s not a nerf, it’s a clarification on how the skill actually works.
Crispy508
Seasoned Adventurer
10 months ago
"StarSon;c-2461015" wrote:
"Durumana;c-2460940" wrote:
Removing the "These effects persist if Bane is defeated." line warrants a refund of the omicron. It is false advertising. I should not be expected to read code on swgoh.gg to assess whether an ability is worth investing an omicron in.

Yeah, that line is why I applied it. I did testing in arena and it beat the teams I wanted it to beat just fine without it. Would not have bothered wasting the super scarce materials for no tangible benefit.

Agreed. I hate to be a "conspiracy theory" type person, but its almost too obvious of what they did here.. There's simply no logical reason to include that last sentence in the kit, if all of the effects were not intended to persist after Bane's death. Its just simple reading comprehension that a 5th grader would understand. I think this is one of the cases where the simplest and most obvious answer is correct (even though it sounds crazy). Either CG: (i) intentionally structured the description that way to trick players into using omicrons (which I don't think is the case); or (ii) more likely, it was intended to persist, but they have so many bugs and issues currently, they don't want to fix it or (or can't) and don't want to admit it to the players. It just easier to say "Whoops, how'd that sentence get in there" than make his kit perform as intended. This is backed up by how CG was touting Bane prior to his release, as a superior replacement for Wat with SEE. Again, Bane is still amazing and I love him, but CG's explanation for all of this is baffling. They should definitely refund the omicron
TargetEadu
10 months ago
Another explanation is that the Omicron benefits were supposed to extend to the other Sith and persist, but that functionality was removed before release.