CurseforgeSync 1.0.0

Point your server at a CurseForge modpack and it keeps itself in sync every boot — before Forge scans for mods. Old versions deleted, new ones installed, client-only mods filtered out automatically.

What's in it

• Syncs your mods folder against a CurseForge modpack at every server start-up
• Installs new mods, deletes old versions, leaves hand-added jars alone
• Runs before Forge scans for mods, so changes apply in the same boot
• Skips client-only mods; sorts resource packs and shaders out of mods/
• Optional strict mode mirrors the pack exactly
• Dry-run mode and a built-in command-line tool for testing

Setup

1. Put the jar for your Minecraft version in mods/.
2. Start the server once. It writes config/curseforgesync.json.
3. Copy the number from the Project ID box on your pack's CurseForge page into modpackProjectId.
4. Restart.

{
  "modpackProjectId": 885460
}

To see what a sync would do without touching anything, every jar is also a CLI:

java -jar curseforgesync-1.19.2-1.0.0.jar --dir ./myserver --pack 885460 --dry-run --verbose

Downloads

Minecraft	Forge	Jar
1.7.10	10.13.4.1614	curseforgesync-1.7.10-1.0.0.jar
1.12.2	14.23.5.2860	curseforgesync-1.12.2-1.0.0.jar
1.16.5	36.2.42	curseforgesync-1.16.5-1.0.0.jar
1.19.2	43.5.2	curseforgesync-1.19.2-1.0.0.jar
1.20.6	50.2.10	curseforgesync-1.20.6-1.0.0.jar
1.21.11	61.2.0	curseforgesync-1.21.11-1.0.0.jar
26.1.2	64.1.0	curseforgesync-26.1.2-1.0.0.jar
26.2	65.1.1	curseforgesync-26.2-1.0.0.jar

Note

CurseforgeSync will not appear in your server's mod list, and that is expected. Forge deliberately skips mod-scanning any jar that provides a transformation service — which is exactly the mechanism that lets it run before mod loading.

Full documentation is in the README.