So, one of my Characters has a Romulan Escort (Ha'feh Warbird). While it punches like a Asteroid, it has about the durabiltiy of wet tiolet paper*.
So when it was time for Jack in teh Box challenge of core assault, I did this:
Fly in under Battle Cloak.
Move to the exit side border of the Box.
And just wait.
Attacking requires flying under full trothle = likely to fly out of the box.
Killign enemies only resets their cooldown as a new one spawns.
And just staying alive inside the box brings progress. (I am not quite sure about surviving cloaked, however). And my team was able to do that better without me drawing aggro.
Now, Jack in the Box was the final challenge of this run. And my team was so far behind, the other team killed Regulator before we got out.
End result:
The Mission ended with a enemy Victory, without my team even making it past the 3rd Challenge.
I got no mark selection.
I was hit with a 2 hour "AFK Penalty".
That sounds like eitehr a bug being misinterpreted as AFK penalty (2 hour). Or me playing smart beign consdiered being AFK. Either one sounds like it could use a fix.
*I know the proper saying is "wet tissue paper". But tissue paper is designed to actually still have acceptable durability while wet. Toilet paper is designed to disolve when wet. So it fits a lot better.
0
Comments
Not for killing foes.
Not for flying out of the box.
Not for being dead.
Could you be mixing up "Jack ind the Box" and "Swarm"?
Or was progress for killing foes actually tested (at wich point it might be a bug)?
The description says:
Stay in the box for Progress.
More allies in box = quicker progress.
Enemies will spawn to get you out of the box. Considering that there is no kind of enemy taht could reliably and defedably push you out, tehre is only one way to "get you out of the box" I can think off - blowing you up.
Have you actually tested that not killing the enemies somehow makes that mission stop?
From the days of purely textbased inputs we have the concept of a "Magic String". A input that has effect, but was not hinted at in any place. I was hoping they were smart enough to avoid repeating such a mistake.
Okay, that information is good to know. And something they really need to fix in the player side communiction.