Multiplayer & servers
Flying together is a highlight of big tech mods, but only when everyone is on the same set of version numbers and a shared sense of performance limits. This page is for players, not for datacenter manuals – plain rules that keep the session fun.
Match the whole line
Paste your game version, loader, Create version, and Aeronautics version into a pinned message or a shared doc. When someone new joins, they should be able to copy that list into their launcher without guesswork. “Latest” is not a number; a host cannot debug a mystery pack from voice chat.
When a mod updates, move together. If one person rushes a major bump while the rest stay behind, the group will spend the evening in Troubleshooting mode instead of flying. A scheduled update night, with backups first, is cheaper than a surprise patch on a workday evening.
Whoever hosts, runs the list
Whoever provides the world file or the rental server is the source of truth for mod updates and world backups. Everyone else is a guest with responsibilities: ask before you add a client-only mod, and never drop a server-side mod into a shared world without a dry run. The host is not a sysadmin; they are a friend who should not have to rebuild the map because someone’s “helpful” extra mod corrupted chunks.
Keep performance human
Every contraption, farm, and flying assembly shares the world’s time budget. If TPS is bad, schedule simple machines off-hours, build smaller, or move heavy automation to a less crowded area. A server is a shared living room, not a private benchmark. Talk early about what “enough” looks like, and agree to spread builds so everyone still gets smooth input.
For load-order and mod-mix context, the Compatibility page lists common companions and what they tend to break. The Community page points to the official project presence where people gather for up-to-the-minute support.