Blight: Survival database | confirmed systems tracker

Use this page as the index of what can and cannot be turned into database rows yet.

Current answer

The database index can organize confirmed categories, but exact rows need source-backed evidence.

Use this page as the index of what can and cannot be turned into database rows yet. The current evidence package treats Blight: Survival as pre-release. The strongest source is the Steam app record, then the official site, then dated Steam news items. That order matters because a player-facing wiki page does not convert anticipation, trailers, or search demand into exact build, recipe, route, enemy, or vehicle data.

Source list

Confirmed public facts

Steam describes Blight: Survival as a PvE action-horror survival game in a brutal medieval world, playable solo or with up to three friends against monsters and human opponents.

• Action, Adventure, and Indie genres in Steam app details.
• Single-player, Multi-player, Co-op, Online Co-op, Cross-Platform Multiplayer, Stats, and Steam Achievements categories in Steam app details.
• Steam text supports survival, horror, medieval combat, co-op, and hostile human/non-human threats at the category level.

These facts are enough to justify this page as a public watch page. They are not enough to publish final database rows where the official material has not named the entity and shown the field. That distinction is the main evidence rule for this site.

Page-specific evidence map

• Steam confirms survival/action-horror/co-op scope, so weapons, enemies, co-op, and status pages are justified categories.
• The checked sources do not provide complete rows for stats, drops, locations, or enemy properties.
• The latest saved Steam News API item is Dev Update: July 2026 from 2026-07-15 UTC.
• The database can publish entity categories now, but requires row-level source evidence before adding exact values.

Claim status table

What players can do with this page now

Use this page as a decision filter. A player can safely learn what the public sources actually confirm, which topics deserve tracking, and which guides need a future update when launch, demo, beta, or official news data becomes more specific. If another site publishes exact values that this page does not list, compare that claim against the source ledger above before trusting it.

For database confirmed detail tracker, the useful current action is to keep a short confirmed-so-far list instead of a final answer sheet. Save the relevant source URL, record the checked date, and write down the exact player consequence. If a source only confirms a broad system, keep the page at system level. If a source names an entity but gives no value, create a watch item. If a source names an entity and shows a value, then a table row can be considered.

Evidence needed before stronger advice

A database row needs a named entity, at least one gameplay-relevant field, and a dated source that shows the entity rather than inferring it from genre tags. The new source needs to be public, stable enough to cite, and specific enough that a reader can verify the same claim without relying on interpretation. Screenshots or captured gameplay can help after public access exists, with separate labels from official text.

Before changing this page, collect these fields:

1. Source URL and publisher or uploader.
2. Date checked and date published if available.
3. Exact claim being added.
4. Player-facing consequence of the claim.
5. Confidence level: confirmed, supported, partial, or blocked.
6. Whether the claim affects a route, item, ability, requirement, phase, reward, price, platform, or release answer.

Unsupported claims kept out

The current sources do not support weapon damage tables, armor mitigation values, enemy health pools, extraction rewards, map routes, talent trees, boss names, drop rates, and optimal co-op compositions. Leaving those details out is intentional. A thin but sourced page is more useful than a large table that has to be corrected after launch. This page is designed so unsupported rows can be added quickly later, but only after the source package can defend them.

Recheck sequence

1. Reopen the Steam app page and confirm the release field, developer, publisher, genres, and categories.
2. Check the official site for announcements or press updates that are newer than 2026-09-13.
3. Query the Steam News API and compare the newest title/date against this page's latest saved item.
4. If the new material changes a player decision, update the Current answer and Claim status table first.
5. If the new material only adds flavor, keep it out of gameplay advice unless it confirms a useful field.

Source links

• Steam store: Blight: Survival on Steam
• Official site: Blight: Survival official source
• Steam News API: latest public news feed
• Main hub: /
• Release status: /guides/release-status/

Quick FAQ

Is this enough evidence for final recommendations? No. It is enough for release-aware tracking and confirmed category pages, but not for final row-level recommendations.

Why does the page repeat dates and source names? Because the site is covering games that are unreleased or near release. The checked date is part of the answer.

When does this page change? Change it when Steam, the official site, a dated developer post, or public gameplay evidence provides a claim that alters a player decision.