Interesting observation - experienced Internet disconnect by ISP but was unable to join the battle when connection was restored - anyone had similar experience?

[Leo_Apollo11]

Hi all,

 

Interesting observation - experienced Internet disconnect by ISP but was unable to join the battle when connection was restored - anyone had similar experience?

 

I had 5+ minutes of ISP Internet disconnection just after I started the "Battle". When my ISP got back on OnLine after 5-10 minutes I was able to get back in WoWs but there was "Ship in Battle" info instead of me being in battle.

Anyone had similar experience?

 

 

Leo "Apollo11"

 

 

P.S.

And, of course, I got "Unsporting Conduct"...

 

[Isoruku_Yamamoto]

I had something alike yesterday.

My client wasnt updated yet, and decided to crash and go do so (update) while i was in battle. 

[biker_618]

I was able to rejoin only if game client was active on my pc during reconnection. After restarting game, nope.

 

Experience is from few years ago when my most used "mod" for game was traceroute but take that with pinch of salt as connection was still alive but i was dropped from WoW server ...

[Leo_Apollo11]

Hi all,

 

Interesting... thanks for feedback guys!

 

WG - is this "normal" behavior?

 

@MrConway

@YabbaCoe

@TheWarJaC

@Seraphice

 

 

Leo "Apollo11"

 

 

[Estaca_de_Bares]

It hasn't happened to me yet, but from the info you provided and my experience suffering ISP disconnections in the past (which always allowed me to rejoin battle, although sometimes I got stuck in the battle info/ship roster screen) that seems like a matter of connection and session handling.

 

IIRC, whenever an ISP disconnect happened to me, none of those times did I close the WGC and the maintenance time wasn't that long, so if what @biker_618 describes is true on his side, and combined with the >5min of wait by @Leo_Apollo11, my guess is that the server considered the original session as ended (be it by the closing and reloading of the game/WGC or the long idle client server-wise), so when accessing the game again it was done as a new one, assigned a different session ID and defaulted to going to port.

 

Salute.