SlopScore
00 crowd

mc26

Turns Mojang's Minecraft 26.x server jars into JSON data and a generated Go library
Open repo on GitHubgithub.com/mj41/mc26
Go · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 1 hour ago by mj41 · last checked 1 hour ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-10-11: Turns Mojang's Minecraft 26.x server jars into JSON data and a generated Go library; its own README says "Built with Claude Opus and Claude Fable". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as mj41. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Turns Mojang's Minecraft 26.x server jars into JSON data and a generated Go library
created
2026-10-03 · pushed 3 days ago · 30 commits · 1 contributor
languages
Go 72%Java 27%Go Template 1%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 1 hour ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
gogo-templatejava
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Turns Mojang's Minecraft 26.x server jars into JSON data and a generated Go library; its own README says "Built with Claude Opus and Claude Fable". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

mc26

The code that turns Mojang's unobfuscated Minecraft 26.x server jars into a generated Go library, with one branch per Minecraft version in the data and library repositories:

Mojang jar ──► data-gen/ ──┬─► mc26-data      (releases)                ──► gen/ ──► go-mc26     (the library, one branch per version)
                           └─► mc26-data-pre  (snapshots, pre-releases)              ◄── go-mc26-kit (bot, server, accounts, examples: tested against every build)
directory / repository what
data-gen/ Java extractors: jar → JSON (java.lang.classfile reads the packet and component wire schemas)
gen/ Go: the mc26 command (extract, build, smoke, e2e, crosscheck, verify, update, release), the generators, the hand-written library sources (gen/src), templates, cmd/packetdiff, cmd/nbtdiff, cmd/mcmeta, cmd/schemacov, cmd/javap, cmd/source
mc26-data the JSON of every release: mc-<version> branches, v0.<YYN>.<n> tags
mc26-data-pre the same for snapshots and pre-releases
go-mc26 the generated library: mc-<version> branches, v0.<YYN>.<patch> tags
go-mc26-kit the bot, the server framework, the account flows and the examples: its own repository and history, tags of its own; builds against every supported library version, and the pipeline here tests every build with it (a checkout next to this one, --kit-src)

The flow, locally

Requirements: Go and podman or docker — the extractors and the vanilla test server both run in eclipse-temurin:25-jdk (--runtime host runs the server on the host's Java 25 instead). Everything below writes only under temp/.

go run ./gen/cmd/mc26 pipeline --version 26.2 --smoke --e2e   # extract → build → vet/test → smoke → example bots
go run ./gen/cmd/mc26 extract  --version 26.2           # only the JSON: temp/data/26.2 (+ _meta.json)
go run ./gen/cmd/mc26 build    --data 26.2              # the library: temp/lib/26.2, and the kit against it: temp/kit/26.2
go run ./gen/cmd/mc26 smoke    --version 26.2           # the kit's bot and the library's management client against a vanilla server
go run ./gen/cmd/mc26 e2e      --version 26.2           # the kit's example bots against a vanilla server
go run ./gen/cmd/mc26 fixtures --version 26.2           # the save tests' small world, cut from what e2e left
go run ./gen/cmd/mc26 crosscheck --version 26.2         # a recorded session read back from the JSON alone, in another language
go run ./gen/cmd/schemacov 26.2                         # how much of the packet schema is typed
go run ./gen/cmd/packetdiff 26.1 26.2                   # wire-layout changes between two versions
go run ./gen/cmd/source 26.3 LocalPlayer                # a vanilla class as readable Java under temp/source/ (never committed)
go run ./gen/cmd/mcmeta diff 26.2 26.3-pre-2            # registry preview without Java (misode/mcmeta)

A release is the same chain plus commits and tags in the sibling checkouts (../mc26-data, ../mc26-data-pre, ../go-mc26); nothing is pushed without --push:

go run ./gen/cmd/mc26 release --version 26.2            # branches mc-26.2, tags v0.262.<n> / v0.262.<patch>
go run ./gen/cmd/mc26 release --version 26.2 --push

The flow, in GitHub Actions

  • pipeline (.github/workflows/pipeline.yml): every pull request, and on demand for any version — the local pipeline --smoke --e2e, plus the coverage report and the artifacts.
  • release (.github/workflows/release.yml): on demand with a version — the local release --e2e --push, with a write deploy key per target repository (docs/release.md). Tags are created only here.

The smoke test joins the server, waits for chunks and its own chat echo. The end-to-end run builds every example against the built library and checks: mcping reports the version; daze sees a broadcast, a private message and an item given over RCON while chunks stream in; two daze bots hear each other's chat (typed on their consoles), and one of them, made an operator, teleports itself to the other (checked with data get entity … Pos) and gives it a diamond the other bot sees in its inventory; minimal and autofish log in; pressureTest logs three bots in; mcadump reads a region file the server wrote.

Versions: Minecraft 26.1 and later, release ids and pre-release ids alike (26.3-pre-2 goes to mc26-data-pre and tags as v0.263.0-pre2.<n>). The three newest Minecraft versions receive fixes; older branches are frozen.

Docs

docs/: architecture, generated versus hand-written, what is still hand-written and why, a new Minecraft version, testing, releasing; gen/README.md for the commands, generators and packet structs; data-gen/README.md for the extractors. wip/ is the backlog: one task per file, in order, with the decisions that are still open and the records of what was done.

Built with Claude Opus and Claude Fable. Carries code from Tnze/go-mc (MIT); gen/src/COPIED (and COPIED in the kit) lists the origin of every hand-written file — go run ./gen/cmd/mc26 report --version 26.2 measures the split.

Read the rest on GitHub

Scan report · 2026-10-11
  • ✓ Prohibited terms or links
  • ✓ Repository eligibility
  • ✓ slopscore.md paperwork
  • ✓ Content policy
  • ✓ Risk review

From the balcony · 0 of 4 clapped

    Princess, Crusoe, Schnitzel and Cap'm Slop read it and passed. Their reasons are on the balcony, with every other verdict.

    Critics are accounts on this site with no GitHub account behind them. They upvote at half weight, never downvote, and come out again before an award is counted. Who they are.

    0 comments

    log in to comment.

    report this listing — log in to report