MrConway

There is not much I can say yet, the season has just started. Luckily our new system allows us to quickly change restrictions for the season so we can react to what we see. Maybe next week would be better to talk CVC. We agree, so instead of making big promises we will be working on results. We realize that with the current climate this wouldn't help, so we're not doing it.

Oh my... I don't think you understood the message that I was reacting and answering to, and I think you'll find I have great respect for many of our players and certainly the community at large. I think its fair to call a live stream a show. What is your issue with this statement? Yes, we do of course follow all applicable local rules and regulations where we operate. Requests like that need to be made in writing I believe, Twitch chat is certainly not the place for it. We will of course talk about the situation this evening, but please understand that you will not be getting my personal opinion when asking me questions in my professional capacity. I suggest people just come and chat to us this evening, then we can take it from there.

It will be us, but remember: While there may be many angry people that will come join the stream to disrupt it, there are plenty of people who will come for the fun, banter and information. The show must go on and we're certainly not going to hide away from you :)

Ich bedanke mich fuer die vielen Vorschlaege :) Am Ende haben wir uns fuer Johannes Meck-Leyne entschieden!

All contributors got to choose one of the four weeks to participate in, so you should see them in one of the coming weeks :) The idea of this is to encourage people to discover some of the other excellent streamers in our community.

This is not a remembrance of Gallipoli specifically, but an event dedicated to Anzac day, which is the most significant commemoration of military casualties and veterans in Australia and New Zealand. Gallipoli is mentioned in the article specifically because it is the origin of this commemoration. We intend no offense and I apologize if any has been caused. We'll take this feedback on board for articles like this in the future.

We conducted in in-depth analysis about whether the lack of radar one one side will present an issue and don't think it will, but that is also why we test :) We see tier 8 as a good starting point and if this event is successful there is nothing stopping us from exploring other tiers!

Captains, As you know there is currently a 100% discount on Captain retraining, skill resetting and upgrade dismounting to enable you to experiment and adapt to the new skills and changes to the meta, that the CV rework brought. We have heard a lot of feedback from you that this period of free resets is not sufficient considering the scope of changes and potential upcoming balance tweaks. We agree and I am happy to announce that we will be providing another 1-week period of free reset approximately in 2 months, around the release of 0.8.2.

I just wanted to jump in and clarify a few misconceptions and assumptions that are being passed around here regarding Flamu's removal from the CC program. I think if you have followed Flamu over the years, you should know that we have never sanctioned him for his opinion. The reason the Tweet in question was highlighted (as part of the issue), is that despite the many contacts he has to us, he never bothered to ask for confirmation before posting an incorrect assumption intended to rile up the community. The contributor program is a partnership between content creators and us and only works if both sides are interested in making it work. We do not have the wish or the capability to silence Flamu, he is free to keep making World of Warships content just like any other streamer. We did however choose not to promote and support him anymore. KoTS XII will not have CVs, information that is easily available on the KoTS discord and has been ever since the announcement about the handover was made.

You have mail ;)

Das werden wir hoechstwahrscheinlich nicht aendern, da musst du dir schon Skills aussuchen. Wenn du sowieso nur Ccoop spielst, dann nimm doch einfach die empfohlenen Skills, dann dauert das auch nicht lange :)

Thats a terrible idea IMO, your team is already at a disadvantage with a player missing, why would you want them to waste time and shells on shooting a ship on their your own team?

I can confirm that your math is indeed correct, this is how the calculations work out. This does not however confirm whether there are innate balance issues with the skill, that is something that we are currently still investigating. We will be following up with a detailed dev-blog post on the skill rework and some of the specific skills and their impact once we have finished collecting and analyzing data. It is important to remember that we need to actually have the skills used for a while before we can draw conclusions either way.

Any ships that are not tech-tree ships should remain on your account. If you want to make sure about a certain ship, just ask CS prior to confirming the wipe.

First of all thanks for doing the right thing and reporting him to support. A temporary ban is certainly not the only tool in our arsenal and I have sent this particular report for a review to see if it needs to be escalated. If you come across cases where it appears that the unfair play is a constant thing or where there was clear intent behind it (announced in chat), please do feel free to escalate it to myself or one of the other staff members, preferably via PM. We will definitely check and see what can be done in each individual case as we don't want everyone's enjoyment to be ruined by a few bad apples. Thanks!

You're a brave man mentioning me in a math-heavy post I'll clarify with the dev-team and get back to you.

Standard detectability is poor wording on our part, what it refers to is the concealment listed in port, including the modifiers from modules and captain skills, but without additional modifiers that you may be receiving in game from captains or buffs. As an example, my Yamato has 14.1km detectability when I go into battle and as long as there are no spotted enemies within 14.1 km, deadeye is active.

There'll be detailed information on the next season towards the end of next week, I'll have to ask you for a bit more patience!

Not true, the skill is only active if there are visible (spotted) ships in your detectability range. Displaying it would just make it easier to see and mean you don't have to check the minimap. :)

It is certainly a possibility that we'll do something like that, but I cannot make any promises.

Let me summon our resident expert @Tanatoy

I feel your pain, but if there are no actual game rules that he has been breaking, there is nothing much we can do. I would advise ignoring him until he goes away. Should he have broken any rules, please feel free to PM me.

I'm not saying it isn't on the cards, but we need to make sure we know how she is performing before we can make decisions about changes.

Definitely not during 0.10.0 and also unlikely for 0.10.1 to be honest, but the functionality of the skills will stay the same so I don't think that should be a deal breaker for the skills. For most of them looking at the minimap will tell you if they are active and for Dazzle you just need to be good at counting :P

We've received this feedback a lot and are looking into it. I cannot promise that we will implement it, but chances are quite good!