From 621cea18ca4560d28d80dc0285164b08ee3274a2 Mon Sep 17 00:00:00 2001 From: Ludovic Marie <136255825+ludovic111@users.noreply.github.com> Date: Mon, 19 Oct 2026 15:04:18 +0200 Subject: [PATCH] docs/modpacks.md: carry types bare number ranges Co-Authored-By: Claude Opus 5.5 --- docs/modpacks.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/modpacks.md b/docs/modpacks.md index 576749b75..868196aef 100644 --- a/docs/modpacks.md +++ b/docs/modpacks.md @@ -326,7 +326,10 @@ A byte-order mark is dropped. For ATM10's 42 mods that is 19 files in 7 mods, an carried. No class file is copied. It upgrades from 1.21.1 to 26.3: vanilla-type recipes (ingredients), loot tables (`conditions` lists become one `condition`, `functions` become `modifier`, kinds move to `type`, tool matches on silk touch or shears become `minecraft:tool/can_silk_touch` and -`minecraft:tool/can_shear`), and the `items/` definitions 1.21.4 introduced. +`minecraft:tool/can_shear`, and number providers written as a bare `{"min", "max"}` get +`"type": "minecraft:uniform"`), and the `items/` definitions 1.21.4 introduced. 1.21.1 read such +a bare range as uniform and 26.3 refuses it: 304 of ATM10's carried tables have them (rolls, +counts, enchantment levels), and before the carry typed them their chests came out empty or short. Blocks and items come from the NeoForge oracle when `/oracle/facts.json` exists (step 6): every block the mod registers gets the vanilla template of the same vanilla class and states