verify pass 2: resolve markers via ViaBackwards/ViaRewind/ViaLegacy

Closed most remaining UNCONFIRMED items + caught corrections: 1.7 data[]=proto5,
1.8 multi-block nibble order (z/x), stance y+1.62, 1.15 wolf idx18=begging,
1.18 below-zero sections NOT stripped (claim was wrong), CONTAINER_SLOT_STATE
1.20.3, + pinned first-appeared versions (report details/server links=1.21,
fluidCount=26.1, block-state id14=1.19.4, itemCount VarInt=1.20.5).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
claude-timemachine
2026-06-19 19:13:19 +02:00
parent e4ab541200
commit 02a249a379
10 changed files with 42 additions and 62 deletions
+3 -7
View File
@@ -92,7 +92,7 @@ ViaVersion cross-check: `ClientboundLoginPackets.java` ordinals 05 match; `Se
The Configuration state runs between Login Acknowledged and Finish Configuration. Its purpose: push registry data, feature flags, resource packs, and tags before the client enters Play. The state can be re-entered from Play (server sends `Start Configuration`).
The packet set expanded again in **1.20.5 (protocol 766)**: Cookie, Transfer, Store Cookie, resource-pack split (push/pop vs. unified), Select Known Packs, Custom Report Details, Server Links were added, shifting most IDs.
The packet set expanded again in **1.20.5 (protocol 766)**: Cookie, Transfer, Store Cookie, resource-pack split (push/pop vs. unified), and Select Known Packs were added, shifting most IDs. **1.21** added Custom Report Details and Server Links (CB 0x0F/0x10, SB 0x08/0x09).
### Serverbound
@@ -110,9 +110,7 @@ The packet set expanded again in **1.20.5 (protocol 766)**: Cookie, Transfer, St
| `0x09` | Server Links Response | C→S | 1.21 | `links` (Array; echoes known-type or custom-text link list)² |
¹ In 1.20.21.20.4 the resource pack response had no UUID field; UUID was added when resource-pack-push/pop split was introduced in 1.20.5.
² IDs `0x08` and `0x09` are present in 1.21.1 per `protocol.json` (`custom_report_details`, `server_links`) but absent from earlier ViaVersion 1.20.5 enum — confirm exact introduction version.
<!-- UNCONFIRMED: Exact first version for SB Custom Report Details (0x08) and Server Links Response (0x09) — protocol.json shows them in 1.21.1; ViaVersion 1_20_5 SB enum only lists 8 entries (0x000x07). Likely 1.21.0 or 1.21.1. -->
² IDs `0x08` and `0x09` confirmed added in **1.21**: absent from `ServerboundConfigurationPackets1_20_5` (ends at 0x07) and present in 1.21.1 `protocol.json`. ViaVersion passes them through in the SB direction without a new enum file — `ServerboundConfigurationPackets1_20_5` covers 1.20.5 through 1.21.x (no SB enum file in `v1_20_5to1_21` package). Source: `ViaVersion/.../protocols/v1_20_5to1_21/packet/ClientboundConfigurationPackets1_21.java` (CB side confirmed) + `minecraft-data/data/pc/1.21.1/protocol.json` configuration.toServer.
**ID shift note (1.20.2 → 1.20.5 serverbound):**
@@ -153,9 +151,7 @@ Source: `minecraft-data/data/pc/1.21.1/protocol.json` → `configuration.toServe
| `0x0F` | Custom Report Details | S→C | 1.21 | `details` (Array of {key:String, value:String}); appears in crash reports¹ |
| `0x10` | Server Links | S→C | 1.21 | `links` (Array of {hasKnownType:bool, knownType:ServerLinkType (if known), unknownType:NbtComponent (if custom), url:String})¹ |
¹ `0x0F` and `0x10` present in 1.21.1 `protocol.json`; not in ViaVersion 1.20.5 CB enum (15 entries, 0x000x0E). Likely introduced 1.21.0 or 1.21.1.
<!-- UNCONFIRMED: Exact first version for CB Custom Report Details (0x0F) and Server Links (0x10) — same tracking note as SB counterparts above. -->
¹ `0x0F` and `0x10` confirmed added in **1.21**: `ClientboundConfigurationPackets1_20_5` ends at `SELECT_KNOWN_PACKS` (0x0E); `ClientboundConfigurationPackets1_21` (in `v1_20_5to1_21` package) adds `CUSTOM_REPORT_DETAILS` (0x0F) and `SERVER_LINKS` (0x10). Source: `ViaVersion/.../protocols/v1_20_5to1_21/packet/ClientboundConfigurationPackets1_21.java`.
**ID shift note (1.20.2 → 1.20.5 clientbound):**