About

About this field guide

Moadra Field Guide is an independent reference for Gloomsoft's Moadra. It explains the systems, the platform differences and the launch-window reception without pretending to be an official wiki or a hands-on review.

What this site covers

The site has a game overview plus fourteen task guides: a beginner route, a chapter walkthrough, the map and fast-travel screen, leaving the Underground Depths, double-jump and high-ledge workarounds, the weapon roster, the Gatling Blaster, the Amari fight, the boss list, platform and Switch 2 compatibility, the demo and download routes, launch reception, playtime and mods.

Not every guide is equally deep. The walkthrough is a verified chapter index rather than a room-by-room route, the Gatling pickup route is linked but not transcribed, and the exact double-jump unlock point is not published anywhere readable. Those limits appear on the affected pages instead of being filled with invented steps.

How facts are checked

Store pages and the developer's own pages are the first source. Dynamic values such as price, discount, review counts, player scores and patch plans carry the date they were observed; they are not presented as permanent facts.

Published reviews are used for impressions of difficulty, pacing and playtime, with the publication named. The 12–18 hour playtime figure comes from one review, not from an official statement or from this site's testing.

This site has not played Moadra. It does not claim hands-on verification of controls, frame rate, route difficulty or boss behaviour. Where the source material stops, the page says so.

Sources

These are the pages read for this build, all checked on 5 November 2026. External links open in a new tab.

Independence

Moadra is developed and published by Gloomsoft. This site is not affiliated with, sponsored by or endorsed by Gloomsoft. The Moadra name and store imagery belong to their respective owners; screenshots are used to identify the game and its systems.

Updates and corrections

Pages carry a checked date. A correction that changes a fact should change that date; a rebuild or a re-deployment alone should not. When a store changes a price, a score or a platform statement, the affected block is updated first, then the checked date.

This build has no comment system, account or contact form. Corrections are made from the primary sources listed above rather than from unsourced messages.

Field index

Search the field guide

Enter opens · Esc closes · Ctrl KBrowse all guides