CurseForge Pack

Status: In Progress

Baseline target:

• Minecraft: 1.21.1
• Loader: NeoForge
• Distribution: CurseForge profile zip during private development

The canonical pre-review decision set now lives in Pack Baseline. This page remains the longer rationale and candidate list.

Pack Role

The pack exists to support the custom mod, not replace it.

It should provide:

• Quest framework
• Controller support
• Per-player loot
• Minimap and world map support
• Co-op player visibility on the minimap and world map
• Recipe browser
• Recipe and station visibility that works with custom crafting lines
• Travel utility
• Relic slot support if needed
• Better combat feel if it tests well
• Temporary structure scaffolding
• Server and client install simplicity

Candidate Mods

These are current candidates with source-backed availability on CurseForge for the target stack.

Mod	Role	Status
FTB Quests	Mainline and biome challenge quest book	Verified available
KubeJS	Script glue, recipe edits, loot tuning	Verified available
Lootr	Per-player structure loot	Verified available
Waystones	Midgame travel network	Verified available
Controlify	Controller-first support with DualSense features	Verified available
Xaero's Minimap	Minimap with waypoint support	Verified available
Xaero's World Map	Fullscreen world map and waypoint management	Verified available
Open Parties and Claims	Party integration and ally-player visibility on Xaero maps	Verified available
Xaero's Minimap and Waystones Compatibility	Waypoint sync helper if Waystones stays	Verified available
EMI	Recipe and item discovery support	Verified available
Curios API	Relic slot framework candidate	Verified available
Better Combat	Combat feel upgrade	Verified available, compatibility not yet tested
YUNG's Better Dungeons	Early dungeon scaffolding	Verified available, design fit not yet tested
YUNG's API	Required dependency for YUNG stack	Verified available
When Dungeons Arise	Large structure scaffolding	Verified available, spawn tuning required

Pack Rules

• The pack must not drown the custom progression in unrelated loot tiers
• Any structure mod used must be heavily tuned or gated
• Utility mods are allowed; progression mods that add their own full tech or fantasy tier ladders are not
• Server and client must stay version-locked
• Mount identity should stay in the custom mod layer, even if supporting libraries are used
• Controller-first usability is a pack-level requirement
• The chosen map stack must support waypoint use cleanly and must not undermine controller usability
• The chosen map stack must show co-op allies clearly, ideally as skin-face or player-head icons
• Recipe browsing and station-aware crafting flow are pack-level requirements

What Should Stay Out

Avoid these until there is a clear need:

• Large kitchen-sink content mods with competing weapon ladders
• Auto-magic or tech mods that replace the intended progression
• Multiple overlapping dungeon mods with no spawn controls
• Multiple map or teleport systems

Distribution Model

Private development and friends-only play:

• Share the client as a CurseForge exported profile zip
• Share the server as a prepared dedicated server zip for Crafty import

Public release can come later if the project stabilizes.

Current Repo Scaffold

The repo now includes an implementation scaffold for the private-development path:

• pack/modpack-lock.json tracks the current Phase 01 baseline expectations
• pack/scripts/sync_client_instance.py syncs the built custom mod jar and tracked config files into a local CurseForge instance
• pack/config/ftbquests/quests/** now carries the tracked FTB Quests scaffold for Greenwake, Frostweb, and Black Archive
• pack/kubejs/** now carries tracked advancement and tooltip glue for those early pack-side loops

This keeps the repo free of third-party jars while still giving the project a repeatable local client workflow.