Mark VI doesn't die, gets 150 stacks
Leviathan’s special “Sabotage the Hangars” relevantly reads:
“Capital Ship Sabotaged: The next allied ship called to Reinforce is immediately destroyed upon deployment”
Mark VI Interceptor’s reinforcement bonus relevantly reads:
“If the Capital Ship is Sith Empire:
- Mark VI Interceptor gains 30 stacks of devouring Swarm instead for every other ally reinforced ship.”
When the enemy Mark VI Interceptor was reinforced as first reinforcement after I had destroyed the hangers, it was not immediately destroyed, and instead did not gain stacks of devouring swarm. My ship, however, was destroyed.
Also, when I did a later reinforcement bringing in my Mark VI Interceptor, after I had seized the enemy bridge, it came in with 150 stacks of devouring swarm. More than enough to take out all the other ships with one hit on each. The only other ally reinforcement called, was the one destroyed. A basic hit on the enemy Mark VI interceptor does not kill it, but instead removes 30 stacks of devouring swarm.
Mark VI Interceptor is immune to instant destroy effects from either Sabotage the Hangars or another Mark VI basic with 40+ stacks of devouring swarm, probably from “Mark VI starts with 10 stacks of Devouring Swarm, and can’t be defeated or destroyed while it has Devouring Swarm.” At least it doesn’t get the bonus devouring swarm if hangars are destroyed, preventing it from one shotting my fleet.
Out of curiosity, anyone know where the 150 stacks I got came from? A cursory read of Lev and Mark VI didn’t show me. Doesn’t really change anything in the battle as mirrors are still a first turn coin toss to determine the winner, which has to be the laziest and most ridiculous way of determining a battle I’ve ever seen.
https://www.youtube.com/watch?v=yqlUqetmtvc
“Capital Ship Sabotaged: The next allied ship called to Reinforce is immediately destroyed upon deployment”
Mark VI Interceptor’s reinforcement bonus relevantly reads:
“If the Capital Ship is Sith Empire:
- Mark VI Interceptor gains 30 stacks of devouring Swarm instead for every other ally reinforced ship.”
When the enemy Mark VI Interceptor was reinforced as first reinforcement after I had destroyed the hangers, it was not immediately destroyed, and instead did not gain stacks of devouring swarm. My ship, however, was destroyed.
Also, when I did a later reinforcement bringing in my Mark VI Interceptor, after I had seized the enemy bridge, it came in with 150 stacks of devouring swarm. More than enough to take out all the other ships with one hit on each. The only other ally reinforcement called, was the one destroyed. A basic hit on the enemy Mark VI interceptor does not kill it, but instead removes 30 stacks of devouring swarm.
Mark VI Interceptor is immune to instant destroy effects from either Sabotage the Hangars or another Mark VI basic with 40+ stacks of devouring swarm, probably from “Mark VI starts with 10 stacks of Devouring Swarm, and can’t be defeated or destroyed while it has Devouring Swarm.” At least it doesn’t get the bonus devouring swarm if hangars are destroyed, preventing it from one shotting my fleet.
Out of curiosity, anyone know where the 150 stacks I got came from? A cursory read of Lev and Mark VI didn’t show me. Doesn’t really change anything in the battle as mirrors are still a first turn coin toss to determine the winner, which has to be the laziest and most ridiculous way of determining a battle I’ve ever seen.
https://www.youtube.com/watch?v=yqlUqetmtvc 0
- 60.8K General Discussion
- 9 Developer Q&A Archive
- 2.6K New Players
- 30.5K Arena and Character Strategy
- 4K Individual Events
- 4.6K Guild Events
- 4.6K PVP and Rivalry
- 50.1K Guild Recruitment
- 731 Art and Media
- 4.1K Off Topic
Howdy, Stranger!
Replies
It being immune to Destroy effects is WAI though. Honestly not sure if the first reinforcement being alive or not matters though.
https://forums.galaxy-of-heroes.starwars.ea.com/home/leaving?allowTrusted=1&target=https://answers.ea.com/t5/Bug-Reports/GAC-Breaking-New-Levi-Bugs-Since-Update/m-p/12799430#M67140
@CG_Tusken_Meathead @CG_SBCrumb
I’ve been around too long to believe CG ever pays attention to us.
If you bothered to open that thread you will see a member of the QA team replied to that ticket
Bug reports in Answers HQ are part of what they work off of to generate the Trello board here: https://trello.com/b/vgQhKHMf/swgoh-developer-tracker
You've nothing to lose but a few minutes of your time to submit the bug - and there may already be a bug report filed for this one, but it doesn't hurt to check.
I don’t care enough about the game to do their job for them. Like I said - it’s still a ridiculous first turn coin-toss
And if they bothered to do their job right in the first place, it would never be needed. Seems no-one could be bothered, only difference is, they’re paid to.
Start with Sith Fighter, Fury & B-28.
If users don't report bugs, they generally don't get fixed. That's not unique to this game - that's any software, ever, everywhere. You recorded the battle, uploaded it to youtube, then came here and wrote up a big long post about it - if you'd have just put that information into AnswersHQ instead, the bug would be reported (though again, I'm pretty sure it's already been reported). I guess you just wanted to vent? If so, that's fair, but just know that you're yelling into the wind when you could have actually done something about it.
BTW, the mirror with that defensive lineup is not a coin toss - it's an easy and pretty consistent win, even when you don't go first. You don't want dagger starting on offense in a mirror. At least that's been my experience so far and I've had very little trouble with mirrors after I figured out the strategy.
You don't care enough to report a bug to help get it fixed, but you care enough to make a thread which won't help get it fixed?
As for 150 stacks, I don't know, no comment.
Regardless of well they do their job doesn't matter as far as attention seeking goes though
I do agree it would've been better for CG to release stuff without bugs in them, and I know CG wants that too but stuff happens
Don’t forget: We are their beta testers since they abandoned the prior beta program. This means two things:
1. Be cautions spending resources on any new release, and don’t expect it to work as intended.
2. Devs will be paying attention to bug reports, as this is now a fundamental part of their (our) QA role.