Skip to main content
Community Packs opens an in-game browser where you can find and import community .akr setup packs scoped to your current map. Choose a category, search by keyword, and import packs directly without leaving the game.

​
Index URL

The browser reads packs from a JSON catalog at the configured Index URL (shown at the top of the Community Packs window). The default catalog is hosted at https://akron.micr.dev/catalog/index.json. You can point this to a custom URL or local file:/// path. Catalog entries can contain map-specific StartPos, Auto Kill, Auto Deafen, and other scoped .akr packs. The official catalog uses Akron-branded URLs, but the files are stored in Cloudflare R2 behind the website routes. Akron only sees normal HTTPS downloads: /catalog/index.json for the pack list, then a direct .akr URL when you import a selected pack.

​
Import a Pack

1

Open the target map

Community packs are filtered by the current map SID, so load the map you want a pack for before opening the browser.
2

Open Community Packs

Open Akron’s overlay, navigate to the Interface tab, and select Community Packs.
3

Refresh the catalog

Click Refresh to fetch the latest catalog index.
4

Filter entries

Choose a category (All, StartPos, Auto Kill, or Auto Deafen) and type in the search box to filter by title, description, author, map URL, section label, or tags.
5

Import the selected pack

Select a pack in the list, review its details on the right, and click Import Selected. Click a preview to inspect it at a larger size, or use See in Discord when the pack includes its source thread. Akron downloads the .akr file into Saves/AkronSetups/community-*.akr and imports the declared scope.

​
Pack Safety

Community packs use the same .akr import path as local exports.
  • Back up first. Export your current setup before importing a community pack so you can restore it.
  • Check the section. Verify that the pack’s section (StartPos, Auto Kill, and so on) matches what you expect.
  • StartPos packs can carry room state. StartPos community packs may include portable room-state snapshots for collected entities, flags, counters, inventory, player state, and respawn state. Akron strips deaths, time, and file stats from those snapshots before export and import.
  • Attempt-changing imports are policy-visible. Imported settings that affect attempt counts may appear in status and proof metadata.
  • Prefer scoped imports. Use section-specific packs over whole-setup packs when you only need one category.
  • Only setup archives import. Public packs must use the current .akr setup archive shape: manifest.json plus setup.json, with Kind set to setup and setup format akron-setup-v2.

​
Size Limits

Akron caps catalog and pack downloads before importing:
  • Catalog index: 1 MiB.
  • .akr pack download: 4 MiB.
  • Setup payload inside an .akr: 2 MiB.
The official Discord bot uses the same 4 MiB .akr limit before publishing a public catalog pack. Catalog screenshots can start larger than the stored image. Official upload paths store marked-room captures privately for review, then publish optimized JPEG previews for the catalog carousel. Moderator reviews show every submitted image, and published Discord galleries include navigation and download controls. In-game uploads automatically capture rooms that contain the selected StartPos, Auto Kill, or Auto Deafen content before submission. StartPos galleries begin with Slot 1 and continue in slot order. In-game uploads can submit StartPos, Auto Kill, and Auto Deafen packs. Generated titles use the current map’s localized name when one is available. Akron attaches the current map SID to the upload, so check that any Auto Kill or Auto Deafen areas in your active setup belong to the current map before submitting.

​
Catalog Contract

Catalog entries point to .akr downloads and identify the section, map SID, title, author, tags, and update time. See Community pack catalog for the JSON schema and Akron .akr archives for archive validation rules. Catalog maintainers should validate pack metadata, scopes, and download URLs before publishing a shared catalog.