Aotearas

Youtube Recommendation fix-up part deux:

What do you think those jiggly mounds in the video were? But I can fix up that recommendation list again with some good stuff if you want:

First game ever in my freshly acquired Grozovoi: Almost a Kraken too if it weren't for that meddling @charleswelsh getting the killing shots on all three thereafter targets ... (got my Kraken later in a Molotov game though so at least I got the signal flags). First impression: precisely as I expect her to play like, that is like an Udaloi that can actually sneak up on something. I've also decided to kit her out for AA build (AFT, both AA range and +25% dps upgrades and will ultimately also spec into BFT; naturally I run DFAA instead of Engine Boost, with the DFAA upgrade ), but sadly there was no CV to really mess with. Neat ship. Guns are amazing (duh), it's actually stealthy (6km surface concealment), torps are at least usable (still 8km ones for now) now that it has sufficient stealthtorp capabilities and with Survivability Expert plenty HP to use up in DD duels. Bit on the chubby side though ...

Well, I suppose I could've spared that Bayern (sunk dealing a grand total of 33 damage ) for someone else, but I kinda wanted that Kraken really, really bad ...

Still saving money. Plan is still to get a GTX 1080, buy it from EVGA once I know reliably the new Nvidia generation will come up within three months and then use the EVGA Step-Up program to get myself the next-gen equivalent at minimal extra cost. Depending on how long it takes Nvidia to finalize the new generation, I might've even saved up enough to go for a 1080 Ti (or alternatively go for entire new rig). Oh, and talking about CPUs:

Forum was slow and I had pretty massive server lag in two games (appeared to have effected all players considering what people said in all chat). After those two games however it went back to the usual. Maybe on of the hamsters had to take a nap.

Met @pra3y. He asked me to lick windows someplace else, so I restrained myself and only killed half the enemy team whilst he was busy turning the skies bloodred with his Saipan.

Can we paint it pink and call the rescue fund Operation Pettycoat?

Get rid of that superstructure and we can start talking rubels.

You didn't seem to understand what I wrote. I'm not eschewing teamplay. I'm just not going out of my way to butter up randoms unless it is absolutely necessary to win the match. And that's the ultimate line in the sand for me. I play to win because that's what I enjoy, I like winning (as long as it isn't a boring curbstomp game that's over in four minutes ...). If that means I have to throw myself against half the enemy team whilst the remaining majority of mine is happily lemmingtraining around at a snails pace, then I'll throw myself at the enemy team and play speedbump for as long as I possibly can to have a chance at winning. If that isn't necessary, then I'll make sure that I keep the team's best ressource as long as I can and as far as I'm concerned. If that means letting someone sink if even if I could risk helping him, then I'll err on the side of caution and preserve that team asset that I know is doing its best to win (me). I also didn't say I'm only helping certain clans or well known players. I said those are the only ones that I'd back up even in case of doubt because I can reasonably expect them to know what they're doing. I do believe I also said that in the (unlikely) event that some random player is filling me with confidence. So if I see someone trying to coordinate in team chat ("will support DDs in cap X if I can get a smoke" or "going to spot that DD, please focus fire"), I'll back them up as long as it doesn't seem reckless. That is plenty enough teamwork as far as I'm concerned and about as effective as I can reasonably ask for in terms of results. Anyone wants more from me, I'll ask for a higher standard of teamplay from everyone else that fills me with enough confidence that I'm not wasting me time and putting my ship at unnecessary risks.

Whilst everything you wrote is entirely correct, my experience with randoms says that taking one for the team at essentially any point of the game is plain russian roulette. I'll spare the plethora of "randoms are bad, mkay" anecdotes, suffice it to say that I wouldn't trust the average randoms I'm seeing to break out of a wet cardboard box if I gave them industrial cardboard box openers and written instructions on how to use them. Putting myself in unnecessary danger to help those people is (as arrogant as that sounds) quite possibly lowering the team's chances at victory proportional to the amount of damage I'm taking and the typical potato level of the random who got himself in a position where I'd need to take some punches to the chin in order to help him. Now, I'm not saying "screw teamwork". I actually tend to plug the gaps in team positioning if at at feasible (read: not suicidal) if needs be, but I do that mostly because I feel confident in my chances. With divisionmates I feel confident holding a flank just by our threesome against half or so of the entire enemy team. With randoms? Hell no, I'd be turning around and kiting the moment I see any number of enemy ships that I can't handle all by myself unless those randoms filled me with confidence in their skills which is pretty hard to do these days ... essentially reserved for forumites or by association with competent clans (if say a [TTT] fellow decides to take a stand I'd back him up, otherwise I'd nope right the hell outta there). In an optimal environment I'd have no reservation in agreeing with the TO, alas however ...

Don't look at me folks. I've been busy perusing the Scrub Secret Society's Top-Sekrit archives for rare colour documentation on our contributions in World War 2.5 after they've been finally cleared to release to the public. Quality research takes time! Here a downsized sneak-preview:

@xXx_Blogis_xXx I summon thee. Give us a screenshot of your current credit balance. What I'd love to see is a bank facility for clans. Members could drop excess credits into the bank account for every clan member to use and if WG feels a bit generous they might even add a system that generates oil depending on how much credits are in the clan bank.

Short of learning programming and then disassembling WoWs source code for potential issues or straight up building a completely new PC, I really haven't forgotten anything. And no, I don't use Windows Creator. It's really just the game, which is why I'm impotently raging at WG since that is the only recourse left for me after I exhausted all potential options to try and troubleshoot the issue myself.

InB4StarsavailableinthePremiumshop Oh ... and something I nearly forgot but is simply too precious not to share: @Loran_Battle is my witness, I exemplified our clan esprit in an earlier game to the point of nearly breaking down in laughter. For details I pass the mic to our dear Second Overlord, because the memory is starting a couple chuckles again.

Clearly he didn't have enough Vodka.

Akizuki is the Epicenter of attraction! I hereby and forever henceforth do declare the Inner Circle on Tears of the Desert to be claimed by her Most Zuki-Zuki Highness Akizuki by the grace of the Heavens, the Earth, the Seas and 160 rpm 100mm/65. In other news, I also unlocked myself this thing:

@Loran_Battle Found it: https://imgur.com/gallery/rljFq A sneak-peak (look at the entire album, that stuff is amazing!):

... I did. Really, I don't need anyone asking me if I did this or that. It's not my end. It's just the game not working stable for whatever vodka-induced reason. The whole sh*tshow started with patch 0.6.1. The game worked flawlessly before that patch. Ever since that patch I got multiple CTDs per gaming session, though thankfully mostly just randomly in port or when loading up games. A quick client restart lost me perhaps half a minute of the match start. Annoying, but I can deal with that. With the last big patch however (0.6.13) the game started to randomly freeze up ingame during matches. No error messages or anything, it just freezes up completely and I have to kill the process via Taskmanager. Seriously, it's not me having a faulty install, or a potato PC full of bloatware or whatnot. The only reasonable explanations that I can give at this point is that WG straight-up blundered with the optimization process for higher spec PCs (assuming all their budget and effort went into making sure it runs on russian potato PCs). Nothing else fits the symptons ... to repeat: PC exceeds hardware specifications, clean OS (with latest service updates), clean installs (double-checked), no mods, up to date drivers, no hardware failures (checked CPU, GPU, RAM and harddrive), stable highspeed internet connection (no connectivity issues or noticable packetloss, then again internet issues would result in different issues that CTDs/game freezes anyway). Problems started precisely with patch 0.6.1 (randoms CTDs in port, starting up battle queue, loading up the match or exiting to port) and escalated in 0.6.13 (ingame freeze-ups).

Relevant:

AHAHAHAHAHAH!!! "huhu" -> Chat Ban! Ich lach mich krumm

I want rainbow tracers. Like, tracers that literally leave a rainbow in their wake. And I'd put 'em on my Atlanta. You know why and you know you want too!

If you'd be looking at a captain just for the Atlanta, yes she can make good use of one due to her quirky gameplay features. With a 19 point captain you'd optimally look at: Row: Priority Target Row: Adrenaline Rush Row: Demolition Expert or Basic Firing Training Row: Concealment Expert, Advanced Firing Training and Inertia Fuze High Explosives Lastly the remaining point should go into Preventive Maintenance (first row). To really make that build work you'd need a 18 point captain, so that takes a while. A 14 pointer with just Concealment Expert and Advanced Firing Training works pretty decent too, tohugh most of your damage against equal/higher tier cruisers and almost all battleships will come from fires (unless they're generous enough to give you a neat broadside at around 7km range for the AP to really bite in). The choice between Demolition Expert and Basic Firing Training is largely preference. With the former you get some more fires to add to the damage, but the latter straight-up buffs your DPM by 10% (which in the long run also increases your firechance proportionally since you fire 10% more HE shells at the enemy, duh) ... one thing to consider is the latter also buffs your AA considerably, so if you like playing together with friends in CVs, there's that. Alternatively, assuming the upcoming USN CL line will keep their HE shells, you can select Superintendant instead of DE or BFT and train that captain up for use with the CLs (additional charges for consumables, also benefits the Atlanta's Radar, and the heal which the hightier CLs should get like all other hightier cruisers). This also has the added benefit that you can train the captain on the Cleveland for now (and on the other CLs once they're released), where the lack of say AFT isn't quite as limiting (a Cleveland without AFT is still formidable, so you can go for CE first, IFHE second and then add AFT with a sufficiently highlevel captain). I personally wouldn't recommend playing the Atlanta without AFT due to the restraining firing range, or without CE due to its frail nature, range and detectability are paramount for ships that can't take many hits on the chin. Long story short: You're going to do a lot of captain grinding, but unless you absolutely want to maximize the cpatain skills for the Atlanta alone, the build should synergize incredibly well with the upcoming USN CL which helps with captain levelling (and eliminates the necessity to simultanously grind up yet another captain for those).

Let me guess, you invited another potato into the clan when you intended to report him? That is precisely the reason why I asked to revert back to normal grunt level membership