Warium-NeoForge-1.21.1/docs/agent-handoff.md

Agent Handoff

Use this file when a task spans multiple sessions, has unresolved follow-up work, or changes release behavior.

Current State

Private NeoForge 21.1.225 port scaffold is implemented. It generates registry stubs and extracted resources from the verified Warium 1.2.7 jar in CI, but original behavior systems still need manual porting from the decompiled output.

Changes Made

• Bootstrapped repository from codex-agent-repository-kit.
• Added NeoForge/Gradle Java 21 project files.
• Added scripts for Warium jar download, SHA1 verification, inventory extraction, source/resource generation, decompilation, runtime dependency download, and registry parity checks.
• Added Gitea build workflow with artifact upload, private package publishing, and server smoke-test step.

Verification

Check	Result
python tools/generate_port_sources.py	Passed locally with bundled Python
python tools/registry_parity.py	Passed locally: 448 blocks, 326 standalone items
python tools/prepare_runtime_mods.py	Passed locally for GeckoLib and RPL
./gradlew --no-daemon build	Pending Gitea runner; local Java is not installed
./gradlew --no-daemon runData	Pending Gitea runner; local Java is not installed

Open Questions

• Warium license conflict remains unresolved: Modrinth shows ARR, jar metadata shows AFL-3.0.
• Real NeoForge 1.21.1 WariumAPI/WariumVS artifacts were not found during planning; the repo currently declares compatibility shim mod metadata.

Next Steps

• Push to MrSphay/Warium-NeoForge-1.21.1 and poll Gitea Actions.
• Fix any Gradle/NeoForge compile errors found by the runner.
• Port original MCreator behavior systems from build/decompiled/warium-1.2.7.
• Replace WariumAPI/WariumVS shims with real dependencies when available.

Risks

• Current jar is not a complete gameplay port; it preserves many registry/resource IDs but not the original machine, weapon, projectile, AI, GUI, networking, or nuclear behavior.
• Public release must wait for rights clearance.