Niibler

OVH is a solid choice: https://www.ovh.co.uk/

I like my DDs. After seeing this new skill system and knowing steam sales were on I grabbed my ships money and invested on something else. Haven't played World of Battleships since then. I'm not saying I'm not going to play anymore, I will (eventually). TL;DR: New system is just sad to look at by the majority of sub-par classes like CV's, DDs and even CAs.

I'm also looking forward the stepping up to World of Battleships becoming a browser point and click game. We still need to remove those complicated mechanics like moving and using WASD and maybe nerf everything a littlee more except Battleships. Now for real, this easy login could be improved, my suggestion is: Only allow Battleships to be played without a login, that way new players won't be tempted to try the other sub-par classes and will prevent frustration in the future in case they decide do create an account.

And even with all this you still have fun playing the game and will continue playing? WG must be doing something right.

I'm guessing some clan touched the OP in the wrong place. Bad boys!! Now for real, I think the division 3 player limit should be increased, I wanna play with more friends at the same time and you know...random is random...no one cares anyway

Also lovely that Fire prevention only allows a maximum of 3 fires running by eliminating one of the fire places on the superstructure. So, DE nerf, FP buff, welcome to land of BaByships

To turn replays recording ON (if the first way didn't work): 1. Open for editing the preferences.xml file. 2. Scroll it till the last lines: </scriptsPreferences> </root> 3. Paste two new lines before </scriptsPreferences> line <isReplayEnabled> true </isReplayEnabled> 4. This is how you should see the result: <isReplayEnabled> true </isReplayEnabled> </scriptsPreferences></root> 5. Save file & launch the game client. 6. Enjoy the game! 7. All of the replays will be stored at the ..\replays folder which will be automatically created inside the game folder. 8. To launch the replay, close the game client first 9. After closing the game, use drag'n'drop *.wowreplay file to WorldOfWarships.exe or associate file extention with the game executable. 10. Every battle generates separate replay file. Port cannot be recorded. 11. You can play the *.wowsreplay file with the same client version only. Replays might not work properly with newer version of the game client. 12. Replay controls: 'Insert' & 'Delete' for playing speed control 'End' for pause (which is actually x100 slower speed) 'Home' for normal speed 'LMB' for toggling camera direction between free & recorded '>' & '<' for fast-forward & rewind (can be used together with 'Ctrl') From: https://na.wargaming.net/support/kb/articles/517

God bless Steam Winter sales!

Still, what is the fixation with the USRR ships...

There is also a mission in campaign, do X amount of damage to USRR ships.

Leaked picture of one of the new ships:

I wouldn't be so sure they are bots, probably just "people playing for fun"

Make game modes optional. People that like X will be able to keep playing X. People that don't like X can opt-out of playing X.

Besides the chat ban after multiple reports the karma system is just a placeholder. Does nothing besides e-peen/placebo effects.

1. DescriptionThe smoke consumable does not work when the timer reaches zero, it has a weird delay that varies from 1 to several seconds and requires several keystrokes to activate. This bug is so old that you can find dinosaurs around it. 2. Reproduction steps Wait for the timer on the smoke consumable to end. At zero seconds: - Press whatever key you have to activate it. (btw what about unifying the consumables keys??) - Smoke won't deploy. - Press the key again and again and again until it finally works. 3. Result Smoke does not pop immediately when timer reaches zero, it requires several keystrokes to finally work. 4. Expected result When you have the timer at zero and you press the key to use the consumable, it is expected the consumable is used. 5. Technical detailsN/A 6. Note This bug has been reported several times in the past already.

Some surveillance stations can't be hit, requires too much teamwork to be even fun to play (most people play for fun and don't care about teamplay, teammates or objectives), please make it optional for PVP.

Screenshot, disable messages, blacklist, get the replay from the folder, report to CS, forget about it.

Missing the point like a boss. At least try to read what other people are saying.

Team focus...yeah...that happens often... The most common focus I see is in making lemming trains, feeding, staying at 18+ Km or afk for the initial 3 minutes of the game. Sneak what? Surveillance stations, some are not even possible to hit from one of the sides. Take out the dust on your DDs and try it yourself.

Report it as a bug here: http://forum.worldofwarships.eu/index.php?/topic/67663-bugs/

Instead of removing WG could make them optional, checkbox for all the game modes and one can pick which ones to queue for.

I would vote Yes! to remove Bastion, Standard and even Epicenter (at the current state).

Ok, I tweaked my bug report a bit in order to keep it ELI5. For all the rest, if you wanna report the bug here is the thread for it: http://forum.worldofwarships.eu/index.php?/topic/67663-bugs/

1. DescriptionThe smoke consumable does not work when the timer reaches zero, it has a weird delay that varies from 1 to several seconds and several keystrokes to activate. This bug is so old that you can find dinosaurs around it. 2. Reproduction steps Wait for the timer on the smoke consumable to end. At zero seconds: - Press whatever key you have to activate it. (btw what about unifying the consumables keys??) - Smoke won't deploy. - Press the key again and again and again until it finally works. 3. Result Smoke does not pop immediately when timer reaches zero, it requires several keystrokes to finally work. 4. Expected result When you have the timer at zero and you press the key to use the consumable, it is expected the consumable is used. 5. Technical detailsN/A 6. Note This bug has been reported several times in the past already.