FMMLoader can read an optional manifest.json file to get mod metadata. If not present, FMMLoader will prompt users to enter details manually or auto-detect what it can.

Basic Structure

{
  "name": "My Facepack",
  "version": "1.0.0",
  "author": "Your Name",
  "description": "High-quality player faces for the Premier League",
  "type": "graphics",
  "subtype": "faces"
}

Fields

Field	Required	Description
`name`	Yes	Display name for the mod
`version`	No	Semantic version (e.g., `1.0.0`)
`author`	No	Creator name or team
`description`	No	Brief description of what the mod contains
`type`	No	Mod category (see below)
`subtype`	No	More specific classification

Type Values

`type: "graphics"`

For visual assets. Use subtype to specify:

Subtype	Description
`faces`	Player/staff facepacks
`logos`	Club, competition, nation logos
`kits`	Team uniforms
`mixed`	Megapacks with multiple types

{
  "name": "DF11 Faces 2026",
  "type": "graphics",
  "subtype": "faces"
}

`type: "database"`

For editor data files (.fmf):

{
  "name": "Updated Transfers 2026",
  "type": "database",
  "description": "January transfer window updates"
}

`type: "skin"`

For UI themes:

{
  "name": "Dark Mode Skin",
  "type": "skin"
}

`type: "other"`

For anything else (scripts, configs, etc.):

{
  "name": "Custom Match Engine Tweaks",
  "type": "other"
}

Extended Example

{
  "name": "Complete Graphics Megapack",
  "version": "2026.1.0",
  "author": "FM Community Team",
  "description": "Faces, logos, and kits for all playable leagues",
  "type": "graphics",
  "subtype": "mixed",
  "website": "https://example.com/megapack",
  "license": "Free for personal use"
}

File Location

Place manifest.json at the root of your mod folder or archive:

my-facepack.zip
├── manifest.json
└── faces/
    ├── 12345.png
    └── ...

Or in a wrapper folder:

my-facepack.zip
└── my-facepack/
    ├── manifest.json
    └── faces/
        └── ...

Without a Manifest

If you don't include a manifest:

FMMLoader analyzes the folder structure
Auto-detects type when possible (e.g., faces/ folder → facepack)
Prompts user for missing metadata via the Mod Metadata Dialog

Including a manifest improves the user experience but is not required.

Manifest Format