WG Staff
  • Content count

  • Joined

  • Last visited

  • Battles


About Kandly

  • Rank
    Community Coordinator
  • Birthday
  • Portal profile Kandly

Profile Information

  • Gender
    Not Telling
  • Portal profile Kandly


  • Position
  • Portal profile Kandly

Recent Profile Visitors

1,700 profile views
  1. Great post OP - thank you for your well written topic and your team-focused approach! I agree with many of the things you've said, especially since you consider all the variables that go into "doing your job" in a battle and you wish to start a conversation around this. It's true that tactical decisions should involve more than one aspect - so I applaud your attitude and the fact that you analyze your choices after the battle is finished. We always discover possible areas of improvement when doing so! :)
  2. Too late @Miessa3, I've already forwarded this suggestion! It is now our #1 priority to get this into the game! ^ I'm kidding, of course. As for the detonation mechanic, this has been widely discussed on the forum since the beginning and the feedback on it has always been divided. We currently have no plans to remove it from the game altogether, but if there's any plan to tweak it, we'll definitely let you know. ;)
  3. Hi there! TBH I personally like the insane flashy camos (some of them ironically, I have to admit), but I'll happily forward this suggestion. :) Seeing that we already included several player-requested filters in-game, I don't see why this wouldn't be possible in the future.

    Hi guys! The latest Multipack for can be found here.
  5. Hi guys, Please post your feedback regarding the tech tree visuals in Update 0.6.13 below. Cheers, Kandly
  6. Hi guys, Please post all feedback regarding the loading screen tips of Update 0.6.13 below. Cheers, Kandly
  7. Hi guys, Please post all feedback regarding the balance changes in Update 0.6.13 below. Cheers, Kandly
  8. 0.6.13

    Hi guys! Please post all Update 0.6.13 bug reports in this topic using the following template: 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. Cheers, Kandly
  9. Hi guys, Please post your general feedback regarding Update 0.6.13 below. For other types of feedback, please consult the following list: Update 0.6.13 - Bugs Update 0.6.13 - Balance Changes Update 0.6.13 - Loading Screen Tips Update 0.6.13 - Tech Tree visuals Cheers, Kandly
  10. Hello Captains! As you probably know already, Update 0.6.13 is coming tomorrow. Therefore, some players may experience a few technical problems during that time. Please check the list of known issues here. Cheers, Kandly
  11. Captains, We revealed two awesome ships yesterday - but wait: today, we have two more! Lyon The last French superdreadnought project to be drafted before World War 1, the Lyon was supposed to sport a large battery of 340 mm guns. Her construction was stopped during the war. Richelieu What worked for Dunkerque will work on a bigger scale, right? Right! Richelieu with the original French design of two quad turrets forward will surely strike fear into her enemies on the seven seas. Action Stations!
  12. Captains, Something new is cooking in the development kitchen - let's have a look! Exhibit A What? Another Italian! Yes, another Italian ship is here! Sporting the flashy air recognition stripes, she is ready to sail! Exhibit B We already have King George V in-game - now let¨s add her famous sister. They share the fame of engaging German battleships in battle! Action Stations!
  13. Honestly, I get it, but let's stop insulting people. Not performing well in X battle in X game doesn't make anyone stupid, it just means they didn't perform well that time. Even good players can suck sometimes. Trust me, I've seen it. No, it's not only you, of course sometimes it's the team. We all have moments when we ask ourselves "why in the name of all that's holy do we have 3 perfectly capable ships calmly cruise towards the edge of the map, too far to hit the enemy team" / "why is that CV circling his planes around an island, tens of kilometers away from any ship while this amazing enemy CV already killed 2 dudes of ours" / "why are they not listening to me when I'm telling them what do to in chat and why, WHY do BBs love to gather together in useless lumps and beach themselves in front of the entire enemy team, oh god WHY" ... But then I realize that this sometimes happens to every single player out there. We all get annoyed and we're under the impression it's only our teams that mess up, or feel like the game is unbalanced in this regard, no matter our skill level. I have yet to discover a competitive game in which I don't feel this way once in a while, so yes, I understand what you're saying, but I gotta say that this is purely subjective and relates to your perception of the game, not the reality of it. Basically, we're all in the same boat of zero chill - all of us, reds and greens alike. We see the mistakes our own team makes more clearly than the enemy's, because unfortunately, our attention is limited. Some of you said that we could do something about this by tweaking the matchmaking or creating elite groups for those who perform well or something. Hmm, the only thing I have to say about that is that I have collected the exact same feedback I read here, but about Ranked instead of Random. "How come this happens at Rank 3? That person should know better." Mistakes are everywhere and we cannot control this. All we can do is educate. We need to talk about this sort of frustration openly instead of always trying to find a perfectly rational reason for any victory or defeat, because in the end it's just... well, random. You, as a player, can only do your best and make sure your part is covered, but you cannot win an entire match on your own. Losing the match isn't on you either, it's on the entire team. There are way too many variables here to try and control this, so the most we can do is our job. You did your job OP - but didn't win. It happens. Removing this part of the game would simply make it not a game anymore, but a nice simulator where all you do is the right things, only to get good things in return. Gaming is kind of like gambling (including the good/bad streaks). When it's good, it's amazing and feels like an angel hugged you on pink fluffy candy clouds - and when it's bad, it's infuriating. This holds true for all the games I've played - and I played a whole bunch of them. P.S. It's good to be back, sorry for my absence, guys! I was away for an event.
  14. Hi guys! Please leave your general feedback regarding Update 0.6.12 in this topic. For other types of feedback, please consult the following topics: Update 0.6.12 Feedback - BugsUpdate 0.6.12 Feedback - Halloween Event - Chapter 1 Reloaded Update 0.6.12 Feedback - Halloween Event - Chapter 2 Update 0.6.12 Feedback - Smoke mechanic change - Overall Update 0.6.12 Feedback - Smoke mechanic change - Specific ships Update 0.6.12 Feedback - Clan Battles - General Update 0.6.12 Feedback - Clan Battles - Matchmaking Update 0.6.12 Feedback - Clan Battles - Ship Rental Update 0.6.12 Feedback - Clan Battles - Tactics Update 0.6.12 Feedback - Other changes Cheers, Kandly
  15. Hi guys! Please leave your feedback regarding our other changes in Update 0.6.12 in this topic. Cheers, Kandly