Published and maintained by Diligesker Lab · Published May 28, 2026 · Reviewed July 30, 2026. Mechanical claims are checked against the current browser build, project data, or test records. Report a correction.
ABOUT DILIGESKER’S LAB
Diligesker’s Lab is an independent browser-game site operated by a small game maker. It publishes playable builds together with enough evidence for a visitor to understand the rules, current state, and limits before starting.
What the lab makes
The current catalog contains two different games: Netherguard, a dark-fantasy logic deduction game, and Block Smash, a roguelike brick-breaker survival game. Both can be opened directly in a modern browser from this site.
Why the project pages are detailed
A launch button alone does not explain whether a game is current, how it works, or what may fail on a particular device. Each project page therefore includes current screenshots, first-minute instructions, controls, systems, known limitations, credits, and a last-check date.
How information is checked
Descriptions are compared with the current game build and project records. Technical notes are based on the actual WordPress play wrappers and hosted runtime packages. When a build, screenshot, control, or limitation changes, the related project page and public change log should change with it.
Use of tools
Development and editorial tools may assist with coding, testing, drafting, image preparation, or translation. They are not treated as sources. The site operator remains responsible for the shipped games, public claims, corrections, and decisions about what remains published.
Contact and corrections
Bug reports and content corrections are welcome. A useful report includes the URL, browser, device, the last visible step, and supporting evidence such as a screenshot.
Who publishes the lab
Diligesker Lab is the consistent publisher identity used by the independent creator who designs, builds, packages, tests, and documents the two games on this site. It is a small personal game lab rather than a multi-author news publication. The same operator maintains the WordPress play wrappers, project evidence, guides, policy pages, and correction inbox.
Editorial and testing standard
- First-party scope: strategy and system claims must come from the shipped game, its source data, or a reproducible test—not from another guide rewritten for this site.
- Evidence: screenshots are captured from a working build and captions identify what a visitor can verify. Random boards and rewards are presented as examples, not guaranteed outcomes.
- Version awareness: a visible review date means the page was compared with the current public route on that date. It does not imply that every balance value will remain permanent.
- Correction path: factual mismatches, broken routes, attribution issues, and unclear limitations can be reported through the Contact page. Confirmed visitor-facing changes are recorded on Updates.
How assisted tools are used
Software and AI-assisted tools may help search a codebase, organize test evidence, draft a first version, prepare an image, or check consistency. They do not create the underlying game experience and are not accepted as evidence by themselves. Before publication, mechanical claims are checked against the current game data or observed build, links are tested, and copy is edited for the actual page. Content that cannot be verified is removed rather than padded with a guess.
What readers should expect
The lab aims to answer a practical question on every page: what can I play, what decision does this rule change, how was the browser build checked, or what should I report if something fails? It does not publish general gaming news, scraped walkthroughs, paid rankings, or high-volume summaries. A guide should remain useful beside the game even if it never receives search traffic.