NaVi T-Side Dual-Corridor Default: Late A Smoke vs Mid Thickness—Who Eats the First Rotate

September 23, 2026 at 22:07:35

NaVi’s T default splits A hall soft contact from mid/connect hard presence, then times smokes on the second beat so CT’s first rotation often pays for the wrong lane.

Lead

When you break down NaVi’s T-side default, the first peek matters less than which corridor buys information first, which lane trades utility for half a beat, and where the second wave of nades lands when CT is forced to rotate. Read it the way CTs habitually do: anchor roles on one line, utility tempo on the other.

Dual-corridor anchors: soft A hall, hard mid thickness

NaVi commonly sets A hall entry as a soft roof—someone can take CT’s first angle without fully committing body on second zero. Mid and connector carry hard thickness: two bodies staggered so CT cannot free-advance the windows and door-axis timings they trust.

If CT’s muscle memory is “noise at A, reinforce A,” T often tags A corridor with a one-step peek and immediate fade. The info is real; the cost is controlled. What actually burns rotation budget is usually the connector-side cell inside mid thickness—they may not open first, but they sell “mid is about to explode.”

Read keys:

  • Soft roof sells motion; hard thickness sells commitment.
  • Fade the soft roof too early and A CT saves nades; stack thickness too deep and the second-beat swing to A lacks bodies—NaVi often adds real A pressure only on beat two.

Utility chain: late smoke and second-beat cash-in

Their nade lines rarely chase “three smokes white at open.” More often the first util serves mid thickness, while A hall smoke or flash deliberately arrives half a beat late, in the ~4–8s window, after CT has already shifted toward connector or mid.

Typical tempo (conceptual, not a fixed script):

  1. 0–3s: A shallow smoke or pop flash on mid—goal is not full deny, but to stop connector from hugging window for free reads.
  2. 4–8s: Late A smoke lands—if CT already moved toward connect, A CT often sits in the awkward “smoke before bodies” phase; soft roof upgrades to short burst or paired flash.
  3. Second-beat cash-in: Hard-thickness side chooses fake-to-real or real-to-fake, pinning the third CT’s path on half-open door axis or narrow lateral choke.

CT counterplay is not “see smoke, instant re-clear.” Track which lane threw util first and which lane only sold footsteps. On NaVi defaults, first util lane ≠ first hit lane; the corridor with the late smoke is often where first kill and first rotate actually happen.

Endgame entry: default stop-loss on thin info

When the dual-corridor default stalls, NaVi tends to carry unredeemed util on one lane into the clutch—e.g. mid still holding a connect-closing smoke, A keeping flash without body. CT clutches that read “last smoke side = hit side” get rotation-faked by the util ledger; safer to track who still holds the hard-thickness anchor in the final minute.

Stack framework (five-man, copy rhythm not pixels):

  • Lock soft roof / hard thickness as two roles; third owns the late-smoke clock.
  • Post-round, two questions only: Who paid CT’s first rotate? Did beat-two util land on a rotation CT already committed?

Treat the default as a rotate-debt allocator, not “who wide-peeks is the hero.” NaVi’s dual-corridor default is hard to read because smoke lateness and thickness bluff rarely share the same corridor.