Modpack Build

The pack-side gap is no longer mod choice. It is authoring the missing scripts, datapack resources, and export checks.

Workspace Snapshot

Current instance state:

Item	Verified fact
version and loader	the current instance is 1.20.1 on Forge
KubeJS roots	both kubejs/ and local/kubejs/ exist, but the main authored content is under kubejs/
current script counts	startup_scripts = 2, client_scripts = 1, and kubejs/server_scripts is not present yet
current data resource count	kubejs/data currently contains 0 files
event stack	mods/ already contains EventJS-1.20.1-1.4.0.jar, but there is still no project use of NativeEvents, ServerEvents, or StartupEvents in local scripts
TaCZ stack	the instance already ships tacz, tacz-tweaks, tacz_turrets, taczaddon, taczammoquery, and taczjs

The main pack-side gap is not "choose more mods." It is turning server_scripts and datapack resources into real project content.

Pack-side boundaries

Pack-side work owns only the following layers:

Layer	Owns	Does not own
mod stack	dependency choice and available systems	ruin runtime rules
config layer	default behavior, feel, and policy	long-term ruin records
scripts and datapacks	tags, loot, progression glue, and server event entry points	formal runtime services
export and QA	confirming the instance starts, reloads, and plays correctly	design acceptance

KubeJS And Datapack Boundaries

The bundled kubejs/README.txt already defines the directory roles, and the first slice should follow them:

Directory	Runtime boundary	Current state
kubejs/startup_scripts	loads once during startup, suitable for startup-time registration	contains 2 files, but not formal site logic yet
kubejs/server_scripts	reloads with server resources, suitable for server events, loot, tags, and recipe changes	directory not present yet
kubejs/data	acts as a datapack directory for loot_tables, tags, functions, and other server resources	currently empty
kubejs/client_scripts	reloads with client resources, suitable for tooltips and client hints	currently holds 1 example-level script

This boundary determines the first-slice landing order:

1. Content that should live as world resources goes into kubejs/data first.
2. Server-side glue that should iterate through /reload goes into kubejs/server_scripts.
3. Client hints can exist only after server-side data already exists. They are not the primary logic layer.

TaCZ setup and editing rules

The project has already settled on TaCZ. That part is no longer open.

Path or mod	Verified fact	Conclusion
mods/tacz-1.20.1-1.1.7-hotfix2.jar	TaCZ is already installed	the first slice should build directly on it
mods/tacz-tweaks-2.13.1-all.jar, mods/tacz_turrets-1.1.2-all.jar, mods/taczaddon-1.20.1-1.1.7.jar, mods/taczammoquery-1.20.1-1.0.0.jar, mods/taczjs-forge-1.4.0+mc1.20.1.jar	the current instance already carries several TaCZ extensions	the current gun content is already broad enough; the first slice should narrow scope instead of adding more layers
tacz/tacz-pre.toml	DefaultPackDebug = false	editing the default pack directly should not be treated as the normal way to work
tacz/tacz_default_gun/gunpack.meta.json	the live default gun pack namespace is tacz	the project's own gun packs should not continue under that namespace

The resulting rules are fixed:

1. The first slice keeps using TaCZ instead of splitting into separate weapon systems.
2. Normal long-term work should prefer a project-owned gun pack over direct edits to tacz_default_gun.
3. With DefaultPackDebug = false, direct edits to the default pack stay temporary experiments.

First-Slice Gaps

Given the current instance state, the first slice is still missing the following pack-side content:

Gap	Current state	First landing area
host and classification tags	kubejs/data has no project data yet	kubejs/data/lost_civilization/tags/...
loot and progression resources	no formal ruin resources exist yet	loot_tables, advancements, and any required functions
server-side glue	kubejs/server_scripts does not exist yet	activation submission, loot adjustment, progression steps, and server event bridges
local smoke test	no stable checklist exists yet	startup, /reload, instance entry, and one recovery completion

That makes the first pack-side route short:

1. Lock the TaCZ editing method and namespace policy.
2. Add the minimum datapack resources.
3. Add the minimum server_scripts glue.
4. Only then expand client hints, additional weapon content, or heavier presentation.