Jump to content
Forum Shutdown 28/7/2023 Read more... ×

Aotearas

Players
  • Content Сount

    8,460
  • Joined

  • Last visited

  • Battles

    13076
  • Clan

    [SCRUB]

Everything posted by Aotearas

  1. Aotearas

    New MM is an audacity

    That abbreviation you use (MM), I don't think it means what you think it does.
  2. Aotearas

    Never aim below the waterline

    To be entirely fair, a big naval gun shell has exponentionally larger surface to bleed energy when in contact with a high resistance medium like water and the nature of the fuse employed in those shells (base fuzes that were triggered by the inertia shock from the sudden deceleration) meant that hitting the water nearly always set them off prematurely. In fact anti-submarine shells were so special compared to normal naval artillery shells because they did not trigger when impacting water. Or in short: A shell impacting water will lose a lot of energy very fast and depending on the distance to the actual target after the initial impact in the water may not retain enough power to penetrate the target's armour or even initiate the payload prematurely. The impressive water fountains of shells missing ships weren't simply splashes from the impact, those were the shells detonating.
  3. Aotearas

    Unbalanced games

    Or EVERYONE is potating
  4. Aye. There's a LOT of things that are working counterintuitive, like preferential matchmaking for lower tiers (t4 BB in a division with t4 DD or CL for example), the "Fire Prevention" captain skill being not nearly as effective as it says and unless I don't remember correctly the detection penalties for firing guns and fires aren't explained either (past a fleeting mention in the loading screens), just to name a few.
  5. Our division (Loran_Battle, DJ_DIE and me (duh)) ran into atomskitten. Sadly I picked the wrong side to #yolorush his Warspite and he had his guns waiting.
  6. Aotearas

    Weekly recurring mission reset early?

    They're going from 12th until the 18th (12:00 CEST).
  7. Sometimes people need to be taught a lesson ...
  8. Aotearas

    WG, you want no toxicity ingame ? Stop fail divisions then (4 tk inside)

    Now THAT is killstealing.
  9. Aotearas

    PSA: No Situational Awareness Bug

    Please guys, we all know how this works: he's got the blue community contributer tag, that means he's allowed to ignore normal posting etiquette. Just your bogstandard everyday favouritism, nothing out of the ordinary. The only thing noteworthy left here is iChase's absence in light of several comments challenging his evidence. But considering how the internet works, that's not really out of the ordinary too ...
  10. Aotearas

    Molotov available in the premium shop

    Then why is the Molotov cheaper than the Blyskawica? Even if it's a tier lower, it's a big cruiser compared to the Blyskawica destroyer. Following that logic it should also be more expensive. Or wait, ... why is the Ishizuchi not more expensive than the Murmansk then?
  11. Aotearas

    Molotov available in the premium shop

    So, the t6 premium ship is cheaper than the previous t5. Well, I suppose the upcoming Indianapolis t7 is going to be 15€ then. It would only be logical, right? ... right?
  12. Aotearas

    Some interesting info around the world

    T5-7 ranked, eh? So Saipan, Hiryuu, Indianapolis, Myoukou, Nagato, Blyskawica and Hatsuharu only ... plus the usual suspects like people entering with a stock New York, because raisins.
  13. Aotearas

    What's your most kills record ?

  14. Aotearas

    What's your most kills record ?

    13 frags in the Prinz Eugen.
  15. Most, if not all the displeasure with the current detection woes could be solved by simply updating the SA skill to include the 3s delay in unspotting so it doesn't drop when players are in fact still detected. That should be a no-brainer hotfix, THEN the devs and testers can go hunting down any irregularities to iron out whichever quirks there may be.
  16. Exactly. The limited sample size/data that can be generated by a relatively small number of STs (no idea how many there are) is simply insufficient to pinpoint a possible bug whose trigger is not know. Which is also the reason why iChase's "definite proof" thing is hilariously conceited at best considering a couple rounds in the training room is nowhere near enough data to conclude a bug doesn't exist if no consistent triggers are even know yet to replicate the more severe instances of keeping detected by the enemy when one shouldn't. Chances aren't bad it could be a bug that's dependent on server load (considering detection is handled serverside) and as such trying to find it in a handful training room sessions is just laughable.
  17. Aotearas

    zero inferior to wildcat ? Absurd

    To be a bit more accurate here: The 20mm were still easily punching through the armor. It's just that they didn't cause enough damage to disable the bomber fast enough unless they hit something vital like the engines. With a sturdily designed plane and a bit of redundancy, you can suffer a lot of holes into the airplane before it actually goes down. And since the typical attack pattern against a bomber formation was to strafe the formation and get out of its defensive fire umbrella ASAP, 20mm and machineguns simply couldn't deliver a sufficiently destructive strike (say alpha damage) in the short time they had a target, they upgraded to weapons that had more punch to maximize the firepower they could pour into a target during the limited timeframe.
  18. Aotearas

    PSA: No Situational Awareness Bug

    So, is iChase going to adress any of the counterarguments that have been stated (again)? You know, pop in and say that he might try some different tests? Maybe explain how the smoke blinking worked before 0.5.5. if it wasn't a change in how spotting/dtection works? Or maybe simply just acknowledging the fact that a handful controlled test environment games doesn't constitute a sufficient sample size to refute the possibility of a bug that might cause people to keep being spotted for far longer (and no, I don't mean just three seconds) and call it "definite proof"? Or is it just going to be pats on the back from the Youtube comments who appear to think us a bunch of morons and complaining for the sake of complaining?
  19. Aotearas

    Okey seriously im pink after 1 accident

    First of all, nice edit. Secondly, I very much doubt that people who suffer from damage inflicted be teammates (TK yes or no) specifically asked them to shoot an apple off their ship.
  20. Aotearas

    Okey seriously im pink after 1 accident

    This argument is stupid. Quite factually stupid! Are are assigning responsibility to the victim (if you can't deal with being TKed, don't play). That's the same twisted logic as "if you don't want to get raped, don't dress sexily".
  21. Aotearas

    Torpedo soup - why it exist and what can be done

    Considering the go-to counter for confirmed sniper presences is to simply mortar the crapout of the triangulated position of a sniper or possibly even calling in a fire-mission from nearby field artillery, unless body armour gets resistent to artillery strikes, comparing them to BBs is something you might try as a joke on a Drill Seargant when you lost the bet and got dared to make him smile
  22. Aotearas

    PSA: No Situational Awareness Bug

    Does not explain how DDs could blink in and out of detection when laying smoke screen when still cruising at speed. If the 3s delay worked the same way as they say it does now, then instead of being unspotted, spotted again, unspotted and spotted again in rapid succession, the 3s delay would effectively keep them permanently spotted until such time that they decelerated enough to remain in their smoke puff without outrunning it because the frequency of a DD smoking at maximum speed exiting its own smoke puffs is faster than 3s (meaning it would get respotted before the 3s delay would wear off, hence he'd never technically get unspotted for the attacker!). Also does not explain how I can get unspotted, wait a couple seconds, THEN turn away (to avoid blindfire along my previous course) and still be hit by an accurate salvo that shouldn't be possible because by the time I changed my course, the 3s delay was over and my course change couldn't have been seen, hence shells already in the air would've been aimed at a position that I'm no longer headed to. Trust me when I say I'd love to chalk that up to amazing prediction skills of the enemy players, but I've encountered this particular issue a couple times too many than my (possibly cynical) impression of the average player would admit being a reasonable possibility. __ I might add that it felt different to me before I heard/read about this supposedly being a bug, so confirmation bias shoudn't account for any misperceptions (or at the very least not for the initially percieved difference!).
  23. Aotearas

    Okey seriously im pink after 1 accident

    The previous system was something like that. The result was the griefers with rudimentary emotional control simply never caused enough damage to turn pink. But they kept causing damage. Aside from the stigma, what's actually so bad about being pink that it needs to be changed? You cause some team damage, you turn pink; you don't damage team mates for a while, the pink goes away. No one's physically forcing people to perform the walk of shame down their hometown to be ridiculed by their friends and neighbours causing a social stigma that will leave a mark on their remaining lifes. It's a game and if you play it correctly the chances to turn pink even with the currently imperfect system is ridiculously low. And if you torp from second line and catch a teammate who was busy trying not to die by the enemy to notice and/or evade your torps, then you bloody deserve going pink. Simple as that.
×