PanludiaBEHIND THE DIRECTORY
How we select
integrations.
Panludia focuses on PC and browser integrations. Implementations requiring console hardware, console emulators or console ROMs and disc images are outside our editorial scope. This is a platform choice, not a judgment about those projects.
From discovery to a documented listing
The selection processStart with the original project
We identify the game edition, maintainer and original repository or distribution page. Discovery lists help us find candidates; they are not evidence that an integration works.
Check the installation path
We review available setup instructions, dependencies, releases and supported game versions. Operating-system support must be documented for the integration itself, not inferred from the game's store page.
Compare claims with evidence
We examine documentation, release notes and issue reports. Where relevant and feasible, we inspect source code or package contents for specific compatibility, progression or security concerns. This is targeted review, not an exhaustive audit of every file.
List with context, or hold back
A documented installation path and understandable limitations can justify a listing with caveats. Unresolved credential exposure, unsupported game versions, contradictory core progression or an essential component we cannot inspect can lead us to hold an entry back.
Keep the decision traceable
Community pages identify their maintainer, sources, reviewed version or date and known limitations. Findings concern the material reviewed at that time; later releases can change the assessment. User reports, static-code findings and reproduced defects are different kinds of evidence.
Keep popularity separate
Platform reviews and release download totals help visitors sort the directory. They do not establish safety, integration quality or the number of Archipelago players. A listing does not automatically add an integration to the launcher.