Casualties Unknown Experiment — Role and Character Guide

The Experiment is the subject at the center of the run

Casualties: Unknown places an expendable test subject inside a hostile alien environment. Your assignment is to retrieve lost cargo by navigating the caves while managing the conditions of the character you control. The Experiment identity describes that subject and its place in the premise, rather than a separate game mode with an independently verified set of rules.

This matters when interpreting a search result that uses experiment loosely. A lore explanation, a character discussion and a mod demonstration can all mention an Experiment while answering different questions. Begin with the player’s role, then identify whether the rest of the source concerns official progression, a particular NPC or a community addition to the base game.

Connect the character with the game’s survival systems

The playable subject has to deal with supplies, crafting and injuries during the descent. The official description emphasizes the limb and cardiovascular simulation, so survival involves reading conditions rather than treating the character as a single generic health bar. Tools and resources matter because the assignment places the Experiment in environments where mistakes can end a run.

The developer recommends learning the tutorial before starting that journey. Crafting and First Aid introduce practical interactions that apply to the subject you are controlling, including making useful items and handling wounds. Those lessons provide a firmer basis for early decisions than an invented character-build chart that has no matching version or source.

What the developer announced about three characters

The September progress update announces three playable characters. The developer describes them as having their own statistics, distinctive mechanics and different approaches to play. The statement establishes a planned variety of character experiences without supplying a verified table of every ability, starting attribute or interaction in the eventual release build.

The same update introduces the choice as the Experiment and two other species. Keep that wording attached to the developer’s announcement rather than filling the remaining slots with names or power descriptions drawn from unverified lore discussions. The supplied research deliberately excludes invented ability tables, so this overview focuses on the confirmed structure of the announcement.

How the announced character sequence works

The developer says you unlock the next character by finishing a run with the previous one. This describes a sequential progression rather than a promise that all announced characters are selectable immediately. It also means that a character introduction and an unlock walkthrough are different kinds of information, even when they appear under the same general topic.

The supplied brief does not establish a tested route through those release unlocks. It establishes what the developer said the progression would require, with the full game still scheduled for launch at the research date. Use that announced requirement to understand the intended sequence without assuming that every step has been independently completed in the public demo.

Keep demo availability separate from full-release plans

The Steam demo covers five cave layers, while the full game was announced with eleven. A statement about the full release’s characters belongs to that larger release scope rather than automatically describing the selection screen in the demo. Compare both the product and the version when a video or discussion seems to show more content than your installation provides.

The launch announcement says the demo will not receive the full game’s changes. That makes the distinction meaningful for character progression as well as crafting, balance and later environments. An announced unlock requirement should therefore remain labelled as release information instead of being presented as a troubleshooting fix for a demo menu that does not offer the same options.

Understand the Expie nickname without mixing contexts

Expie is the community shorthand associated with an Experiment. It is useful for recognizing discussions of the familiar player subject, but the same word also appears in fan art and a separate trader entry. Read the surrounding context before treating a sentence about an Expie as a specific claim about the playable character’s mechanics.

Fan-made appearances and skin replacements do not expand the official character announcement by themselves. They concern community designs or modifications, while the developer’s progression statement concerns the full game’s planned playable lineup. Keeping those categories separate lets you enjoy the community terminology without mistaking every named design for a confirmed unlockable species.

What to do with this information before a first run

Start by learning the Experiment’s practical assignment and the systems used to survive it. Play the available tutorial, inspect crafting requirements and learn how the health panel describes injuries. These are actions supported by the collected material and directly related to the player subject, rather than guesses about an unreleased character’s ideal build.

For later progression, follow the developer’s announcements and match any detailed guide to the released build it covers. The November 8 material supports three announced characters and sequential completion-based unlocks, but does not establish a complete launch walkthrough. That is enough to explain the planned progression clearly while leaving unsupported ability values and character-specific routes out of the guide.

Separate an announced requirement from a complete walkthrough

The developer’s progression statement tells you the intended relationship between finishing a run and unlocking the next character. It does not supply a route through every layer, a tested ending choice or an ability-by-ability comparison of the full lineup. Reading the statement at that level answers how the sequence is described while avoiding the assumption that a short announcement is already a complete progression manual.

When a community post appears to contradict the announcement, identify whether it is describing the public demo, a playtest or a later release. The product and version can explain why a menu, character choice or completed run is being discussed under different conditions. Retain those details before treating one player’s screenshot as evidence that the developer’s announced requirement applies identically to every available build.

For your own next step, decide whether you need help with the present character or information about the planned unlock sequence. The first question points toward the tutorial, crafting and injury controls; the second points toward the developer’s progression announcement and a matching release guide. Keeping them separate makes the Experiment overview useful without filling gaps with invented names, starting values or guaranteed optimal builds.

Continue exploring