NobleRipper

For some reason it won't let me access the code redeem page right now, just reverting to the /shop URL but not displaying anything apart from the header and footer. Anyone else having the same problem, out of interest? The game has been kicking me out so often this latest patch, I'm hardly surprised that the bonus code page has started doing the same thing...

Yep! I suppose we're all home-schooled at the moment ;)

Indeed. Every day a school day, eh?

Thanks!

That seems to be exactly what it is. Just tried to load in to an Ops match five times, finally got in after a low-memory warning and my comp stroking out for a couple of minutes. It's only happened with WoWs, and only since last patch, but now the game is crashing in more matches than not; at this point I'm tempted just to give up and wait until next patch (although I might give subs and balans cruisers a miss as well come to think of it...)

Thanks, missed that!

What does this one do, out of interest?

Shouldn't the article have been flagged again in the game client? That seems to be the case usually when news articles are updated, seems odd to have an exception for this one.

Nice work!

Yep. Also worth a mention: WG need to invest some of that random-bundle money in a coder that knows how to do pathfinding, it would seem.

Do TOTHESALTMINES or TEAANDMEDALS not still work?

For me it's none of the above; I'm considering quitting at least for the time being because the last update was so unstable I can rarely now have a game where the client doesn't crash right at the start or partway through and force me to re-load WoWs entirely (preferably before the match is over to avoid turning pink). I was getting lukewarm enough to playing before that happened that at this point it's not even really worth the hassle of going through the whole bug report process.

I just had two crashes in one game, which was the first one I tried today; ever since the patch hit it's been happening at least once in more games than not. Fortunately have always managed to get back in before the end of the game, or at least I haven't had any 'quit early' pink penalties yet. The game client's stability seems to be so fragile since last uodate that it can't tolerate other things open in the background, or any alt-tabbing from the game to other things (which I was happily doing up until now to cover the two-minute deadzone between starting a game and actually getting into a position to start fighting the enemy). It seems possible I could solve the problem by exiting everything else, but to be honest by this stage I'm preferring to do those other things instead; I suspect that the only real fix will be to wait for a new patch one (or more) down the line where the problem is fixed. It's a shame given that there's the Golden Week stuff on, but it already takes a while to load into the client and then a game, if I then have to re-do that in the middle of every match then even 200% XP isn't worth it.

With you there. More Ops at different tiers would be great; maybe the female captains could be rewards for 5*? Personally I'd love to see more of an emphasis on WWI-era ships and combat; not just from the lack of characters, but because of the large numbers of different warships that were built the world over up to 1914 of which we only have a relative handful represented at the moment. By which I mean, I want RN monitors!

Sounds both fun and engaging. I just wish there was some way to buy that kind of luck from WG...

Actually, pretty sure sailors are known to use similar language to the chat in most Random battles...

I had the crashes (one each in both games I played today), but no Chrome. Seemed like it might have been to do with having Discord open, but to be honest I didn't fancy the prospect of getting crashed out of another game so I decided to call it a day with WoWs and stay on Discord.

No idea if it's being caused by a disconnect per se, but the game has terminated itself twice on me now (one for each battle I've played today, I think I'll give up for a while); second battle was entirely bots apart from me and I can't imagine I'm the only one wanting to play T6 co-op at the moment, so presumably there are connection issues elsewhere too.

I say again, WG: players UP, plz buff!

Working, and I say this with a considerable amount of deliberation, as intended...

Can't argue with Fiji, for a good long while she was my only T7. Nelson is lots of fun and very useful (although can always use a speed flag), given that if you keep front-towards-enemy at all times the turrets never have to swing very far and the guns are nice and punchy; Duke of York is much more disappointing though (not recommended). ...But then, I don't have many T7 ships, so can't really comment much past that (ARP Myoko is ok, then that's me out). As usual, I personally wouldn't advise destroyers; although Skåne has quick-firing torps (which would potentially be really useful for the mêlée at the end), I can only imagine they're the same fart-in-a-hurricane weakness as her predecessors and I hear she's not even that fast. At least she doesn't have smoke either For my own personal edification, could I ask people's opinions of New Orleans, Algerie and Hood for the job?

You're mistaken, Narai was fixed; the problem was that people were getting too much FXP In seriousness, I should probably say that it's nice to hear that the backwards bug is affecting the enemy ships for a change.

Ah, thanks; must have missed that one. Let's see how it goes!

'Lucky' you. And I wonder how much of that was waiting for the two sides to spot each other before the first shots were fired? @MrConway Any further word on the situation yet, out of interest?

It's behind you! https://forum.worldofwarships.eu/topic/133635-conquer-the-stars-in-master-of-orion/?page=3&tab=comments#comment-3434892