Netherguard: Hero Hunt
Preparing the playable web game inside WordPress…
Netherguard is a compact deduction game for short browser sessions. Use confirmed clues, inspect suspect cards, and avoid unsupported guesses before naming the hidden hero.
Controls: pointer-based browser input. If the game does not load, refresh once and report the page URL, browser, device, and whether this loading card appeared.
Designed, written, and tested by Diligesker Lab · Public build reviewed July 30, 2026 · Report a gameplay or documentation mismatch
How to play this Netherguard browser build
Netherguard: Hero Hunt is a logic-deduction game, not a hidden-object search or a reflex challenge. A case presents demon residents, one or more heroes in disguise, and a complete set of statements about identity, position, traits, or relationships. Your task is to combine those statements until an accusation is supported. The useful habit is to ask which candidates are impossible before asking which portrait merely looks suspicious.
A reliable first investigation
- Read every clue once before selecting anyone. A direct identity statement may feel decisive, but row, trait, and neighbor counts often determine how that fact fits the rest of the board.
- Mark contradictions. If a suspect conflicts with a confirmed trait or position, remove that candidate from consideration. Do not replace evidence with repeated taps.
- Cross-check counts. A group count must still work after a direct clue rules a card in or out. If your tentative answer makes the total impossible, revisit the earlier assumption.
- Accuse only when the remaining clues agree. The intended solution is supported by a chain of evidence. The game is built so a lucky guess is unnecessary.
Controls, language, and progress
| Area | What to expect |
|---|---|
| Input | Use the on-screen controls with a mouse, trackpad, or touch. The game does not require keyboard shortcuts. |
| Language | The current game interface supports English and Korean. The WordPress wrapper selects English on a first visit; the in-game language choice can be changed later. |
| Progress | Campaign progress, tutorial state, and preferences can be kept in this browser’s local storage. Clearing site data or using a private session may reset that local state. |
| Account | No Diligesker account or sign-in is required to start the public browser build. |
| Session comfort | Portrait orientation gives the clearest layout on a phone. Browser chrome and very short viewports can reduce the visible play area. |
What this page loads
The play route fetches a WordPress-hosted HTML5 package, unpacks its files in the browser with the open-source fflate library, maps the packaged images and styles to temporary browser URLs, and then mounts the game. The initial loading card is therefore part of the expected startup sequence. Exact implementation and route checks are recorded in the Build and Test Evidence.
If the game does not start
Refresh once and keep the loading card visible long enough to note its final message. If the menu still does not appear, send the contact page the play URL, browser and version, device, orientation, whether the loading card appeared, and the last visible stage. You can still read the rules and current screenshots, follow the beginner clue method, or work through the Reedshadow Passage case without running the game.
Scope of this public build
This is a maintained browser edition of an experimental game. Screenshots and written rules describe the build checked on the review date above; balance, touch comfort, story presentation, and platform-specific features can change. The public change log records visitor-visible revisions. If a rule on this page no longer matches the shipped build, the correction route is part of the product—not an afterthought.