Blight: Survival database

Use the Database route for the broad record set, Weapons for gear, Enemies for threats, Co-op for team play, and Status for release timing. The split keeps survival details readable while exact damage, drops, and encounter rules are still unavailable. If you are deciding what to follow before launch, start with Status, then move to the page that matches the decision: gear choice, enemy behavior, or squad planning.

A good database entry should answer what the thing is, where it was shown, and why it matters to a player. If the game has only shown atmosphere or a category name, the page keeps that as context instead of turning it into fake stats. Weapons can describe role and handling once visible; Enemies can describe behavior and threat type; Co-op can describe party implications; Database ties those records together once names and fields are known.

When new gameplay or a developer update appears, add the entity first, then the useful fields players can act on: weapon role, enemy behavior, co-op implication, or release/status change. A clip showing a blade, shield, ambush, or formation should not immediately become a damage table. It should become a clear record of what was shown, why it matters, and which follow-up page needs more detail.