Skip to main content

Deleting Games

You can remove games either by deleting files from /files or by using the API. Game progress and metadata are kept, so re-adding a game later is possible.

Deleting a Game via Filesystem​

Delete the game files in your files directory (default: /files).

  • If at least one version file is still there, the game remains visible.
  • If no version files are left, the game is soft-deleted on the next indexing cycle.

Example (Filesystem)​

Example:

  • Minecraft (v1.0.0) (2011).zip
  • Minecraft (v1.1.0) (2011).zip

Delete only v1.0.0 → game stays. Delete v1.1.0 as well → game is soft-deleted on next indexing.

Deleting a Game via API​

Admins can delete game files via API. With multi-version support, deletion is version-specific.

Behavior:

  • GET /api/games/:game_id returns the available version entries in versions[].
  • DELETE /api/game/:game_id/versions/:version_id deletes exactly one version file from disk.
  • If other version files remain, the game stays visible and another version may become the default download.
  • If no files remain, the game is soft-deleted on the next indexing or integrity-check cycle.

There is currently no bulk API endpoint that deletes all versions of a game in one call. To fully remove a game through the API, delete each version individually or remove the files from /files.

Only Admin users can call this endpoint, and the server needs write access to VOLUMES_FILES.

See API docs for full endpoint details.