Closed AerikAwesome closed 11 months ago
I am getting the exact same issue
Identified the cause: https://www.curseforge.com/minecraft/mc-mods/ironchests/files/4670973
New modloader type is 'NeoForge'
Think that means the type needs to be added to this if that is the case.
Indeed.
I tried adding affected mods to CF_EXCLUDE_MODS, but this did not work.
Might have something to do with this that was posted in the Curseforge discord today.
https://discord.com/channels/428228256236306434/525372338653626389/1135119605141082232
I don't think so, this seems to be https://neoforged.net/news/theproject/
Thanks @AerikAwesome for identifying that! I'll get that into the enum shortly. I only would have hardcoded things defined by the API spec, so I'll take a quick look at what's going on there.
FYI, their API spec does not include that new modloader type. Easy to add, but how annoying 😒
Image build is running https://github.com/itzg/docker-minecraft-server/actions/runs/5706703596
Describe the problem
When trying to update modpack https://www.curseforge.com/minecraft/modpacks/statech-industry from v1.1.2 to v.1.1.3, container fails with the following error:
I suspect one of the included (unsure which) mods has a "latestFileIndex" with a modloader outside the normal range.
Container definition
Container logs