CurseForge modpack servers fail to install or start

Open
#182 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, java, typescript
Domain
backend

Research direction

Find where Isopod sets CF_EXCLUDE_MODS and JVM_OPTS for new servers, likely in the TypeScript backend that builds instance env. Inspect the Docker image's CurseForge installer that reads .cache/curseforge/cache-index.json and stops on missing slugs. Change exclusion to project IDs, skip --add-opens on Java 8, and tolerate truncated cache. Done when acceptance criteria pass.

Written by the indexing model from the issue text.

Description

Bug

Every CurseForge modpack server fails to install, and any modpack on Minecraft 1.16 or older also fails to start.

Causes

  1. Isopod sets CF_EXCLUDE_MODS to a list of client-only mods by slug. 12 of the 54 slugs don't exist on CurseForge, and the image's installer stops at the first slug it can't find: No mods found with slug=.... When it stops, it can leave .cache/curseforge/cache-index.json cut short, which fails the next attempt as well.
  2. Isopod sets JVM_OPTS=--add-opens ... on new servers. Java 8 doesn't know that option, so servers on the java8 image stop with Unrecognized option: --add-opens.

Acceptance Criteria

  • New CurseForge modpack servers exclude client-only mods by project ID, so a renamed or deleted slug can't stop an install.
  • Servers on Java 8 don't get --add-opens.
  • Existing servers with the bad slugs or the Java 8 option work on their next start, with no manual edits.
  • A cut-off helper cache file doesn't fail an install.
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.