AutoModpack syncs the server's modpack to every player automatically. The server publishes a pack; clients verify it, download it, and follow every change you publish. Mods, configs, resource packs, and shader packs all travel the same way.

Start with the [quick start](docs/quick-start). It covers installing the mod on a server and connecting with a client. Players who just want to play read [For players](docs/players): what they see, from verification through the first install to groups and the Modpacks screen, and every per-pack action.

From there:

- [Building the modpack](docs/pack-content) explains what gets synced and where to put your own content, and [how a pack is built](docs/how-it-works/pack-pipeline) follows one `generate` run from input to download.
- [Groups](docs/groups) explains how to split the pack into parts players pick in-game, so one server offers different setups to different players.
- [Server configuration](docs/configuration/server-config) and [client configuration](docs/configuration/client-config) document every setting.
- [Security](docs/security) explains how clients know a server is who it claims to be, and everything the mod runs and contacts.
- [Safety nets](docs/how-it-works/safety-nets) lists every recovery path: server-side rollbacks, crash-safe updates, the instance timeline, and what to back up, plus the local storage maintenance tools: timeline, clean, verify, and repair.
- [Troubleshooting](docs/troubleshooting) decodes the disconnect reasons, the error screen, and the restart reasons.
- [Upgrading from v4](docs/migrating-from-v4) explains what the old config becomes and what starts fresh.
- [The big picture](docs/how-it-works/concepts) walks the whole system in ten steps.

Questions or problems? Join the [Discord server](https://discord.gg/hS6aMyeA9P). If the project saves you time, you can support its development on [Ko-fi](https://ko-fi.com/skidam).