Pack metadata

pack.json at the archive root describes the file. The same metadata model is used for packs, games, templates, and account backups.

Field	Type	Default	Meaning
type	string	"pack"	pack, game, template, or accounts
name	string	""	Display name
description	string	""	Human-readable description
author	string	""	Author or organization
version	string	""	Content version label
dependencies	string array	[]	Dependency identifiers
fileVersion	integer	0	Archive format version

pack.json

{
  "type": "pack",
  "name": "My tabletop pack",
  "description": "Cards and pieces for our weekly game",
  "author": "Example author",
  "version": "1.0.0",
  "dependencies": [],
  "fileVersion": 0
}

The version label describes your content; it does not replace the archive format version or network protocol version. Keep fileVersion at the supported format value when authoring a pack.

There is no user-selected id field. The pack identifier comes from the archive’s bytes. Changing content or repacking the ZIP changes that identity. See identifiers and references.

Dependencies are metadata, not a package-manager command: distribute required packs and ensure they are enabled in the world. Use translations for localized item names; metadata describes the archive as a whole.