← ClaudeAtlas

modportlisted

Port a Minecraft Java mod (any version, jar or source) to the b1.7.3_rewrite mod loader as one .bmod that runs on client and server, extending the loader and SDK where the mod needs something new. Use when the user says /modport, /port, "port this mod", or hands over a mod jar to bring to beta 1.7.3. Also use to audit a finished port against its source.
qad3n/b1.7.3-modport · ★ 0 · AI & Automation · score 62
Install: claude install-skill qad3n/b1.7.3-modport
# Port a mod to the b1.7.3_rewrite loader Java mods cannot run. A port is a Rust rewrite (wasm guest, `b173_api` SDK, API 2.0, ABI 4) that uses the decompiled mod as its spec. Deconstruct the mod into content, mechanics and data, then rewrite it as a native loader mod: one file in both client and server `mods/`, everything through the loader's registries. The Java is a source of facts, not a structure to copy. This file is the whole map. Follow "The run" from step 1 to step 8 without stopping to ask, except where "When to ask" says so. ## Operating rules - **Tools first, files second.** Never read loader design or progress docs, guides or whole SDK files to orient. `T/api.sh find <word>` answers "is there an API for this" in one call. Open a file only at the line a tool printed. - **Work from the ledger.** `PORT_STATUS.md` holds one row per piece of content, behavior and data. The run is: pick the first open row, build it, check it, tick it. Never work on something that has no row; add the row first. - **Read the source once per row.** Open a Java class only for the rule or number its row needs, read that method, close it. Never read a class top to bottom "to understand the mod", never re-read one already mined. - **Narrow checks.** After a change run the port build and the one console check that covers it. Run the full gates (step 7) once, at the end. Never re-run a check that passed on unchanged code. - **Park bugs.** A bug that is not in the row being built goe