Modpacks

Yes, you can include these mods. Here is how to do it cleanly.

Permission

Every MyCelium mod and the Mycel library are MIT licensed, so you may include them in any modpack, public or private, without asking. A link back to the mod's page is appreciated but not required. Just keep the LICENSE habit: do not relicense other people's work as your own.

What to ship

• The loader your pack uses, with the matching mod jars. Fabric packs need Fabric API too; Forge and NeoForge packs just need their mod jar.
• Mycel, same version the mods were built against (currently 1.1.0). One copy covers every MyCelium mod in the pack.
• The mod jars themselves, all for the same Minecraft version. Never mix a 26.3 mod jar with another game version and hope for the best.

Client and server files

MyCelium mods are server side, so the same jars go in both the client and the server pack. There is no client-only or server-only split to maintain. Server-only packs (no client distribution at all) work fine and still cover vanilla clients.

Config files

You do not have to ship config files. If config/instantxp.json or config/autoblockrefiller.json is missing, the mod generates it with defaults on first launch. If you want a non-default setup out of the box (say a bigger XP radius), ship your edited file and it will be respected. New settings added by later updates merge in with their defaults, so old shipped configs keep working.

Keeping the pack updated

Pin all three together when updating: the game version, the loader, Mycel, and the mods. Check the changelog for which versions go together. Updating one mod jar while leaving an ancient Mycel jar in place is the classic way to earn a crash on startup.