Data packs

Data Packs is where you browse and install reusable ArcadeStudio content packaged as .arcadepack files.

Development status

The current development build supports Browse in Cards or List view, local .arcadepack import, installation, pack cover art, and community repository catalogs. Marketplace checkout is not part of this documented flow.

Find and install a pack

1. Open Data Packs.
2. Use search and filters to narrow the catalog.
3. Choose Cards for cover-based browsing or List for a compact view.
4. Open a pack’s details and review its publisher, content type, version, requirements, and status.
5. Select Install.

Official and community packs remain identified separately. Installing a pack puts its content into Studio; it does not automatically make every optional layer active on the cabinet.

Install is not enable

Enable a pack in the workspace that owns its behavior:

Pack content	Where it becomes active
Catalog and metadata enrichment	Data Management → Workshop
Rules	Rules → Stack
Automation	Duplicate or create a flow, then turn Live on in Automation
Cabinet, controller, LED, overlay, or launch content	The matching Studio workspace, followed by Publish

Installation alone does not map LEDs, rebuild Master.db, turn an Automation flow Live, or publish anything to ArcadeServer.

Essentials metadata packs

The current bundled community catalog contains:

• NES Essentials
• SNES Essentials
• Genesis Essentials
• Dreamcast Essentials
• Game Boy Essentials

These are metadata-enrichment overlays with controller labels and colors where supplied by the pack.

After installing one, Studio marks the catalog as needing a database rebuild:

1. Open Data Management → Workshop.
2. Review Button labels, Controller templates, and Metadata enrichment.
3. Preview the build.
4. Select Rebuild Master.db.

The rebuild applies installed enrichment to the working catalog. It also works when there are no DAT or XML import sources: Studio starts from the existing working catalog and applies the overlay.

Caution

Rebuild catalog on the Data Packs page refreshes the shop catalog. It does not rebuild Master.db or apply metadata enrichment.

Import a local pack

Use Import .arcadepack when you already have a package file:

1. Select Import .arcadepack.
2. Choose the package file.
3. Review the detected publisher, content type, and validation result.
4. Install it, then complete any enable, rebuild, mapping, or publish step shown for that content type.

An imported package appears without being added to the bundled community catalog.

Read pack status

Common card states tell you the next step:

• Available — the pack can be installed.
• Installed — the package is present in Studio.
• Update available — a newer catalog version is available for review.
• Requires DB rebuild — metadata content is installed, but the working Master.db has not been rebuilt with it yet.

After a rebuild or configuration change, use Publish to send the resulting cabinet configuration to ArcadeServer.

Next: Getting started or Rules.