The Spike: planting and defusing

Know which team can do what

The Spike is the attacking objective. Attackers bring it to a valid site and complete a plant; defenders prevent that or complete a defuse after it has been planted. Your next useful action depends on the current state, so check the objective display before following a memorized route. Carrying, planting and defending a planted Spike are different tasks. A player can win an important fight and still need to finish an objective interaction afterward.

Locate the Spike and communicate

Before committing to a site, make sure the team knows where the Spike is. If you are carrying it, explain your intended approach so teammates can create space and cover it. If it is elsewhere, do not assume somebody will automatically bring it after an entry succeeds. Use the game's visible indicators and factual communication. An uncertain location should be described as uncertain rather than repeated as a confirmed call that sends the team in the wrong direction.

Reach a valid planting area

Ascent has A and B sites. Approach the intended planting area and watch for the relevant interaction prompt. Standing near a site does not necessarily mean every point around it accepts a plant. If the prompt does not appear, inspect your position and the objective state before repeatedly pressing the key. Stay aware of the round situation: opening menus or experimenting with inputs while exposed can turn an ordinary interaction question into an avoidable elimination.

Complete the planting action

Use the configured interact input and hold it for the required interaction. Watch the progress rather than counting a remembered number of seconds. Starting the action is not the same as finishing it, and an interruption can leave the objective in a different state from what you intended. Once the plant completes, confirm the new objective indicator. Tell teammates about the completed plant with a short factual call so they can adjust their next decisions.

Protect the objective after planting

After a plant, the task is no longer simply reaching the site. The attacking team needs to prevent a successful defuse while managing the remaining time and available players. Do not abandon all access to the objective merely because an opponent was eliminated elsewhere. Choose positions that support the actual goal and communicate useful information. A planted Spike can still require attention after the last visible fight; watch the round state instead of assuming the scoreboard alone has resolved it.

Approach a defuse carefully

Defenders need access to the planted Spike and enough opportunity to complete the interaction. Locate it, consider remaining threats and use the configured interact input beside it. Listen to available cues, but verify what the interface shows when possible. A teammate covering an approach can help make the interaction practical. Do not give instructions based only on a guess about the remaining time when the current objective display provides better information.

Read progress and interruptions

Watch the defuse indicator and note what progress remains after an interruption. The build includes a saved half-defuse checkpoint, so an interrupted action may resume from that checkpoint rather than from a completed defuse. The checkpoint is not a finished objective. Confirm that the full interaction resolves before treating the round as won. When reporting an issue, describe whether the bar started, reached a checkpoint or completed, because those are distinct observations.

Practice the sequence safely

Use the available practice area to learn the binding, required position and progress display. Start while standing still, then approach from a short distance and repeat. If you changed the interact binding, test the new input directly and inspect secondary binds if something unexpected happens. A successful practice attempt establishes that the basic control works on your device; it does not prove every live interaction will be uncontested or that a different position accepts the same action.

Common misunderstandings

Eliminating an opponent is not a substitute for checking an active planted objective. Holding the wrong key, standing outside the valid area or releasing before completion can all look like an interaction failure. Distinguish those possibilities before assuming the game ignored you. A single screenshot after the round usually cannot show which input was held or how the progress changed. If no recording exists, a careful timeline is still useful and should openly identify any details you are unsure about.

Report an interaction problem

Choose Gameplay & bugs and include site, map, side, objective state, binding, approximate time and what the prompt or progress bar showed. Say whether the action began and what interrupted it. A clip starting before the approach is particularly useful. Do not recreate the failure by sabotaging a teammate's live round. The goal of a report is to establish the visible sequence so the team can distinguish a placement, control, timing or game-state problem.

Compare a plant attempt with a completed plant

Consider an attacker reaching a site while a teammate covers the approach. The carrier starts holding interact, then moves away before the action finishes. Reaching the site and beginning the progress bar are both useful observations, but neither confirms a completed plant. The next decision should follow the actual objective state. If the team assumes the plant finished, everyone may reposition around an objective that is still being carried.

To avoid this, confirm the completion indicator and give a brief factual call. If the action is interrupted, say that it stopped. Your team can then decide whether to create another opportunity, recover the carrier's position or change the approach. Clear state information matters more than announcing an intention that was never completed.

Understand a contested defuse

A defender approaching a planted Spike needs to balance access, threats and interaction progress. Starting a defuse can reveal the defender's position, and an interruption can leave only partial progress. Watch the displayed state instead of assuming that a sound or a teammate's instruction means the full action completed. A saved checkpoint still requires the rest of the interaction.

When reviewing a failed defuse, identify what actually interrupted it. Was the input released, did the player move, was there an elimination or did the interface stop responding? Those observations produce different troubleshooting steps. Do not describe an ordinary interrupted action as a confirmed bug simply because the round was close. If the indicator itself behaves unexpectedly, include the moment it changes in your recording.

Make objective calls useful and short

Good calls answer a practical question: where is the Spike, did the plant complete, is a defender interacting, or is the reported information old? If you only heard a cue, describe it as a cue. If you saw progress, describe that. Your teammates can combine these observations with their own view instead of relying on a confident statement that exceeds what you know.

Avoid filling voice communication with repeated countdown guesses. The player completing an interaction needs game audio and space to watch the interface. Share new information when the situation changes. After the round, explain a confusing sequence calmly and use the visible objective state as the starting point.

Frequently asked objective questions

Why does the interaction prompt disappear? Compare your position, the objective state and whether another menu has focus. Note which change makes the prompt return. If the same valid position consistently fails, record the approach and interface together.

Can I learn the timing from an old clip? A clip can demonstrate the sequence, but the current progress indicator is a better guide to your present interaction. Updates and different circumstances can make remembered timings unreliable.

What should I report if the round result looks wrong? Include the side, site, state before the interaction, visible progress and final result. A clip covering the whole sequence is more useful than a screenshot showing only the result banner.