v2.3.1

Full Changelog: v2.3.0...v2.3.1

v2.3.0

Full Changelog: v2.2.0...v2.3.0

v2.2.0

The channel colours are the channel's own. Turning the water lines down, and turning them any
colour you like, both work now.

• Every state of a stretch has its own colour. Dug-but-unfloored and iced used to borrow the
  node colours from the Display tab, so the one button that said it coloured the channel moved the
  cyan and left the yellow and the green exactly as they were. Five colours, each labelled with the
  state it paints: Not dug, Dug, no ice, Iced, Bad run, Drain.
• An opacity setting for the water lines. It existed in the config file and was never on screen.
  The outline of a stretch follows it too instead of staying pinned at full strength, which is what
  made turning it down look like it did nothing.
• A Look tab on the Water page, between Setup and Cost, for how the channel is drawn: show it or
  not, opacity, the five colours, and the sources-and-plates proposal. Setup keeps what the network
  is made of. The colours were squeezed into Setup's right hand column, which is why there was room
  for one of them and not three.

Minecraft 26.1.2, and what 2.1.0 was supposed to be. 2.1.0 was tagged and never published: its
release failed on the 26.x builds and nothing was uploaded, so this is the first release since
2.0.0 and it carries both.

• A jar for 26.1.2, which is the first Minecraft that ships unobfuscated. Everything about
  building for it is different: there are no mappings to remap against any more, the build script
  uses the plugin that does not remap, and the game wants Java 25. Treat it as a beta. It
  compiles clean against the real 26.1.2 API, and unlike the 1.21 jars nobody has had it in a world
  yet.
• 26.2 is not here yet. It replaced the path a mod's own geometry takes to the screen, not just
  the names on it, and that is a rewrite rather than a port. It is next.
• Every jar now declares the one version it was compiled for again. Since 2.1.0 they all claimed
  >=1.21 <26.3, which let Fabric load a 1.21 jar on a version it was never built against.

v2.0.0

The water lines. A perimeter is only half the build: the other half is the channels that carry
what you throw in at a beacon to the digsort in the middle. The mod now plans them, and it has its
own page for it.

• A Water page, not a ninth tab. Nine tabs did not fit in one row, and the water lines are not
  a ninth setting of the same thing anyway: they are the perimeter seen from underneath. Press
  Water > at the end of the tab row and the whole screen turns the page, to Currents (the
  map you draw on), Setup (drain, shape, ice, how far a source carries, colours) and Cost
  (the whole bill). < Beacons brings you back.

• Its own map. Same view as the beacons map, so turning the page keeps you
  looking at the same piece of the world, but the nodes step back and the channels come forward:
  a run one block wide has no chance against a hundred coverage boxes at full strength. The
  beacons themselves are drawn bigger rather than dimmer, and every pyramid base is outlined,
  because those are what the channel has to fit between.

• The first time you open it, it says who this is for. This part of the mod assumes you are
  building a digsort, and anybody who is not deserves to be told so once rather than left to work
  it out from a screen full of jargon. Once, and then never again; there is a button on the tab to
  read it back.

• Excluded nodes get no channel. They are outside the perimeter: nobody throws shulkers in at
  one, so running ice out to them was digging for nothing. They are still drawn and still avoided,
  because their pyramid sits on the channel's own layer. On a real perimeter with nineteen of them
  that is 1,700 blocks of channel and nine shulkers of ice saved.

• Generate, and you get the whole network worked out from the plan: one spine per row, one
  trunk to the drain, every run a block clear of every pyramid base. The shape is a fishbone
  because what is being optimised is the trip and not the bill: every item travels its own exact
  Manhattan distance to the middle around a single corner, which nothing without diagonals beats.
  The tree shape is a button away for the perimeters where it wins.

• Draw your own. Turn Draw on and drag: runs are one block wide and snap to the axis, right
  click erases one whether Draw is on or not. What is on the map is what gets built, so a run you
  draw is not an override sitting on top of a calculation. That is also why Generate throws away
  what you drew, and asks first when there is anything to lose.

• You point at the drain. The middle of a grid is not a place: it is usually inside the centre
  node's own pyramid, and the sorter is wherever it actually got built. Aim at the block the water
  leaves by, open the screen, press the button.

• The count, in the Materials tab: channel, ice, buckets, pressure plates, junctions, and the
  shulkers of ice you actually have to mine, which is nine times the ice you place for packed and
  eighty one for blue. On a real hundred node perimeter that is the difference between a weekend
  and a fantasy, and it is better to know before the first block goes in.

• It tells you what is wrong rather than refusing. A run dug through a pyramid base is drawn in
  red, a node the channel never reaches gets a cross, and a network that does not join up says how
  many nodes are stranded. Your call, every time.

• The channels are drawn in the world at the layer they will be dug on, so you can stand in the
  hole and see where the next one goes. Toggle and colour on the Display tab.

• The water lines are saved with the plan and travel with it: opening a shared plan brings its
  channels, and editing them on a shared plan sends them up when you close the screen.

• The channel reads itself back out of the world. Every block of it is scanned as you get near,
  the same way the pyramids are, and drawn by what it is waiting for: cyan is still solid rock,
  yellow is dug out with no ice under it, green is floored and waiting for water, and a stretch
  with water in it stops being drawn at all. So the map empties as the thing gets built, and the
  line that is left is the work that is left. Blocks too far away to read are never counted as
  missing.

• Erasing takes out the stretch between crossings, not the whole eight hundred block spine.

• A node whose beacon already has water on it gets a ring on the currents map: that is the drop
  into the channel working, and it is the one part of it that can be checked from a distance.

• Sources and plates can be shown (Setup, off by default): a source at the head of each run and
  every few blocks after it, a stop where each run flows into another. Marked as a proposal
  everywhere it appears, because nothing about those positions has been checked against a channel
  that runs. Dig one stretch, see what the water really does, then trust them.

• The channel's Y is yours to set, not fixed at the bottom layer.

Not in this release, on purpose: the network does not export to a litematic yet, and the water
sources and pressure plates are counted rather than placed. Those are the parts a compiler cannot
check, and they wait until the shape has been dug in a real world.

Full Changelog: v1.3.0...v2.0.0

v1.3.0

• A node can be moved on its own. Some node always lands where a beacon cannot go, and until
  now the only answer was to nudge the whole grid and move the other two hundred with it. Turn
  Move on in the map, or hold alt, and drag that one node: everything else stays put. It snaps
  back onto its own row or column within four blocks, so a nudged node normally stays lined up and
  the water channel that serves its row stays straight; hold control to place it anywhere, or use
  the arrow keys for the last block or two. The map draws a line back to the cell it came from.
  Moved nodes travel to the rest of the team on a shared plan like any other change.
• A node moved off its row is left out of the water network rather than dragging that row's
  channel across the perimeter to reach it. It still gets its beacons and its pyramid.

Full Changelog: v1.2.0...v1.3.0

v1.2.0

Full Changelog: v1.1.1...v1.2.0

v1.1.1

Adds 1.21.11, and skips 1.21.9 and 1.21.10 on purpose.

Fabric API removed the world render events in 1.21.9, which is what an earlier version of
docs/PORT-1.21.9-PLUS.md called a wall that needed a mixin of our own. It did not: Fabric
redesigned the events and shipped them again in 0.137.0+1.21.10, so the mod hooks a supported
API here as it always has. 1.21.9 never got them back on its own branch and its Fabric API stopped
in December, and 1.21.10 has the events but predates the renames of 1.21.11, so it would cost its
own substitution table and its own copies of four files. Neither is worth carrying.

The largest part of the port was a rename nobody had flagged: ResourceLocation is called
Identifier in 1.21.11, which took the four networking payload classes with it.

• Line width survived. RenderSystem.lineWidth is gone in 1.21.11, because a line's width
  stopped being a global switch and became an attribute of each of its vertices, read by vanilla's
  own line shader. The wireframe now goes through that shader, so the setting still does what it
  says, and it is honoured on hardware that used to ignore it and draw everything one pixel wide.
• The mouse and key handlers take event objects, the widgets draw their contents rather than
  themselves, and a cycling button is told its starting value when it is built. All of it is the
  same code underneath: BeaconatorScreen is still one file, not one per version.
• No change to anything on 1.21 through 1.21.8, which build and test exactly as before.

Full Changelog: v1.1.0...v1.1.1

v1.1.0

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Full Changelog: https://github.com/CodeW4VE/Beaconator/commits/v1.0.0