What the official combat language confirms
The official Steam page frames CONTROL Resonant as a single-player action RPG in a warped Manhattan. Its description explicitly mentions supernatural powers, the Hiss, Mold, and an Aberrant weapon that can take forms including a hammer and dual blades. That is enough to define the combat vocabulary for this hub. It is not enough to publish damage charts, ability tiers, resource rotations, or a final “best build.” Those details are still version-gated because the game has not released at audit time.
The most useful early question is therefore how the systems are meant to fit together. Powers are likely to be the part of the combat loop that changes the space around an encounter, while the Aberrant weapon supplies close-range forms. The wording “likely” is important here: until the game’s tutorial and official documentation show the complete loop, a guide should distinguish direct product facts from interpretation of trailers and previews.
Read an encounter as a space, not a damage race
Current official news and gameplay material point toward combat in a dynamic city with anomalies, puzzles, side content, and bosses. That suggests players will need to read the room as carefully as an enemy health bar. Check for vertical routes, objects that might matter, cover, hazards, and exits before committing to an attack. This is a preparation habit, not a claim that a particular object can be thrown or destroyed in the final build.
The safest first-session routine is to let the tutorial establish the action vocabulary. Note which inputs the game assigns to powers, how the weapon forms are selected, and whether the game communicates a resource or cooldown. Then test one change at a time. If a preview showed a flashy move, do not assume that it is available at the first save, that it has the same timing, or that it belongs to every difficulty setting.
Powers: separate confirmed names from imagined trees
“Supernatural powers” is confirmed product language, but the official store page does not provide a complete ability list or unlock order. A good guide can still help a reader prepare by explaining what to record: the power’s in-game name, the first point at which it becomes available, the input or menu used to select it, whether it affects enemies or the environment, and any resource or cooldown displayed by the live build. That format creates useful launch documentation without inventing numbers.
When a public source uses a descriptive phrase rather than the game’s final name, preserve both carefully. For example, a trailer may show a movement or telekinetic effect while the shipped game uses a formal ability label. The article should say “the trailer shows” until the tutorial or official glossary confirms the label. This keeps search coverage broad while protecting players from following a preview-only term.
Threats and anomalies need version labels
The Hiss and Mold are named threats in the Steam description. The official news vocabulary also points to anomalies and bosses. These entities can anchor future encounter pages, but a guide must not assume that every Hiss or Mold variant behaves the same way, or that an anomaly is a combat encounter rather than a world activity. Once the game is live, each entry should identify the version, location or mission context, visible cues, and a reproducible response.
Until then, use the threat names as an index. A player searching for “Hiss combat” should find a concise explanation of what is officially known and a link to the dated source. A player searching for a boss should see an honest status note if the boss name, phase order, or reward is not public. A thin page that only repeats “check in game” is not useful; the combat hub instead explains how future evidence will be evaluated.
Weapon forms and movement choices
The Aberrant weapon is the central arsenal term currently available from the official store text. The hammer and dual blades are named examples, so they belong in cross-links and glossary language. Exact form switching, range, stamina, animation timing, and upgrade costs do not belong in a definitive table until the live game confirms them. A preview image can establish that a form exists in a scene, but it cannot establish the full rules of that form.
Players can prepare by avoiding tunnel vision. If a form is close-range, the surrounding space, movement option, and power interaction may matter as much as raw damage. If a form has a different rhythm, the tutorial and first safe encounter are better learning environments than a late boss. These are general combat-reading principles, not a disguised claim about an unreleased stat system.
A launch testing checklist
On first launch, record the difficulty and accessibility settings before testing a new power. Capture the wording of the tutorial prompt, the first ability or form name, and any displayed resource. Reproduce one ordinary encounter in a safe room, then compare one environmental interaction and one enemy interaction. Do not draw conclusions from a single scripted set piece. If an update changes a timing or unlock, keep both the old and new version notes rather than silently rewriting history.
The technical page should also record whether the PC build exposes separate graphics, input, motion, subtitle, and aim options. A combat guide should link to that page instead of burying accessibility advice in a damage discussion. Good combat coverage lets a player choose a comfortable setup and understand the encounter, not merely copy a speedrunner’s settings.
Sources: Steam store page, Remedy news, Remedy official game page.
This complete topic entry is source-backed; revisit it after release when official mechanics, requirements, and update notes change.