.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 athttps://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, or Auto Deafen .akr packs.
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.Submit a map pack
Use the moderated in-game flow for map-linked StartPos, Auto Kill, and Auto Deafen packs:1
Open the target map
Load the map that owns the setup. Akron includes its map SID with the submission.
2
Open Upload Pack
Open Akron’s overlay, navigate to the Interface tab, and select Upload Pack.
3
Choose the pack section and attribution
Select StartPos, Auto Kill, or Auto Deafen. Choose Anonymous or Discord attribution. If you choose Discord, enter your Discord ID. Review the generated title and description.
4
Submit the pack
Make sure the setup includes at least one StartPos or area in the current map, then click Submit Upload. Akron automatically captures up to 10 matching rooms and submits the pack for staff review.
.akr files in their matching Discord pack forums.
Pack safety
Community packs use the same.akr import path as local exports.
- Export your current setup before importing a community pack.
- Confirm that the pack section is StartPos, Auto Kill, or Auto Deafen.
- For StartPos packs, install the same map and object-providing mods used by the author. Each imported StartPos includes its v10 snapshot, coordinates, and spawn settings.
- Imported settings can affect attempt status and proof metadata when used.
- The Community Packs browser accepts StartPos, Auto Kill, and Auto Deafen setup archives.
- A public pack contains
manifest.json,setup.json, and one v10 snapshot entry per StartPos. Its manifestkindissetupand its payload format isakron-setup-v8.
Size limits
Akron caps catalog and pack downloads before importing:- Catalog index: 1 MiB.
.akrpack download: 512 MiB.- Setup payload inside an
.akr: 2 MiB. - Each compressed StartPos snapshot attachment: 128 MiB.
- All compressed StartPos snapshot attachments in one pack: 509 MiB.
- Each downloaded catalog preview image: 2 MiB, no wider or taller than 2048 pixels, and no larger than 4,194,304 pixels in total.
- Marked-room captures in one in-game upload: 10 rooms.
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.