docs: bring the wiki up to 6.0.0
6.0.0 is out, so the API pages drop the "not published yet" banner and the
feature pages catch up with what shipped.
New ground:
- Fluid locks, including the two things that read as bugs without an
explanation: why one entry covers every bucket in the pack, and why
recipes nobody listed disappear. Plus the limits at pumps and pipes.
- Zones, with the shapes, the per-zone rules and what happens when two of
them overlap. Marked beta.
- Spawn rules: phase, conditions and extra biomes, the four limits around
worldgen and weather, and the editor dialog they are written in.
- The map background that changes as a player unlocks stages.
- item_tag as a ninth requirement, and why a tag entry settles on the
first deposit instead of staying open.
- The world chapter of the open scroll now covers zones, trades and fluids.
- /history zone, /history temporary and three debug subcommands.
Corrections, all of them things a reader would have tripped over:
- The dependency format was documented with a per-condition "type" field
that does not exist, and half the field names were wrong. Anyone copying
it got a stage that never opened. Both examples are fixed with it.
- Lock-Categories still claimed the attack lock indexes spawn entries.
That coupling is gone in 6.0.0; the paragraph keeps the lesson and drops
the false present tense.
- Category and requirement counts were two short.
Behaviour changes that show up silently get a box where the setting lives,
not only in the release notes: spawn locks no longer imply attack locks,
the trade action counts as locked in files written before it existed, and
a 6.0.0 client cannot join an older server.
docs: correct the API pages the trade locks made wrong
The addon page taught villager trades as the thing History Stages cannot
do, so an addon has to hook it. That stopped being true — merchant offers
are three built-in categories now — and an example that invites someone
to rebuild what ships is worse than no example. Moved it to quest
rewards, which we still know nothing about, and said plainly what
happened so the next reader is not left wondering.
The toolkit's note that only the dependency editor honours a tab's icon
and badge is out of date: the stage editor asks the tab as well, after
its own decorations, and badges stack instead of overwriting. That note
was a documented dead end that no longer exists. Added the segment bar
beside the on/off switch and its geometry, and the add-button hook, which
moved up from the dependency contract to the one both axes share.
The built-in count was already off by one before this — the fluids were
never listed — and is fifteen now.
docs: the two recipe-type registration windows
Neither adds anything, which is why they sit apart from the five extension points rather than in
their table: they describe recipe types History Stages already sees, so it stops guessing about
them. One says what a type looks like in the editor, the other that it can be gated per player.
The bus each is fired on is written down because getting it wrong fails silently -- a listener on
the wrong one is simply never called. The appearance event runs in client setup, since everything
it carries is UI; the per-player one in common setup, since it gates and stores.
The warning about only registering a station with its own menu is the one that costs an evening
otherwise: the editor offers the per-player lock, the entry lands in the stage file, and nothing
ever happens.
The count of api types naming the loader moves from nine to eleven. That number is the evidence
for the claim around it, so a stale one argues against itself.
docs: split Integrations & API and retire the one-page developer section
The page was two things under one title, and its own headings admitted it: a
table of mod integrations marked "For Modpack Developers", sitting in a sidebar
section called "For Mod Developers". The table is now its own page, Mod
Compatibility, where pack authors will look for it.
The developer half was largely a thinner copy of Stage State & Events, which
covers the same four events with the accessors, the every-path guarantee, the
creative-scroll gap and the mod-bus/game-bus trap the old page never mentioned.
Only two pieces were unique and they move there: the table of where the event
class lives before and after 6.0.0, and the Fabric Event<> listeners.
That leaves "For Mod Developers" with nothing in it, so it goes. The two
audiences it was trying to serve already have sections of their own.
docs: add an addon development section for the 6.0.0 API
Eight pages covering the five extension points, the editor toolkit and the
stage state API, with every example lifted from the demo addon rather than
written by hand, so the build breaks before an example can go stale.
Also fixes the existing developer API section, which named a class path that
6.0.0 moved and listed two of the four stage events. Both KubeJS variants are
now shown side by side, since the old path is still correct on 5.6.x and
Forge 1.20.