Mod Packs and modules

There are two ways to deal with more than one piece. They are different.

Mod Packs: several separate mods

A Mod Pack is a set of separate mods that install and roll back as one unit.

• Cyrus checks the whole set for conflicts first (duplicate commands, shared files, version clashes).
• Every open warning must be acknowledged before you can install.
• Mod Packs can include third-party mods by link and checksum. Cyrus only embeds mods it built itself.
• Not locked behind a plan.
• Uninstalling or rolling back removes the whole pack.

Modules: one big mod made of parts

For a large mod, you can split it into modules inside one mod. It stays one mod with one jar, but you can:

• edit or rebuild one module without touching the others,
• see each module's own revisions, tests and token spend,
• see which modules depend on which, and get an error if they do not fit together,
• export a module as a mod of its own.

Modules are not available yet. They are built and being finalised. This page will update when they are switched on.

Which should I use?

• Different authors or separate ideas: Mod Pack.
• One large idea you want to build in pieces: modules.