Server configuration

automodpack/server.conf in the server root directory. The file is created on the first start with defaults.

The file uses a small subset of HOCON: comments (#), key: value options, inline lists, and braced nesting.

Editing the file

Apply changes with /automodpack config reload or a restart. When the reload changes connection settings, run /automodpack host restart to apply them.

General

Groups

The modpack section holds the pack: modpack.name is the display name players see, and the categories follow it, each mapping category name, then group id, then the declaration. The factory config contains one category, General, holding a single group main, which is required and selected by default. Extra groups become optional parts that players pick in the in-game "Group Selection" screen, listed under their categories. Group content comes from two sources: the directory automodpack/host-modpack/<id>/ is included in full, and from-server pulls in files from the server root. The full picture is in building the modpack.

Both keys are identities, so treat them as permanent. The group id is the slug used by requires and breaks-with, by players' saved selections, and as the folder name under automodpack/host-modpack/<id>/; renaming it strands saved selections, breaks references from other groups, and requires renaming the folder. Renaming a category strands players' saved category choices. display-name is the always-safe rename, so keep anything volatile (versions, dates) out of ids and category names. A group with a blank display-name shows its id instead.

Categories

Category names are player-facing display strings, not ids: they render verbatim as the section headers of the Group Selection screen. A name must be non-blank, carry no leading or trailing whitespace or control characters, and be at most 64 characters long, and names must be unique case-insensitively. An empty category or a group id declared twice is a validation error that fails /automodpack generate with the reasons in the log. Categories and their groups appear in the client in declared order, not alphabetically.

Rule lists

Each group carries three rule lists, relative to the server root.

Globbing wildcards

A leading / is allowed and ignored. Rules are otherwise relative to the server root, with one exception: a rule may name its own group's directory under automodpack/host-modpack/<id>/, which is useful for excluding part of it.

• * matches within a single directory, for example mods/*.jar.
• ** matches recursively, for example kubejs/**.
• ! negates a rule inside its own list. A path matches a list when a positive rule matches it and no ! rule does.

Where the negation applies depends on the list it sits in. Inside from-server it skips a path from the synced set only, and the group directory may still provide it. exclude keeps a path from reaching clients entirely, so prefer it for exclusions and reach for a from-server negation only when the group-directory copy should still ship.

Read more about glob syntax on the Globbing Wikipedia article.

Group fields

Platforms

A platform is any short lowercase name. Clients detect windows, linux, and macos automatically and preselect the matching entry in the platform dropdown of the Group Selection screen. Any other name a group declares, for example steamdeck, is listed there too, so a player on a detected desktop OS can still opt into it. An empty compatible-platforms means every platform.

When a client cannot detect a platform at all, groups without compatible-platforms behave as usual and platform-restricted groups stay unavailable until the player picks a platform.

Network and hosting

Setting modpack-host to false turns off every built-in listener while clients keep receiving connection information. AutoModpack cannot validate external routing from the Minecraft server process, so a reverse proxy setup is your responsibility; the proxies page covers known-good setups.

Un-modded clients

With require-modpack off, players who join without AutoModpack stay in the game, and modded clients are asked whether to sync the pack when they connect.