Panocek

Yet if one asks WG to actually hold their own word and "punish glitchers" one should also accept part where bonk arrives from Last Stand usage. Otherwise it makes you a Though amount of fun and engaging for banning our local flaming primadonna is probably going to be... just right More realistic option would be just global pop-up for all players reminding to not use glitches/bugs/exploits for their own gain and that being end of story

Thing is, EULA clearly states "abusing all exploits" is punishable (excerpt 2.16), it makes no distinction how severe they are. So either WG holds their own word, or draws some artificial line "which exploit is bannable enough", which is totally going to scare people from trying to stretch the line and see where it breaks And you could argue if extra acceleration, allowing you to either accelerate out of harms way when coupled with Propulsion Mod OR put Steering Gears OR DamaConMod to get other benefits while retaining bonus acceleration falls outside "to obtain any competitive advantage"

Except not really. You benefit from Last Stand acceleration bug all the time, whether you had skill before because ship in question loves to lose engine/rudder, or you've heard about the bug and decided to invest into the skill.

With that logic, anyone who ever played ship with Last Stand skill should be gifted with a ban, given skill was (and still is?) bugged, giving extra acceleration.

In soviet russia... You know the drill

Or psychological tricks to make "playing WoWs" a habit are at work. Game for me wasn't enjoyable in a long time and people I've been playing with or forums to shitpost on were bigger "keeping factor" than game itself, then there's disagreeable direction game is heading development wise. That and I guess any game will simply get old after playing it for 7 years basically straight.

"cyka blyat rush b"

It wasn't a bug, it was part of the game since day one, but WG at some point decided to tone down battleships casually devstriking DDs by capping pen damage to equal of that of overpen. Khaba and Harugumo retained that "feature" for quite some time, then WG in early tests of French DDs also kept that as "balancing factor over improved saturation".

You mean UI guys had to come up with something to prove themselves worth keeping in employment?

The best part is, quick, dirty and effective solution I can think of would be simply adding bit of delay between firing under guise of "aiming guns", so game client is forced to "update" ballistic chart. Whole trick is not easy to pull off in normal conditions already (high, stable framerate, consistent low ping etc), so delay of 0.1s or similar would probably be just enough duct tape to keep the bowl of spaghetti from leaking

Why pay testers to do the job, when testers can pay you for your live product?

MVP. Minimum Viable Product Technically it does work, and I wouldn't be surprised if it was working for 7 years by now. Its just... not exactly exploitproof Everyone gangsta until NorCal starts firing comets at people

Same trick should be doable with Wyoming as well, as by the looks of it, game pre-calculates time to impact and penetration at initial short range, then applies the same properties at target 20km away if you flick mouse fast enough

Its not a bug, its a feature. Though tying entire ballistic system to the camera and aimpoint is too galaxy brain for me to handle. I guess it compares to Bethesda tying physics engine in Skyrim to framerate? and yes, few minutes in training room and I've confirmed these bugs myself. Gearing yeeting shells off the map, covering 20km in less than 1s as well scoring citadel hits at 10km against Minotaur, when normally guns can't penetrate 102mm plating past 5km is certainly amusing. On screenshot above I've tried to track the shells after firing, but they landed before camera got anywhere close. Shot taken at 10km

Commander REEEwork happened under guise of "introducing more variety". In practice, it is nothing more than cashgrab and nerf to ships that proved to be "bit too effective". Only positive aspect of it are separate skill trees for single Commander, so you can rock your best commander on as many premiums as possible with skills that aren't straight up detrimental.

When devs themselves are toxic to the playerbase... what was the saying? you reap what you sow?

My guess it would be combination of fast redeploy that can bring some dp on the side, if anything. Also ranged fast redeploy is kinda novel, besides Kafka s2 and sort-of Amber April.

As usual, game mode dependant on teammates being actual teammates, not just enemies you can't damage for some unfathomable reason.

Its no different than any other tryhard division, with goal of winning and/or farming salt. Probably both.

Certainly novel approach, but I don't think it will be actually useful. Certainly I doubt it will dislodge Flagpipe combo, not without handcrafted map and (de)buffs present to make new character interesting.

Any chance for this to make into the game as one of the camera presets, akin to sound presets (cinematic, night etc)?

Kinda this. Many currently available ships are mediocre compared to older, removed from sales units and while they were so-so before introduction of supershits, I don't see reason for spending even "free" resources on getting these now. Which puts into question why gather these in first place

Ise trades main guns for planes. Kearsage doesn't. Also she have one of the best, if not the best theoretical accuracy from all tier 9 12gun battleships, as well she have the fastest reloading guns from 12gun 406mm armed ones - Hizen reload at 38s, Minniesota at 40s, while 380mm armed Pommern/Alsace have 33 and 32s respectively, both come with noticeable accuracy loss to boot. Only flaws I can think of are: -doesn't turn AT ALL -massive hangar makes her vulnerable when trying to use all guns -low velocity guns, same as NC, so it takes some getting used to -her looks can be charitably described as "charmingly autistic"

Because WG can change it and you have no say about it

I've managed to log in just fine +-40min ago, trying to log in now results in failure