How a round works
Attackers plant the Spike, defenders stop them. First to the round target wins.
6 min read 1,266 words VALOSTRIKE Player Support
Contents · 14 sections
Understand the objective first
VALOSTRIKE is a team shooter built around attacking and defending sites. On Ascent, attackers try to create an opportunity to plant the Spike while defenders try to stop them or recover the site afterward. Eliminations matter because they change the resources available to each team, but the objective remains important even when only a few players are left. Before focusing on complicated tactics, learn which side you are on and what the round currently requires.
Prepare during the buy phase
Use the opening time to choose equipment, check ability availability and decide where you intend to go. Look at the team's plan before committing to a separate route. A simple shared destination is easier to execute than several individual plans that never connect. Keep an eye on the round interface for the current phase. Menus and equipment choices are easier to handle before an opponent can pressure you than during the first contested moment.
Play one life carefully
You normally have one life in a round, so every early decision can affect the rest of the team. Move with a purpose, avoid exposing yourself to several angles at once and communicate useful information when safe. Taking a fight is a decision about the objective and available support, not just a chance to increase a score. When eliminated, avoid filling communications with guesses that the remaining players cannot verify or use.
Attack with the Spike in mind
Attackers need to account for the Spike's location as the round develops. Reaching a site without the objective does not create a completed plant, and leaving its carrier isolated can make a successful entry difficult to use. Communicate the intended route and check that the person carrying it can follow. When the situation changes, explain the new plan briefly. Clear information about where the Spike is can be more valuable than a long description of a duel.
Defend the sites and the clock
Defenders need to understand which routes are covered and which information is missing. A quiet area does not prove opponents are absent; it only describes what you have observed. Give factual calls and avoid abandoning every position based on a single uncertain sound. If the Spike is planted, the task changes: the team needs to recover access and complete a defuse before the objective resolves. Staying alive without addressing the planted Spike does not finish that task.
Know how the round can end
Attackers can win through elimination or a successful Spike detonation. Defenders can win by stopping the attack before a plant, or by defusing after a plant. The planted objective changes the situation: do not assume eliminating the last attacker automatically resolves an active Spike. Watch the current objective state and progress indicators. The interface is a better reference for the round's remaining task than a remembered rule from another mode or another game.
Communicate practical information
Use a location, a confirmed observation and a useful intention. “Spike at A; I can cover your approach” is more actionable than several shouted guesses. If you are unsure, say so. Avoid revealing private information in public chat or attacking a teammate for a mistake. A team can recover from a failed plan more easily when the next instruction is understandable. Reporting abusive behavior is separate from giving useful round information.
Learn from a round without overgeneralizing
After a loss, identify one decision you could improve: an exposed route, an uncoordinated purchase or a missed objective interaction. Do not try to explain every loss as a technical problem. Conversely, an unexpected interface state is worth documenting when it contradicts what actually happened. Separate a tactical mistake from a reproducible defect. A recording of the relevant sequence can help you make that distinction without relying on memory after a tense fight.
Follow the match progression
Teams change sides during the match. Re-check your role and equipment options after the switch rather than continuing the previous plan automatically. The current scoreboard and round display show the match state; rely on them for the configured target and progress. Practice the basic attacking and defending tasks before worrying about advanced strategy. Understanding when the objective changes is a foundation that remains useful even as maps, agents and balance evolve.
Ask for help with a specific situation
If a round result seems incorrect, describe the mode, map, side, approximate time and objective state before the end. Explain whether the Spike was planted, what the timer showed and which players remained if known. Avoid asserting information you could not see. A clip spanning the final interaction and result is more useful than the final scoreboard alone. Use Gameplay & bugs for an unexpected result or a Getting started article when the question is about learning the rules.
Think in distinct round phases
Before the round opens, check your role, equipment and the team's intended route. Once play begins, gather information and move with a purpose. If the Spike is planted, update your plan around protecting or defusing it. When a round ends, use the next preparation period to review equipment and communicate. Treating every moment as a search for eliminations makes it easy to miss that the objective has changed.
For a new player, a useful first goal is being able to explain the current phase out loud. “We are preparing,” “we need to enter a site,” and “we need access to the planted Spike” imply different next actions. You do not need a sophisticated strategy to contribute. Following the current objective and giving accurate information already helps teammates make decisions.
Read a round result without guessing
After a close finish, check which condition resolved the round. A player eliminated near the end does not by itself explain whether a plant, defuse, timer or elimination determined the outcome. A short sequence matters more than the final image. If the result appears inconsistent, preserve a clip that begins before the decisive interaction and describe the order of events you saw.
When no clip exists, write a factual timeline. Include your side, whether the Spike was planted, what the progress indicator showed and what result appeared. Label uncertain timing as uncertain. Support can work with an honest partial account, while an invented exact duration may send an investigation in the wrong direction.
Communicate after elimination
After losing your life for the round, you can still share useful information from your last confirmed observation. Say where you saw an opponent and when, rather than presenting an old location as their current position. Give teammates room to hear game cues and finish an interaction. Repeating a guess loudly is less helpful than one brief accurate call.
If another player makes a mistake, save a detailed discussion for a calmer moment. Instructions shouted during a clutch can distract from the very objective you want completed. Focus on the information available and review the decision afterward. A new player learning the objective is different from someone deliberately sabotaging a match.
Frequently asked first-match questions
Do I respawn immediately? The standard round loop gives you one life in that round. Watch the current mode and interface for any mode-specific differences, and use the next round to adjust rather than expecting a respawn timer to solve the situation.
Is the round over when one team is eliminated? Check the planted objective and the result indicator. A remaining objective interaction may still determine the outcome.
What should I learn first? Understand which side you are on, where the Spike is and what action can still win the round. Add advanced routes and ability combinations after those decisions feel familiar.
Still need help with this topic?
Send the team a private ticket. Include what happened and the steps you have already tried so we can continue from here.
Contact support