For Mod Creators

This guide helps mod creators package their work for seamless import into FMMLoader26.

How FMMLoader Processes Mods

When a user imports your mod:

1. Extract - Archives are extracted to a staging area
2. Analyze - FMMLoader scans folder structure and file types
3. Classify - Mod type is detected (graphics, database, etc.)
4. Route - Files are mapped to the correct FM directories

The better your mod is structured, the smoother this process.

Recommended Structure

Graphics Packs

your-facepack/
├── faces/
│   ├── 12345.png      # Person ID as filename
│   ├── 67890.png
│   └── ...

your-logopack/
├── logos/
│   ├── club/
│   │   └── 123/       # Club ID folder
│   │       ├── logo.png
│   │       └── small_logo.png
│   └── comp/
│       └── 456/
│           └── logo.png

your-kitpack/
├── kits/
│   └── 123/           # Club ID folder
│       ├── home.png
│       ├── away.png
│       └── third.png

Database Mods

your-database-mod/
├── editor data/
│   ├── your-mod.fmf
│   └── ...

Or just distribute the .fmf file directly.

Skins

your-skin/
├── skin_name/
│   ├── skin.fmf
│   ├── skin_config.xml
│   └── ...

Naming Conventions

Person IDs (Faces)

Use FM's internal person ID as the filename:

• 12345.png - correct
• lionel_messi.png - incorrect (won't match)

Club/Competition IDs (Logos, Kits)

Use FM's internal unique IDs for folder names.

Finding IDs

Use the FM Editor or community-maintained ID databases to look up correct identifiers.

Graphics Classification

FMMLoader uses heuristics to classify graphics packs:

If confidence is low, users are prompted to confirm the type.

Tips for Reliable Detection

• Use standard folder names (faces, logos, kits)
• Keep one type per archive when possible
• For megapacks, include all subfolders at the root level

Archive Format

Recommended: .zip with standard compression

Avoid:

• .rar (limited support)
• Password-protected archives
• Nested archives (zip inside zip)

Folder Structure in Archive

# Good - contents at root
your-facepack.zip
└── faces/
    └── 12345.png

# Also good - single wrapper folder
your-facepack.zip
└── your-facepack/
    └── faces/
        └── 12345.png

# Avoid - deeply nested
your-facepack.zip
└── mods/
    └── fm26/
        └── graphics/
            └── your-facepack/
                └── faces/
                    └── 12345.png

Testing Your Mod

1. Create a test .zip of your mod
2. Import into FMMLoader via drag & drop
3. Verify:
   • Correct type detection
   • Files routed to expected folders
   • No errors in FMMLoader logs
4. Enable, Apply, and test in FM26

Distribution

When sharing your mod:

• Provide a direct .zip download when possible
• Note any FMMLoader-specific instructions if needed
• Include a README with mod description and version

FMMLoader doesn't require special manifest files - a well-structured folder is enough.