Issues, Workarounds & Localization

My client more so this past 10 days or so has been quite unstable, I've done the repair, changed the port number, turned down every possible graphic setting and even raised it with the ISP. They advised changing out the micro-filter, so I removed it and installed a new faceplate with a built-in splitter/filter. My ISP have been quite helpful and keen to resolve my issue, but my guessing is its probably a service provider issue than an eve issue.

I am a telecoms engineer by trade and understand about error-bit-rate, and it is my understanding that my ISP has basically tried to push my copper twisted pair feed to its absolute max and thus probably created a packet loss higher than your threshold.

Your GM's have been marvellous in re-imbursing my pimped golem, I didn't expect it, I rather hoped ( kinda embarrassing to lose any ship in a level 4, let alone a golem ).

It appears that my ISP is going to data-line test to try to find a better pair from the exchange but I highly doubt they'll find one on the same cable as when one pair starts to degrade, you know the rest are likely to follow suit.

An issue that I am concerned with however is this:

When my client dropped, I still had dialtone and knowing my router could well be out of sync with the exchange, I reset my modem and prayed to the almighty that I'd be able to log back in mid-mission to my bastion-moded golem. The in use bastion module MUST of locked me in system as I wasn't being warp scrambled and with the slow log-in process along with the router reset, I came back in game to see myself in my pod.

Its the 2nd time its happened, the first I managed to reset/relog with 20% structure left ( in bastion mode ), a few cycles of the XL booster and I was ok to finish up, dock and repair. 2nd time not so lucky. The bastion module I only tend to put on for one cycle if I need to run my booster and then I disengage it, but if you're mid-cycle and lose the client, you're screwed.
The only thing I can think of is to not use the bastion module during this period of instability, but was wondering if the devs were working on some kind of workaround to disengage it due to client loss? I know about the past problems with people doing the old logoffski in pvp, but maybe you could cut mission runners a little slack? We've taken quite a battering on isk per hr/salvage nerf etc this past few years.

Obviously, the auto-warp to safety usually kicks in after a few mins after client drop, but not if you're in bastion mode. Totally unfunny.

same here, disconnect after dc aft...... what to do?