docs(roadmap): track post-migration mod follow-ups
Two follow-ups from the packwiz→04-mods migration: curate cosmetic-client entries in mods-sides.json, and rework the landing join flow off the dead packwiz pack.toml URL onto the HeliosLauncher/distribution.json flow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
14
CLAUDE.md
14
CLAUDE.md
@@ -125,6 +125,20 @@ mirrored at apex `/launcher/`. Per guest:
|
||||
|
||||
## Open / Pending Work
|
||||
|
||||
### Roadmap — mod migration follow-ups (post packwiz→04-mods)
|
||||
- [ ] **Curate `mods-sides.json` cosmetic-client mods.** tomllib auto-flagged 11
|
||||
hard client-only mods; the other 65 default `both`, including client-cosmetic
|
||||
ones (BetterF3, entityculling, MouseTweaks, ponderjs, fancymenu, drippy, melody,
|
||||
welcomescreen, Searchables, JustEnoughResources, TravelersTitles, yeetus…) that
|
||||
load harmlessly on the server but waste RAM. Hand-edit them to `client` so
|
||||
`sync-server-mods.sh` drops them from `./server-mods`. (Also review `appleskin`,
|
||||
flagged `client` — flip to `both` if server-side food data wanted.)
|
||||
- [ ] **Rework the landing join flow off packwiz.** `pack.` vhost is gone;
|
||||
`site.ts packwizUrl` is a dead-URL placeholder (kept w/ TODO so the build
|
||||
passes) and `i18n/ui.ts` join steps (all 3 langs) still tell guests to import
|
||||
`pack.toml`. Redesign step 3 around the HeliosLauncher/`distribution.json`
|
||||
install flow. See `plan/04-mods.md` + `site.ts` TODO.
|
||||
|
||||
- [ ] **Mod shortlist** for the kitchen-sink pack: Performance (Embeddium,
|
||||
FerriteCore, ModernFix), Tech (Mekanism, Create, IE, AE2), Magic (Ars Nouveau,
|
||||
Botania, Iron's Spells), Storage (Sophisticated, Functional), Exploration
|
||||
|
||||
Reference in New Issue
Block a user