WARDOGS FIELD MANUAL

How to read WARDOGS playtest feedback

Verification status: editorial. Last verified: 2026-09-06

Playtest feedback is useful when it preserves context. A short clip or post can reveal a lead, but it cannot by itself establish a bug, balance rule, player count, or release commitment. This briefing separates the kinds of signals readers will encounter around a test.

Official statements set the status

Steam and BULKHEAD announcements determine access, scheduled events, and acknowledged changes. When a status changes, link back to that current statement rather than treating an older news item as the final word.

Repeated reports can form a lead

Independent players describing the same symptom can justify a focused check. Keep the build, platform, time, mode, and reproduction steps together. A report without that context should remain a report, even if it sounds plausible.

Opinions are not telemetry

Reviews and community discussion are valuable for learning what players notice, but they do not measure a whole population. A strong reaction may point to an onboarding or clarity problem; it does not prove a universal performance or balance result.

Use a three-part note

When sharing a finding, write: what happened, where and when it happened, and what evidence supports it. This format lets a reader compare reports without turning a personal match into a permanent claim about the game.

Continue with verified routes

For access and schedule questions, start with the official update. For technical symptoms, use the known issues guide.