Is AutoModpack server-side or client-side?
Both. It needs to be installed on the server and on every client.
How do I add client-only mods to the pack?
Put them in automodpack/host-modpack/main/mods/ on the server. They ship to clients without the server loading them. The full guide is building the modpack.
How do I keep a server mod from reaching clients?
Add it to exclude in the server config, for example mods/the-server-mod.jar. Client-only mods go the other way, into automodpack/host-modpack/main/mods/. The recipes, including a complete server/client split, are in which files reach clients.
How do I restrict access to my modpack?
Keep validate-secrets on in the server config, set online-mode=true in server.properties, and use the whitelist or bans as usual. Downloads then require a secret issued through the Minecraft login. See security.
Does it work on a LAN or a single-player world opened to others?
Yes. Generate the pack with /automodpack generate and start the host with /automodpack host start.
Does it work with single-player worlds shared through Essential, World Host, or e4mc?
Yes, since AutoModpack version 5, they should work just fine.
Can I use extra mods alongside the pack?
Yes. Put any mod in the instance's standard mods folder as usual.
How do I delete files from the pack?
Delete them from the server, or add them to exclude list. Both are described in building the modpack. Clients remove their copy on the next update when the ownership ledger proves the file was removed.
Can the pack delete arbitrary files from my computer?
The pack can only remove files it can prove it delivered: the path and the exact hash and size must match the pack's ownership ledger, and the file's bytes are kept on your side before deletion. Files you created or changed survive, and saves/, screenshots/, logs/, and automodpack/ are always off limits. The details are in client updates.
Do I have to open a port on my router?
Usually not. The default HOLEPUNCH mode carries the modpack connection through the Minecraft login, so it needs nothing beyond the already open Minecraft port. The modes and their port behavior are in hosting.
What happens when the server updates AutoModpack itself?
Clients follow the version the server runs: they update or downgrade through Modrinth to match it. See AutoModpack's own updates.
Why does the pack live under host-modpack/main/?
Each group has a directory under automodpack/host-modpack/<group>/, and main is the default group. File rules live on each group in the modpack section of the server config.
What are groups?
Optional parts of a modpack, like a shader bundle or a platform-specific mod set. The server admin declares them under a category in the modpack section of the server config; players pick the ones they want in the in-game "Group Selection" screen, and the choice sticks across updates. They are covered in building the modpack.
Is my launcher supported?
All standard launchers should just work, for wider compatibility check the launcher list.
Does AutoModpack update my mods to their latest versions?
AutoModpack keeps clients identical to the server, and updating the server's mods stays your job.
I found a bug. What should I do?
Report it on the issue tracker. Include the Minecraft version, loader, and the log from the side that misbehaved.
I found a security vulnerability. What should I do?
Report it privately to the author on Discord.