VALORANT Lotus A execute guide for patch 13.02
A consistent Lotus A execute begins before the barrier drops. The attacking team needs a Rubble plan, utility for A Main and Tree, a plant location that.
Updated for VALORANT patch 13.02. A consistent Lotus A execute begins before the barrier drops. The attacking team needs a Rubble plan, utility for A Main and Tree, a plant location that matches surviving control, and a post-plant call. Patch 13.02 keeps Lotus in the competitive pool and does not replace those geometric fundamentals.
Lotus A execute: the core plan
Use one initiator effect to clear or displace the first A Main defender, one smoke for Stairs or top site, and a second smoke for Tree. The entry pair takes site space while the spike carrier stays one trade behind. Do not spend every flash on the doorway: one piece of reactive utility should remain for a defender pushing through Tree or retaking from Drop.
This is a repeatable decision framework, not a promise that every opponent or server will react identically. Test it in a low-stakes environment, record where it breaks and change one variable at a time.
Step-by-step execution
- Step 1: At barrier drop, send two players toward Rubble with rifles ready for the close swing. A third player watches the A Lobby flank timing instead of stacking five bodies into one choke.
- Step 2: Use recon, a drone, Trailblazer or a carefully placed flash to test A Main and the close cubbies. Clear one angle at a time; do not assume a smoke removes a defender who can push through it.
- Step 3: Place the main site smoke to cut the long defender sightline and smoke Tree before the entry commits. Announce both expiration times so the planter knows whether a safer default plant is necessary.
- Step 4: The first entry crosses to take the nearest site contact while the second keeps a tradeable distance and clears under Heaven or close cover. The spike carrier follows only after those two angles are addressed.
- Step 5: Plant for the space actually controlled. If the team owns A Main, choose a position visible from that lane; if defenders still threaten the planter, prioritize a completed safe plant over an ideal lineup.
- Step 6: After the plant, split surviving players between A Main and gained site space. Save one molly, flash or recon for the tap, call who swings first and avoid giving defenders separate one-versus-one fights.
Assign one player or one clear cue to every transition. Plans often fail because two correct actions happen at different times. Short, specific communication keeps information useful without filling the channel with narration.
Common mistakes
The common failure is arriving with five players but no order. Early smokes expire while teammates wait, the carrier blocks the entry path, and everyone watches Stairs while a defender emerges from Tree. Another error is planting for A Main and then abandoning A Main, leaving no one able to punish a defuse behind utility.
Do not repair every failure by adding complexity. First decide whether the cause was information, timing, spacing, resources or execution. The smallest correction is easiest to remember and test on the next attempt.
Practice routine
Enter a custom lobby with the exact five-agent composition. Mark the time from barrier drop to both smokes landing, then repeat until the entry crosses on the same cue. Run the sequence with one defender in each common position and rotate that defender after every repetition. Finish with three post-plant drills in which the retaker taps immediately, waits for smoke fade or flanks through Rubble.
- Record the first moment the plan became uncertain.
- Check whether the required resource was available.
- Review spacing before blaming mechanics.
- Keep successful parts when changing the failed step.
A replay or saved clip is more reliable than memory after a tense attempt. Review the decision before the outcome: a poor choice can succeed, and a sound one can still lose. Repeat the same setup until timing is stable before adding a harder variation.
Communication and role ownership
The initiator owns the first-clear cue, the controller calls smoke placement and duration, and the spike carrier confirms the plant. Entry players report cleared spaces rather than shouting only damage. In the post-plant, name the first contact and the player holding the spike tap. One person calls the swing so utility and rifles arrive together.
Adaptation checklist
If defenders fight Rubble, slow down and trade that space before revealing the full hit. If they give A Main but stack site, preserve recon for after the first smoke. A repeated Tree push requires a trap, late lurk or held rifle, not automatically another early smoke. Against fast retakes, keep two players close enough to contest site instead of retreating into identical A Main angles.
If an update changes geometry, economy, cooldowns or damage, retest the affected step rather than assuming the whole guide is obsolete. The version label above defines the boundary of this advice.
Final routine
Review whether the team controlled Rubble, whether entry utility landed before the cross and whether the chosen plant matched the post-plant positions. Correct the earliest failed condition first. A clean plant produced by poor trades is not a repeatable success, and a lost round can still demonstrate a sound execute if the final duel was simply missed.
Keep one learning goal per session. A narrow objective makes improvement visible and prevents a long checklist from competing with the match itself. Stop the drill once concentration falls, then return with the same measurable goal.
Sources: primary release notes or official records. Factual claims were checked against these records; interpretation is our own.
Continue with the Kaizensclan archive, our practical guides and the latest game reviews.
Editorial note
Facts and mechanics were checked against the linked primary sources before publication.
This article was reviewed on August 11, 2026.

Community channel
Join the discussion
Start a thoughtful, specific conversation about this story.
Verified readers only
Continue with Google to comment.
Your Google account creates a reader-only Kaizensclan profile. Your first comment is reviewed before publication.