The Outlast Trials Trials List: Programs and MK-Challenges

Trials vs MK-Challenges

The Outlast Trials Trials List starts with one key distinction: a Trial is a longer, story-driven therapy run, while an MK-Challenge is a shorter therapy that uses a modified or redesigned section of an existing map. Red Barrels' official game description makes this distinction directly. Both formats use the same core habits: understand the objective, watch the space, manage threats, and extract when the job is complete.

The difference matters for planning. A full Trial gives a team more time to lose resources, split its information, or overstay after the objective is done. A shorter challenge can be a useful place to practice one interaction or route without committing to a long session. Neither format should be treated as a simple combat arena.

A practical Trial index

This table is an index framework, not a claim that every Program has the same objective. Individual Trial pages should carry their own objective, enemy, and version notes once those details have been verified in the live build.

How to read an objective

1. Find the verb. The objective usually tells you the kind of interaction the game expects: carry, activate, destroy, locate, or escape.
2. Find the repeat. If the same interaction appears several times, decide how the party will rotate watch duty and recovery.
3. Find the danger. A marker can lead into a noisy room or a narrow route. Identify the fallback before the first interaction starts.
4. Find the exit. When the objective completes, pause long enough to confirm where the team will regroup. Completion is not the same as extraction.

A new player who follows the marker without understanding the verb can spend a long time in the wrong room. The beginner guide gives the first-session version of this process; this page keeps the index logic available when you return for a different Trial.

Party size and Trial planning

Solo players should treat each objective as a sequence of jobs: interact, watch the route, recover, and move. A duo can divide those jobs, but both players still need to understand the full plan in case one is downed. A three-player group can keep one flexible responder, while a four-player group can cover more space but must manage noise and separation.

The player count page covers the trade-off in detail. The important Trial rule is simple: never split farther than the group can rescue, and never start a long interaction without a fallback route.

Rigs for different Trial shapes

Rigs should answer the failure that is most likely to end the run. Information helps when the route is unclear. Control helps when an interaction needs a window. Recovery helps after a down or a long objective. Escape helps when the shortest route is no longer safe. See the Rigs and builds guide for a scenario-based comparison rather than a permanent tier claim.

Avoid changing every part of a loadout between formats. Keep one familiar item or Rig, change one variable, and record what happened. That makes a seasonal balance change easier to understand and keeps a failed run from turning into a random build search.

What a useful Trial entry should contain

A name alone is not a useful Trials list. Each individual entry should answer the question a player has before loading in, then state the boundary of what has been checked. The proposed record below keeps the index scannable while giving future pages a consistent evidence standard.

This structure lets a reader compare two activities without pretending that their objectives are interchangeable. It also gives the maintainer a clear update task when a patch changes one field. The Rigs page can explain the role framework once, while a Trial entry only records why that role matters in the selected space.

Using the index during a changing rotation

Seasonal rotations can make an older route appear in a new context. Check the activity name, Program relationship, and version note before treating a saved route as current. If the objective is familiar but the room, enemy warning, or extraction prompt has changed, keep the old route as historical context and write a new current note rather than silently merging the two.

A short MK-Challenge is often useful for testing one decision: whether the party can read a particular prompt, keep a regroup point, or save a tool for the exit. A full Trial is better for practicing a longer sequence of decisions, including how the team manages resources after an interruption. The choice depends on what you are trying to learn, not on a permanent rule that one format is always easier.

When the group fails, label the failure by stage: objective recognition, route choice, interruption, recovery, or extraction. Then change one variable on the next attempt. This keeps a Trials index tied to real decisions and prevents a list page from becoming a collection of unverified difficulty claims.

A simple choice before loading in

Ask what the group wants to practice. Choose a shorter MK-Challenge when the goal is to learn one mechanic, read a compact route, or test whether a Rig covers a specific failure. Choose a full Trial when the group is ready to practice pacing, resource use, and extraction across a longer sequence. Confirm the objective and regroup point in either case, because a shorter activity still punishes a party that starts moving without a shared plan.

This choice also helps a returning player interpret a result. Finishing a short challenge proves that one decision worked in that space; it does not prove that the same loadout will be optimal across every Program. A long Trial exposes more opportunities for a route, resource, or communication plan to fail. Record the format beside your notes so a useful lesson stays attached to the situation where it was observed.

What this list will track next

The next content pass will add verified Trial and MK-Challenge entries with the objective text, Program relationship, enemy warnings, expected route, and last checked version. Pages will be added only when the entity has a stable search question or a meaningful decision to explain. This prevents an index full of names with no useful answer.

Until then, use the official Red Barrels game overview for the current format definitions and return here after a patch for a refreshed index.