The Outlast Trials Season 7: Project Boneyard Guide

What this Season 7 page can safely say

The Outlast Trials Season 7 should be treated as a release-tracking topic, not a timeless rules page. The research brief for this site records Project Boneyard as a Season 7 signal, but it also requires a fresh official check before publication. That distinction is important: a codename, teaser, or community summary can change before launch, and a launch announcement can change again after a hotfix.

The useful work on this page is therefore the verification path. When an official post is available, record the exact announcement date, live game version, affected systems, and whether the change is permanent, seasonal, or event-only. Then update the Trials list, Rigs guide, and beginner guide only where the new behavior changes a player's decision.

Season update checklist

How to read seasonal patch notes

First separate availability from strategy. A patch may announce a new activity without changing the general Trial loop. The player count page and crossplay page should stay unchanged unless the official notes alter platform support, online requirements, or party size.

Next identify the decision that moved. If a Rig's control window changes, the Rigs page should update its scenario advice. If an objective or enemy warning changes, the affected Trial or Characters page should carry the new route. If a PC requirement changes, the system requirements page should reproduce the official store value and mark the review date.

Finally keep the old context visible when it helps. A short "previous behavior" note tells returning players why a familiar route feels different. Do not silently overwrite a version-sensitive recommendation and leave an old video or internal link pointing at it.

Project Boneyard: how to avoid overclaiming

The name Project Boneyard is included here because it is the seasonal term in the research plan for this site. Until an accessible first-party announcement confirms the release state, scope, and platforms, it should be read as a research signal, not a verified list of features. The page will be updated when a current official source is available.

That boundary still gives players something useful. If you are deciding whether to return for Season 7, check the official announcement, compare the live version to the date on any guide, and look for changes in the Trials category before bringing a pre-season loadout. If a page does not state its version or review date, treat its "best" recommendation as a starting hypothesis.

Maintenance order after a confirmed patch

1. Update this season page with the official source, version, date, and confirmed changes.
2. Review the affected Trial and MK-Challenge entries.
3. Recheck Rigs, upgrades, and any tier criteria that depend on the changed behavior.
4. Re-read the beginner guide for steps that now use different menus or routes.
5. Run link, frontmatter, sitemap, and build checks before publishing.

Verification workflow for a live Season 7 change

Start with the first-party announcement, then open the live game or current platform listing to see whether the announced item is available to the reader's platform. Record the title of the announcement, its publication date, the version named in the note, and the exact systems it changes. If the post uses a preview or future tense, keep that language in the page until a release note or in-game check confirms the change.

This distinction keeps a seasonal page useful when the official record is incomplete. It also tells a maintainer what to do next: find the missing primary source, test the live menu, or leave the item labeled as a signal. The Trials list should receive the confirmed activity details, while the Rigs guide should receive only the role changes that affect a real decision.

How to read an old Season 7 guide

An old video or build post can still explain a route, but its date and version are part of the claim. Compare its menu wording, objective, Rig behavior, and enemy warnings with the current game before copying the recommendation. If one detail differs, use the old material as context and follow the current prompt; do not combine an old route with a new objective as though they were one tested strategy.

Returning players should also separate access from value. A seasonal activity may still be playable while a former build is less useful, or a new reward may exist without changing the safest beginner route. Review the beginner guide for unchanged learning steps, then update the affected section only when the patch changes what a player should do.

What this page will publish after confirmation

Once a current source confirms Project Boneyard's release state and scope, this page can add the exact date, platforms, affected Trials, changed Rigs, and a short historical note. Until then, the page's strongest answer is the verification path itself. That is more useful than a confident list of features that may belong to a preview, a regional rollout, or a different patch.

How to keep seasonal advice useful between checks

Evergreen pages should continue to answer stable questions while this tracker waits for a confirmed source. Crossplay, party size, and the published PC table can be reviewed on their own schedules; a seasonal signal should not silently rewrite them. When a reader reaches this page from an old build guide, point them to the current version and ask which decision they need to make: whether the activity is available, whether a Rig still behaves the same way, or whether the beginner route changed.

A short update note can then do three jobs: identify the source, name the affected decision, and say what remains unknown. For example, a confirmed activity release can link to the Trials index while a pending balance rumor remains labeled for follow-up. This makes the page useful to players who need a current answer and to maintainers who will revisit it after the next official announcement.

Visit Red Barrels' official game page for the first-party update trail. This wiki remains independent and will label unknown or unconfirmed details instead of presenting them as official facts.