Search the Community

Showing results for tags 'check'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Posting Place
    • News and Announcements
    • Newbie Palace and New Users Introductions
    • Shenanigans
    • Patron Plaza
    • Ask Me Anything
  • Purple Player Interaction Centre
    • Casual Purple
    • Ask a Purple Poaster
    • Purple Poaster Replay Place
  • Serious-Face Enabled Discussions
    • Core Skills & Mechanics Discussion
    • Metagame Discussion
    • People, Platoons and Pwning
    • Vehicles
    • Upcoming Changes Discussion
    • Mathematics Corner
  • Improvement and Study
    • Mentor Meet-up
    • Tape Study
    • Articles
    • Tanks Media
  • Clam Rivalry and Posturing
    • Clam Wars Recruitment
    • [NA] The Drama Llama says: WTF Subversions?
    • [EU] Professional Pro Gamering: stronk tenks and stronk taktiks
    • [SEA] Low Server Population Clam Wars Edition
  • Related Games
    • World of Warships
    • World of Warplanes
    • World of Tanks Console
    • World of Tanks Blitz
    • Armored Warfare
    • War Thunder
  • The Archive
    • Garbage Can


  • Never's Blog
  • Melol's Blog
  • Melol's Blog
  • bjshnog's Game Dev Blog
  • TayTay's Diary
  • Noobs corner
  • Evelyn's Biting Corner
  • Dire's Blog
  • Constie's Awesome Adventures
  • Deft Penk Hidey Hole
  • blerg
  • Mundane Things
  • Majestic's Blog
  • WoTLabs Blog
  • German fanboy sperg blog thingy
  • A cheesy blog
  • Kuroi's Clubhouse
  • B-log
  • Ollie Tabooger's House Of Buttpiracy
  • vonblogger
  • _Clickers Blog of Rando Things
  • Blog name *
  • The_Illusi0nist's Blog
  • Shitposting With Skittles
  • rojo180's Blog
  • Tomhwk's Titillating Teal Time
  • how do i use a Kv2 effectively when teamates refuse to help me in WOT?
  • my blob
  • my blog
  • Shoe's Blog
  • Grumpy fail purple siema player is here
  • No Bullshit Reviews
  • The Journey
  • Sigh...
  • TEST
  • Reports of a beginner
  • CSI: Chinese Server Insanity
  • Hallo1994: Simply, Me
  • Wanderjar's Notebook blog
  • My journey to being a better player


  • World of Tanks
    • Tank Reviews
    • Strategies
    • Videos
    • Mods
  • Game Theory

Found 3 results

  1. Since I haven't been able to find enough opinions on this tank, let's start here! What are your thoughts for ya'll folks who have owned it, or played it at all. Pros? Cons? Meh's? Quirks? Stronkholds? Tell me how you feel. Tell me how you REALLY feel.
  2. Here's a quick summation of why invisitanks happen, even during a peek-a-boo, but also the action-reaction cycles of those situations. A poster @ NA WoT forums complained about Romulan tanks... and well, my post there is only going to be forgotten anyway, so I might as well put it here where people give a damn. More Romulan cloaking devices found. His beef was summed up in the following video video. My responses buried on the bottom of page 3; the wasted breathe and breathtaking Paint.NET skills ridiculous South Park-calibre box tanks shan't go to waste. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Sight lines (server vision checks) are drawn from the center of objects on your tank -- hull and turret -- such that your most-distant corner sprocket can be seen first by a passive tank parked on an edge. All of that foliage in your face and between you and the E100 doesn't help either. It's gimmicky but that's the way it is. Spotting Mechanics: It's in a spoiler because this is a touch esoteric. Spoiler Basically ANGLES: I'll draw a Paint.NET file since my coffee is still scalding: Note: of course, these are not perfectly to scale, but I did, in fact, draw 2 yellow lines from the T34 HT analogue, and it displays an important caveat: when you pie a corner by moving forward: your 2 vision checking areas can overlap -- so it really puts you at a disadvantage. (Whereas you can see with the E100 HT analogue, depending on the exact model and forward / center / rear turret placement of a vehicle, it can have overlapping spot-check lines, increasing the coverage) Finally, the E100 is very tall, and might have a spot check going over bushes you cannot, to see your front hull. did mention some time long after 6.4 they changed or added spot checking areas IIRC, but having played through many a patch cycle, I can tell you that they haven't really changed the scenario above. ++++++++++++++++++++++++++++++++++++++ ====================================== HOW TO DEAL WITH IT: 1) patience if that's an option; of course, there's a very simple technique available to at least rule-out the presence of a tank there with some confidence of probability: 2) when you get to the suspected camp position of a tank, and you are CONFIDENT YOU ARE NOT CURRENTLY SPOTTED, you poke just ... a bit and back off. IF your lightbulb pops: you can bet poking hard and fast is gonna hurt -- a lot. Especially since it could be that worst-case scenario -- high-armor + alpha turreted heavy. And Patton knows what else. 3) Once a fight is joined in these situations, you'll want to bait the defender into shooting first and bouncing / missing / tracking you. A well-disciplined or skilled defender probably won't make the mistake, but many, many players do, and then they can be put into an increasingly negative action/reaction cycle. 4) in the sillier, mutually-stacked peek-a-boo fights, target selection is everything. *Did the very forward guy back up into a teammate? Well, make him pay while he's still exposed. *If possible, track the one in behind, trapping 2 tanks! (this is exceedingly rare) *Is there a tank in the rear of that stack with crappy armor? Often, he'll get left hanging in the wind by his bigger teammates in front, or can be caught off guard *SECURING A KILL IN THESE SITUATIONS IS OFTEN VITAL -- but only provided it's one of the tanks with actually relevant firepower / armor in this situation. Over-pieing to kill a medium tank who mostly wasn't penning people is a waste of hit points. Taking a shot, or even 2, but KILLING the biggest / toughest tank or best-damaging-output PLAYER (often a unicum, but just as often a solid green or blue purple) often IS worth it. *just as important a consideration -- taking shots for teammates, if you have the armor for it. The peeking side which conserves guns/lives usually prevails. 5) not an additional tactic but of absolute importance: you need to know your tank's armor profiles in this situation -- how reliable the off-angling glacis armor becomes, your back up speed, how exposed your sprocket is (permatrack here is quickly lethal, esp. tier 9+ matches) -- and your own tank's soft-gun stats and ability to work against enemy armor. It's rarely over quick, except for enormous, concerted pushes, or defenders against hapless, piecemeal attacks. =========== On your video: one last pointer: regardless of why/how the spotting works, the lightbulb gives you an edge to work with. When that allied Tortoise dies, it was his fading (residual) spot which timed out -- and made the E100 go invisible. At least, based on when you start your video, this is a reasonable inference. When you aggressively chase those vehicles, the worst case scenario is similar to what happened -- they actively disappear while you pie foliage and hard cover (the hill side) while you are lit the entire time. As it were, you and the E100 were mutually unspotted to each other -- you had an initial advantage which died with the Tortoise. (you were operating with knowledge of the E100, but not him, of you -- allied spotting) This is where my diagram kicks in. So the allied death reset the spotting cycle, and that E100 had the critical advantage of the defending spotting mechanics (and possibly the E100's height) and of course, tier/firepower. If anyone wants to add to this, clarify, pigeonhole -- esp. with-respect-to updates to the spotting mechanics ever mentioned in FTR which didn't make it to the NA WoT wiki -- please do so.
  3. I can't get a full grasp of what they're saying here... anyone? The wiki goes on to explain that there has been a visibility checkpoint where the dynamic view range port is located, what then does the release notes item describe?