Assume all commands below are prefixed with /automodpack, /amp is a shorthand for /automodpack. Only the bare /automodpack and /amp commands, which print the about text, need no permission. Everything else runs on the server console or in-game with operator permission level 3.
Publishing
generate- Publishes a new generation when the pack files or rules changed. A changedwaiting-music.oggis published too, even when the pack content is otherwise the same.generate notes <text...>- Publishes a generation with patch notes.generate preview [notes <text...>]- Builds the next generation and reports what would change, without publishing.generate if-content <content-token> [notes <text...>]- Publishes only while the content still matches the given token, so a scripted publish cannot race a manual change.generate history- Prints the newest hundred journal entries with sequence number, date, change summary, and patch notes.generate revert <seq>- Previews a rollback to journal sequence<seq>.generate revert <seq> confirm [notes <text...>]- Publishes the selected old state as a new generation.generate replace-notes [notes...]- Replaces the live generation's patch notes without publishing a new generation. Without inline notes, it reads and clearsautomodpack/host-modpack/patch-notes.md. Empty notes are refused.generate storage- Reports how many bytes the journal and the object store hold.generate export-http [--all] <directory>- Writes the URL-contract tree (head,journal,objects/<sha1>) as byte-for-byte copies of the hosted files, ready for any static HTTPS host. Objects Modrinth or CurseForge still serve themselves are left out;--allkeeps every object in the tree. The command reports what was exported, omitted, and unresolvable. Works in every connection mode and never deletes anything from the directory.generate storage collect confirm- Deletes the object bytes the current generation does not serve. It keeps every journal entry's policy document and any object another server process sharing the data root still pins. Older generations stay listed in the journal but can no longer be restored.
Patch notes for the next publish can also be written to automodpack/host-modpack/patch-notes.md; the file is read and cleared when a generation publishes or when generate replace-notes runs without inline notes. Publishing, rollbacks, and storage are explained in generations.
Hosting
host- Hosting status.host start,stop,restart- Control the modpack host.host activity- Shows modpack request activity since startup: totals per player, a bounded list of recent transfers including failed and disconnected ones, in-flight downloads, and the live upload throughput. Everything is in memory and resets when the server restarts.host fingerprint- Prints the certificate fingerprint of the modpack host. The fingerprint is the SHA-256 of the server's certificate, and the same value is logged at startup.host fingerprint dns <minecraft-hostname>- Prints a DNSSEC record that lets clients verify a self-signed certificate automatically.host fingerprint share <minecraft-address>- Prints a plain and a pinned copyable join address.host bootstrap pin <origin> [server-name]- Writesautomodpack/automodpack-bootstrap.exported.jsonwith a TLS pin, for distributing to clients. The optional server name adds a vanilla server list entry on the client.host bootstrap install <origin> [server-name]- Writes an install export with the published pack and a provisioning secret, using the advertised endpoint. This form needsadvertised-endpoint-hostandadvertised-endpoint-portset in the server config.host bootstrap install <origin> <endpoint> <connection-mode> [server-name]- The same export with an explicit endpoint and connection mode. Either form adds a vanilla server list entry when the optional server name is given.
Both bootstrap commands refuse to run when disable-internal-tls is on. When the endpoint is served by something external, the command fails and names the front-end's certificate as the one to pin instead. The pin export holds only public data: the origin and the fingerprint. The install export contains a provisioning secret, so treat it like a credential; anyone holding one can provision themselves onto your pack. See bootstrap files for how clients import them.
Configuration
config reload- Reloads the server config. When connection settings changed, it tells you to runhost restartto apply them.
Groups
groups- Lists every modpack group under its category, with published file counts and sizes.groups <group-id>- Shows one group's flags, dependencies, glob rules, and the files its published generation carries.