principat121

Mod updated to client version 0.11.2 no change of content Mind the new path to the res_mods subfolder: World_Warships_EU\bin\5315992\res_mods

I needed 140 games to unlock both Moskva/Petro (starting tier5). A bit less as I played some mid tier ships still after having the tier10. I needed 51 games to unlock Schliefen (starting tier4). Yes, I am far from being average and for normal players it will take a bit longer. But the point is, in the current economy it is no problem at all to have a tier10 ship after just 200 games played in total.

Indeed. And I believe you. Most of the time I see players with just a couple of hundreds games played. Highest ship tier reached was tier 5, 6 or 7. Of course such players enjoy playing at least one time the "top dog" with the big boys. But does that mean, that this is good? No. Changes to Petro? Please, do not make a fool of yourself. All the changes didn't bother to cope with the real problem. And Zao? Just took Wargaming five years to do so... again not something to brag about...

No, still too cheap. Make it 500k per game would be better!

Being the best player in a battle DOES NOT mean that you played well!

unpopular opinion: git gut to earn more credits!

@YabbaCoe "The reward for completing each section of the collection is the ability to mount 2 flags on Italian destroyers, cruisers, and aircraft carriers, respectively." What about the battleships?

You just have to log in every day, nothing more. You do not have to do anything ingame. Just 2min max. It is possible.

A ship with those stats can never start any interests San Diego is a exact copy and nerfed version of the already existing Austin. San Diego and Austin are ships that are only balanced around a situational gimmick. They have no purpose when the gimmick is on cooldown.

V Maestrale Action time of the Emergency Engine power consumable reduced: 20 to 15 s. At this rate of nerfing, you can give up that gimmick at all you try to balance these ships around. What do you really think will a 15sec Engine Boost do? And even if you consider that you need a couple of seconds to reach the new top speed. You will end with a net value of maybe 10sec of Engine Boost. Ten Seconds!!! *slow clap* Great show! Such excitement! Much fun!

Yes, indeed it is. Why should you? No one forces you to play high tier ships. And it is on purpose that high tier matches are expensive. You can be glad that WoWs still is way too lenient with credit income for bad play in high tier matches. In WoT you would lose alot of credits for such a bad game. And yes, it was a bad game. The particular circumstances are irrelevant (but such games of course can and will happen to everyone of us). If you want to play more high tier games without losing too much credits you either become better on average with your battle results (35k average damage in 10 games with the FdG is bad, thus the low income) or you play low or mid tier ships in between to farm credits. This is the way.

"Die" Jean aus Jean Bart war ein Mann...

A carrier main complaining about unfair matchmaker! Wow! What time to be alive!

You don't! You suffer... ...silently.

Your whole chain of arguments in this thread about how unfair/strong a Schliefen is, became really funny, considering your most played ship is a Småland... You complain about a combination that makes normal DD capping caps nigh imposible, but on the other hand you have no problems with playing a ship that makes normal DD capping caps nigh impossible. How is that brain knot even possible?

And? 1) Hydro isn't running forever. 2) You outspot the BB. 3) You have torpedos, and as you never get tired to mentioned that BB Schliefen is a potato, he will eventually catch your torpedos. 4) Get 100 points and cap afterwards. A game is rarely won by the team who caps first, but rather the team that caps in the right moments.

Irrelevant. Especially in ranked, you cannot expect a DD to stay away from the caps just because a Schlieffen was spotted near it. Yet this is exactly what's happening in ranked games, the DD has to consider just abandoning a cap, because if that potato Schlieffen pushes in, you're going down. Just the mere threat of a potato yolo push should have a DD think twice about contesting a cap, which is way too much power for a BB. Your answer lies here:

Yeah, because a Schliefen comes out of nowhere, and was never seen before closing in to the cap. Everyone knows a Schliefen is deadly in CQC, but also everyone knows beyond 13km the Schliefen is cannonfodder for focus fire. Don't blame a ship, played to its strength, when the culprit is your very own team and lack of team coordination. 5,5km better read the patch notes next time

Was carefully reading the announcement or the patchnote not an option?

Who said that you would get the Preussen for free? Hint: No one ever said such a thing.

This never happened.

Mod updated to client version 0.11.1 no change of content Mind the new path to the res_mods subfolder: World_Warships_EU\bin\5191542\res_mods

Lustiger Beitrag. Weil es außer 'Kritik' keine Weitsicht über diese Mechanik gibt. Und warum genau ist das kein Matchmaker? Er macht genau das was er soll: Er stellt zwei zufällige (!) Teams zusammen. Fertig. Und das macht er. Also ist es auch als MM zu bezeichnen. Doch, denn es werden echte Gefechte erstellt. Radar gibt es auf Schlachtschiffen (Borodino, Missouri) auf Kreuzern (unzählige) und auch auf Zerstörern (Orkan, Black, Småland). Wie soll das gerade gebogen werden, wenn der Matchmaker nur Spieler benutzen kann, die sich aktuell in der Warteschlange befinden. Ich nutze mXStat für eine persönliche Aufbereitung meiner Spiele-Sessions. Da kann man sich u. a. die WR der Spieler und die Team-WR anzeigen lassen. Erstaunlicherweise liegen die Team-WR selten um große Werte auseinander. Meist ist die Differenz deutlich kleiner als 2%. Man kann also durchaus davon sprechen, dass eine Großzahl an Gefechten im Parameter Team-WR ausgeglichen sind. Wenn du denkst, dass die Teams grob unausgewogen sind, dann steht es dir frei Daten zu präsentieren, die das belegen. Warum nicht? Welcher Parameter soll der MM hier jetzt noch zusätzlich aufnehmen? Wenn du jetzt auf die overmatch-Mechanik hinauswillst, ist das wieder einmal zu kurz gedacht, denn dann könnte ein einzelner Spieler in einer Yamato/Mushashi niemals in ein Gefecht gesteckt werden, bis nicht ein weiterer Spieler eine Yamato/Musashi spielen möchte. Es ergibt objektiv betrachtet keinen Sinn solch ein Hinternis in den MM einbauen zu wollen. Was machen dann die ganzen Belfast und Indianapolis Spieler? Wie gesagt, dein Beitrag zeigt, dass du dich zwar gut über den MM aufregen kannst, aber gleichzeitig ermangelt es dir an der Weitsicht zu erkennen, dass eine Vielzahl deiner Punkt vollkommen unrealistisch sind und nur zu einer Verschlechterung des Spieleerlebnis führen wird. Und zu deinem Spoiler sag ich mal nichts... Wer meint sich einen Aluhut aufsetzen zu müssen, nur weil er nicht versteht wie Zufallsmechanismen funktionieren, dem ist nicht mehr zu helfen. Edit: Die Sockenpuppe @namron1 verteilt wieder Daumen-runter, wenn er argumentativ nichts bringen kann. Verlässlich wie immer...

1. Frage: Wie kann man überhaupt in einem DD an dem Sinn von mehr HP zweifeln? 2. Frage: Was ist Blenden? Ist das der 4 Punkte Skill, der die Genauigkeit des Beschusses reduziert? (Dazzle im englischen Client.) Mehr HP sind immer ein direkter Buff der Überlebensfähigkeit eines DDs. Und wenn mit Blenden der Skill Dazzle gemeint ist, dann kann man sagen, dass das ein ziemlich spezifischer Skill ist, der in jeglichen Builds eher eine untergeordnete Rolle spielt, da der Nutzen ziemlich eingeschränkt ist, dafür, dass dieser 4 Punkte kosten soll. Da gibt es deutlich bessere Alternativen.

That is fine as the "5045210" is the current version of the game client. And the "5191542" is the preloaded version valid from thursday on. I am not sure why the OP has a number between. But my guess is that he didn't updated the game with very first patch of 2022 as soon as it was published, but rather updated his client when the game already had a minor update since (and there were a few). The number represents the major update numbers (build numbers) and do not change when there is a minor small patch or hot fix in between. This is what I observed. The rest is a educated guess.