Compatibility & load order
A long mod list is a craft project in its own right. This page is about peaceful cohabitation between Create, Aeronautics, and whatever else you love – not about chasing every mod on the internet in one day.
Dependencies you really must respect
Create: Aeronautics expects the Create mod in the line and version the project page names. Always read the latest note on Modrinth and on Create’s own page before you assume a range. The exact dependency names change; the habit of checking does not. Other libraries (a config API, a math lib, a networking helper) are normal – install them because the mod asks, not “because a forum list said to.”
Load order, in simple terms
Most modern loaders do the heavy work for you. You add mods; the system resolves a graph. You step in when two mods touch the same part of the game – world gen, a shared key bind, a conflicting mixin – and the log says which pair fought. The fix is not always “move one jar above another”; sometimes it is “pick one of these two features” or “wait for a patch.”
If your launcher has a mod list file (often exportable as text), save a copy of a working set before you add big mods. That snapshot is the fastest way to return to a known-good state after a long evening of “just one more.”
Growing a pack on purpose
Add mods in small batches – a few at a time, a short play session, then a note: “stable with X, not yet with Y.” World-gen mods, minimaps, and full UI overhauls are especially worth testing alone because their failures are loud and hard to tease apart from craft physics.
On a server, match client and server files to the line. A single “harmless” client mod missing on the server, or a tiny version skew, is enough for ghost blocks and kicks. The Server page has a few habits that keep everyone aligned without turning your group chat into a spreadsheet war.