Test Server Feedback

( I just finished running several tests on sisi with a kronos, was in the second room of mordus headhunters level 4 mission and aggroed the entire room to get large incoming DPS, had a Centus x type large armor repairer running and repairing 3770 HP every 11.3 seconds. my tank was cap stable and my resists were all at 82% and above.

incoming DPS reduced my armor to about 88 percent each cycle, thankfully the repairer repairs 25% of armor each cycle so no problem perma tanking the whole room, I then simulated a DC by closing the client. waited 3 minutes and when I came back my ship was still sitting in room but now only had about 30% armor as once bastion dropped my tank was much weaker and the ship made no attempt to warp, I decided to test it again to see if maybe it would warp if given more time. ( there were no scamblers only webbers so that was not an issue)

did the same test and then logged in after 5 minutes, I was in my pod.

As it currently stands even with a strong cap stable tank with deadspace modules, the fact that the ship does not warp out at all means death in heavy DPS missions when DC happens. So bastion is an auto suicide for mission runners.)

I trained a lot of time, for marauders, about 1/3 of the way to level 5. If this is not changed before Rubicon hits TQ than expect mission runners to all sell their marauders or to just never use bastion mode.

Can I please get a Dev response to this as this is very concerning

I have been very much looking forward to using the bastion on TQ but after this testing I realize it's an epic fail ( who is gonna push a big "I want to die now" button) there must be some way this can be fixed

that is correct, that is why you always kill scramblers first thing

there is never 100% safety but at the same time there should not be a 100% death rate either, that is the point of my post, as it currently stands, going into bastion means absolute death unless you can immediately log back in