MrConway

I'll bring it up for discussion!

Unfortunately not...

There will most likely have to be other changes to make sure everything stays balanced, but that should go without saying :)

Do I really need to explain to you what kind of functions we mean here!? We make the final determination on what is and isn't allowed based on these rules, please trust us to apply some common sense to it.

Please send a bug report in to customer support along with a WGCheck report so we can dig into what caused this.

I doubt we will change to division window back completely, but I do hope that we can dedicate some more time to it soon to make it less obtrusive. Unfortunately our UI team is currently very busy so we have to prioritize on the different items we want to improve and fix. So sorry, no ETA right now.

This discount really is aimed at the clan battles players, so if you did not play I am afraid you are simply not eligible. Discounts should be working for everyone, we had to manually enable them following the update so there was a little delay.

Erm... No offense but I would suggest asking over on the WoT forums ;) Or try summoning @vuque Sorry, this was a limited time offer as announced on the portal.

Interesting, thanks for that!

We will monitor the number of achievements given out and then have a look at whether the requirements need to be tweaked. Its a bit too early since the update to be able to say much I'm afraid.

Captains, As many of you have in the past asked how exactly the team killing system works, here is a run-down of the system for you! A player receives the team killer (Discipline) status under the following circumstances: Has done 10,000 or more damage to allies in the most recent 1,000,000 main battery damage (1% of the damage to allies) Has done 10,000 or more damage to allies in the most recent 1,000,000 aerial bomb damage (1% of the damage to allies) Has done 10,000 or more damage to allies in the most recent 1,000,000 aerial torpedo damage (1% of the damage to allies) Has done 40,000 or more damage to allies in the most recent 1,000,000 torpedo damage, was done to the allies (4% of the damage to allies) Killing an ally with main battery, torpedoes, or aircraft Has shot down 30 allied aircraft or more in the 100 most recent air victories (AA defense doesn’t count, aerial combat only) As a result, a players nickname becomes pink! When under this team killer (Discipline) status, a player receives the full damage that he inflicts on any ally as mirror damage, by percentage. For example, if a team killer does 10,000 damage to an ally, which is 50% of that ally's health, the team killer also loses 50% of his health. Allies take only 10% of the damage that a team killer is trying to do to them (5% for torpedoes). Allies take full damage from flood and fire damage caused by team killers, this will be reduced in future. Mirror damage is multiplied if the team killer continues to try and cause damage to allies, scaling up to 150%, 200% etc. To “clear his name”, a team killer must play 6 clean battles - not causing any team damage. If during those 6 battles the teamiller does hit an ally, the number of battles required to be cleared grows proportionally to the potential damage done to the allies, or kills. If a team killer relapses and re-offends, he will need (6 + 2*n) battles to remove the team killer status, where n is the number of relapses.

This information is no longer accurate as the punishments system has been superceded by our new anti-abuse system. You can find all relevant details on our portal: https://worldofwarships.eu/en/news/updates/anti-abuse-system/

I will report this again, but please be aware that we cannot always dedicate the resources to fix every possible bug, we have to prioritize which ones to work on. Please be aware that the player achievements might be a little delayed, if you have not received on by next week please send me a PM.

As others have pointed out, this matchmaking update has only changed the balance between the two teams, ensuring that ships are mirrored by class and tier. This is something we are looking into and might introduce in future updates, provided that we can see a statistical need for it and can implement it without increasing queue times.

Kapitäne, Nach dem Update 0.7.2 haben wir von euch aus der Community viele Meldungen über eine erhöhte Anzahl an Zitadellentreffern bei einigen Schiffen bekommen. Schiffe, die eine gut geschützte Zitadelle hatten, die auch noch unter der Wasserlinie lag, bekamen nach dem Update viel mehr Zitadellentreffer, gerade die Conqueror und die Hindenburg waren davon stark betroffen. Wir hatten mit dem Update allerdings keine Änderungen hieran geplant und konnten ursprünglich auch keine ungewöhnlichen Änderungen feststellen. Wir konnten aber letztendlich anhand eures Feedbacks, sowie der vielen Tests und Videos, die Ursache finden. Es bestand ein Fehler, der in vielen Fällen zu vermehrten Zitadellentreffern unter der Wasserlinie führte. Allgemein hatte dieser Fehler keine grossen Auswirkungen, aber in Spielen wo Schiffe ihre Breitseite zeigten und von AP geschossen getroffen wurden, merkte man es deutlich. Der Fehler entstand durch eine kleine Verbesserung, die wir in 0.7.2 eingeführt hatten, die sich aber in unseren Tests nicht zeigte. Wir haben diesen Fehler heute Morgen mit dem Serverneustart behoben und wollen uns für die Unannehmlichkeiten entschuldigen, sowie euch für den vielen Feedback danken! Dazu möchten wir noch anmerken, dass wir auch viele positive Kommentare zu dem Fehler gesehen haben, da das Spiel dynamischer wurde und schlechtes spielen bei einigen Schiffen stärker bestraft wurde. Wir arbeiten weiterhin an dem Schadensmodell und wollen einige Änderungen einführen, jedoch gezielt und mit Absicht! Sobald wir weiteres wissen, werden wir euch natürlich informieren! Danke! Euer Warships Team

Dear captains, Please share all bugs encountered version 0.7.3 here with the template we provided below. Before submitting your report please check if the bug is listed in our known issues already, in which case no report is necessary. 1. Description Clear and substantial description containing all necessary details. Example: the cruiser Aoba: scout is inoperable. 2. Reproduction steps A sequence of the player's actions which triggered the bug. Example: 1. Select the cruiser Aoba 2. Enter the battle (Training or Random Battle). 3. Try to launch the scout. 3. Result In-game experience resulting from the bug. Example: When you press the scout activation button, you can hear the sound, but nothing actually happens. The aircraft stands still on the catapult. 4. Expected result In-game experience which should have occurred if no bug is present. Example: The scout has to be launched by the catapult. 5. Technical details Example: Bug time: about 19:30 (UTC).Replay (attempt at 01:00), python.log, DxDiag. If you encounter this error, please zip your ~\crashes\ folder, upload it to any online file storage and add the link to your report.

Captains, Please leave any feedback on our new space mode and the associated skins in this thread.

Those are all tricky requests, the first three for balance concerns and selling Arkansas and Iwaki would surely annoy many of our longest and most loyal players. But I'll pass it on for consideration.

Yes, please PM me the replay. I have reported this bug before and will follow up on the status!

That's a great idea, not sure if it is possible to implement easily though. I'll suggest it!

Two options: Find a new clan, or recruit more players :) You might find a clan you can join for the season and then head back to your old clan afterwards.

Aaaand this is the point where my answers will send me straight to Gulag ;) No comment for now

It exists and contributors got to play a very early prototype of it, that's as much information as I can give you at this time. We will reveal more when and if we're happy with the way it is going :)

We do not intend to give any more options when it comes to choosing what kind of map and game type you end up in when queuing for a random battle - this would likely have a severely negative impact on the matchmaker and waiting times for battles. If you are not willing to play whatever map and mode we throw at you in a random battle, please do not queue up and ruin everyone else's enjoyment. Be warned that this behaviour will lead to you being automatically banned from all random battles following the update next week - and good riddance.

Getting the bots working as intended is definitely a first step towards being able to have more challenging operations and maybe a "hard mode". Personally I have always found the bots a bit lackluster in the previous operations, but we will have to look at whether we went too far the other way with this operation. I have brought the issue up internally, we will have a look at the overall statistics of the mode to figure out if we need to make any changes. I will try to get some of those to share with you, but no promises. Thanks for the quality feedback @everyone!