Archipelago World Generation

This resource shows all worlds that are in development and tests them automatically, rather than checking each one by hand. By running a variety of tests, their generation stability can be estimated which reduces the likelihood of errors at generation time. It also reflects the actual status of an apworld as that can differ from the reported stability on the community sheet.

Per world, a seed is generated for the world on its own, for two players of the same game, and for the world alongside core games chosen at random. The solo and multi-game runs are done ten times each, with a different seed every time, and the Tested stability label is based on those results. Both are also run twenty times with the world's options randomised, rolling a different combination each time.

This page covers generation and stability, not gameplay. A world that generates successfully may still be unplayable. The sheet's Stability column is the provided claim, while the Tested stability column is what the testing pipeline found.

The list of worlds comes from the community-maintained Playable Worlds sheet, and the worlds themselves are written by the Archipelago community. Neither is the work of this pipeline, which downloads what the sheet points at and reports what the tests found. A world missing from the sheet is missing here too, and a world that fails here is not thereby a poorly made one.

Columns

Every date and time on this page is shown in your own timezone, as your browser reports it.

Any row

Click a row to open that world's own page — its version history, every test's pass rate and interval, and each failing attempt with the seed it drew. Ctrl or Cmd click opens it in a new tab.

Game

The name as written on the Playable Worlds sheet. Links to where the apworld came from.

Source

Where the apworld comes from. GitHub, GitLab, Codeberg and itch.io are named individually. Custom covers every one-off site, and Discord means the link is to a channel or a message rather than a file, which cannot be downloaded at all. Included means the world ships with Archipelago, so there is nothing to fetch.

Version

The version the world declares for itself in its own archipelago.json — its own numbering, not Archipelago's. Core worlds have one too, read from the Archipelago source instead of from an apworld. Unknown means the world ships no manifest, or ships one that names no version, which is true of about half the core worlds and a third of the rest.

Options

Opens the world's player options on the Archipelago WebHost this pipeline serves, where its settings file can be made. Only worlds the WebHost has loaded have the link.

Release Date

When this .apworld file was uploaded — not when its release was first created, which can be much older if the file was replaced later without cutting a new release. For a core world there is no file, so it is the date the Archipelago release carrying it was published. Unknown means no apworld could be obtained, so there is no file to have a date.

Test Date

When this pipeline last tested it.

Compatibility

Whether the file was built against the Archipelago version actually running here.

Availability

Whether an apworld could be obtained for this game at all.

Reported stability

The value listed on the sheet, not a test result.

Tests

One chip per generation test. A world's own page has each test's full result, how many of its attempts passed, and the seeds and companion games any failing attempt drew.

Tested stability

Stable means every test passed. The single-game and multi-game runs decide between the other labels, since they are what a player actually does. A failure in the duplicate or randomised runs cannot make a world Flaky or Broken, but it does stop it being Stable. Open a world's page for each test's pass rate and p-value. Click a colour in the bar at the top of the page, or its key, to show only that label; click further ones to add them, and click a selected one again to remove it.

Detail

A one-line summary of the first test that did not pass, cut down to the sentence that says what went wrong - the lists of unplaced items and unfilled locations the generator prints are left out. Click a summary that does not fit on one line to wrap it. The untouched output is on the world's own page.

Compatibility

Current

Uploaded after the running Archipelago version was released, so it was built against it. Core worlds are always current.

Outdated

Uploaded before the running version was released. It was never built against what is actually running, so it may break even though its last test passed.

Unknown

No apworld, or no known upload date, so there is nothing to compare against.

Availability

Apworld

A file was downloaded and tested.

Core

Archipelago ships this world itself, so there is no apworld to download and nothing to test — it is supported by definition.

None

No apworld could be obtained: the link points somewhere that cannot be fetched automatically (a Discord message, an unsupported host), or the release contains no apworld. It says nothing about whether the game works.

Tests

S

Single game — the world on its own, every option at its default. Run repeatedly with a different seed each time, so the result is a pass rate.

D

Two players, same game — the same world twice in one seed. Catches state shared between players that a solo test can never see.

M

Multi game — the world alongside companion games. A world can generate alone and still break in a real multiworld. Also repeated, and also reported as a pass rate.

SR

Random options, alone — as S, but with every toggle, choice and range rolled at random instead of left at its default. Only run if S passed.

MR

Random options, multi game — as M, with the same rolled options. Only run if M passed.

Test outcomes

Passed

A seed was generated successfully.

Flaky

Generated on some attempts but not others. The single-game and multi-game tests each run ten times with a different seed, so the fill differs every attempt. A world that succeeds 7 times in 10 is unstable in a way one run could never show. Worse for a player than a consistent failure, because nothing warns you which seeds will break.

Failed

Generation was attempted and did not succeed — a crash, a timeout, or items that could not be placed.

Invalid options

The world rejected the randomly rolled option combination as impossible. A real failure, not a technicality: a player who writes random on those options hits the same error, and only finds out when generation runs.

Needs input

Generation needs a file this pipeline does not have, almost always a base ROM.

Unverified

The file did not load as exactly one world, so nothing could be tested. Not promoted.

Unknown

The test was not run — usually because no apworld could be downloaded, or because the plain-options test it depends on did not pass.

Regressed

This passed immediately before the last Archipelago upgrade and no longer does, so the upgrade itself broke it.

Tested stability

Stable

Every test passed.

Minor issues

Generated on every attempt alone and alongside other games, but one of the other tests failed. The Tests column shows which.

Flaky

Generated on some attempts but not others.

Solo only

Generated on its own every time, but failed alongside other games.

Broken

Never generated, or the file did not load as a world.

Unknown

No apworld to test, generation needs a file this pipeline does not have, or the world is one this pipeline declines to test. The Detail column says which.