Crysantos

Kapitanowie, Ponieważ sposób zgłaszania błędów był trochę chaotyczny to trochę to ujednolicimy. Oto wzór, którego fajnie by było się trzymać zgłaszając błędy: 1. Opis problemu ze wszystkimi możliwymi szczegółami. 2. Sekwencja ruchów, które doprowadziły do tego błędu. Przykład: 1. Wybrałem taki okręt. 2. Wszedłem do bitwy 3. Kliknąłem na coś 4. Komputer zaczął tańczyć salsę. 3. Rezultat - co w efekcie sie stało. 4. Spodziewany rezultat - czyli co normalnie powinno się stać. 5. Szczegóły techniczne - Błąd wystąpił o tej i o tej godzinie. Link do powtórki lub filmiku z wyróżnioną minutą tego co się stało. Python.log i raport DxDiag. Jeśli napotkałeś taki błąd jak ten poniżej:

Hey guys! I'll check whether there are any plans for com. flags to be added for ships that don't have them yet - usually they were part of the Admiral's package for ship sales. Greetings, Crysantos

Hallo Dunkeltier, Danke für den Hinweis. Hierbei scheint es sich um einen Fehler in der deutschen Version zu handeln (in der englischen Version ist es korrekt, in dem Übersichtsfenster des Arsenals ist es auch in der dt. Version korrekt, wenn man mit der Maus darüberfährt). Natürlich handelt es sich hierbei nicht um einen bösen Versuch dir Geld abzunehmen, sondern hier hat sich der Fehlerteufel eingeschlichen. Wir können gerne über eine PN klären, wie wir dir hierbei helfen können, wenn du die Modifikation wieder zurückgeben möchtest. lg, Crysantos

Bonjour à tous, Merci par avance pour les futurs rapports d'erreurs que vous pourriez nous faire concernant la mise à jour 0.7.9 Voici une liste de questions pour améliorer vos rapports : 1. Bug constaté sur le support suivant : mise à jour 0.7.9 2. Bug constaté : En bataille ou dans le port Bataille : Durant une partie / Ecran de chargement des batailles Port : Précisez l'interface en question 3. Type de bug : Graphique Apparence du navire X Carte, problème aux coordonnées XX ... Autres : décrire le problème Typo - Précisez ou vous avez vu la typo et la phrase entière, pas seulement la typo en question Obus : Problème en jeu/dans le port, précisez le problème Capitaine : Problème en jeu/dans le port, précisez le problème Compétences : Problème en jeu/dans le port, précisez le problème Technique : Lag / Crash / Freeze 4. Repetition du bug : Une fois / De temps en temps (aléatoire) / A chaque fois Précisez si c'est sur toutes les batailles / cartes/ navires ou certains. 5. Importance du bug : #3 - Impossibilité totale de jouer #2 - Bug qui impacte les conditions de jeu #1 - Bug qui n'impacte pas les conditions de jeu 6. Ajouter une image & une vidéo du bug en question Attention, ne reportez que les bugs que vous avez constaté vous même et pas ceux dont vous avez entendu parler.

Kapitanowie, Tutaj prowadzimy dyskusję na temat Halloween

Bonjour à tous, Merci par avance pour vos retours concernant le public test 0.7.10. Si vous souhaitez discuter d'un sujet en particulier, n'hésitez pas à utiliser les sujets suivants: Rapports d'erreurs Halloween Sprint des batailles classées Merci!

Hey mate, We've checked in our systems and you got your Supercontainer right on the 14th September, in which you drew 25 Dragon flags You might have missed this since you would simply find this SC within your other boxes without the SC animation in golden letters. I hope I was able to help you here, have a nice week! Greetings, Crysantos

Dear captains, Please leave your feedback on Ranked Season 10 and the new ruleset in this thread!

Captains, Please share all bugs encountered in the public test of version 0.7.8 below, 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.

Captains, Please leave any general feedback on the public test of 0.7.8 here. Should it concern one of the topics mentioned below, please head to the dedicated thread: Bugs Anniversary event Ranked Season Changes to French cruisers As always you can find a detailed list of the changes that we are testing on our portal: https://worldofwarships.eu/en/news/game-updates/update-078-wows-birthday/ Greetings, Crysantos

Dear captains, Please leave your feedback on the World of Warships Anniversary event and the attached Arsenal additions in this thread!

It's all regular battle modes (PvP, Ranked, Coop, PvE), we'll add it :) Greetings, Crysantos

Auf Wunsch des Threaderstellers geschlossen. lg, Crysantos

As far as I know you can't obtain Sovereigns after 0.7.9, so they should be exchanged with the release of 0.7.11 - that should give you plenty of time to exchange them . Done, thanks for spotting it! Greetings, Crysantos

You can obtain said Sovereigns from update 0.7.9 on and also use them immediately. At the end of the arc they'll be automatically exchanged for credits, like at the end of any other event. We're fixing this confusing mention of Update 0.7.10, sorry about that. Greetings, Crysantos

Oha, definitely naming & shaming! Also good game before that - always a pleasure to meet you in battle

It should be finished in the next few months, but I can't promise that we can deliver this in 2018. I understand that you're frustrated about the amount of time this takes and that you would like to get it asap. Right now all I can offer is the last status update, that it'll still take a while - as you can imagine there are topics like the CV rework that require a huge amount of time and work right now. I can't and don't want to make any promises we can't keep but I'll let you know as soon as I have a rough date for delivery of the collector's club. Greetings, Crysantos

We're working on it but for now I can't share any exact date yet - that's always the problem with being transparent about upcoming things in advance, they might get delayed. But we are working on it and as soon as we have more information on this, we'll let you know. Greetings, Crysantos

Hey guys, Both games are unrelated development-wise - sorry to crush your dreams on this Monday morning. Greetings, Crysantos

Dear captains, With update 0.7.8 we've introduced a new consumable for French cruisers - the main reload booster. Please let us know your feedback and experience with it - also with the related balancing changes to the reload of affected cruisers.

Hallo miteinander, Langsam nimmt dieses Thema Dimensionen an, wo wir vielleicht doch etwas härter durchgreifen müssen. Wenn ein Spieler hier ins Forum geht, um eine Frage zu stellen, sollte er unabhängig von seinem Clantag hier einfach Hilfe bekommen. Unsere Forenregeln zu dem Thema sind sehr klar, wir erwarten einen konstruktiven und respektvollen Umgang miteinander. Ich schließe dieses Thema und erwarte von allen Beteiligten ihr Verhalten hier zu überdenken und anzupassen. lg, Crysantos

Keep it constructive and we'll be fine :)

Some people say a picture or gif says more than a thousands words, but I usually prefer a bit more details & text about why you think this way and what you'd like to see changed :) Greetings, Crysantos

I know you don't like me - but please stick to the facts. I only got involved after the ban was applied and the case was brought to my attention - I talked to our CS and the player, I forwarded the reasoning / reason for the ban and made sure there's proof for that. In general our Community team usually doesn't apply bans, this is done by our CS. When I realized that this isn't in line with what has been stated before from others I raised this topic internally and then I'm doing my best that such miscommunication won't happen again in the future and that all departments are aware of this. Greetings, Crysantos

Our CS agents who will decide this based on the proof provided. In general it's hard to draw clear lines here and cover all possible angles. Of course we'll revert the ban for the mentioned case. The aspect of communication is what is very important to me and the entire WoWs team. We changed a lot of things over the past year and there are still some issues - like we encountered with this topic. Once we spot an issue like this, we try to tackle it internally and then act on it. I hope it's visible that we're trying to streamline things and improve visibility where possible, not everything is perfect but we're trying our best to make it better. Greetings, Crysantos