Rope [Rope]

Rope 1.1.1

Fixed

• Minecraft 26.3 (Fabric and NeoForge): no world, new or existing, could be opened with Rope installed; the game stopped with "Failed to load level data or datapacks". The rope recipe advancements now use the 26.3 format.
• Minecraft 26.3: a rope block destroyed by an explosion always dropped itself. It now follows the same explosion rule as on every other version.
• NeoForge 26.3: on every NeoForge build from 26.3.0.37-beta on, the game stopped while loading mods with "Rope (rope) has failed to load correctly". Rope now registers its config the way these builds expect, under the same file name, config/rope-common.toml.
• Minecraft 1.21.11 on Forge and NeoForge: the log no longer shows "Couldn't load mod/rope pack metadata" every time a world is loaded.

Changed

• Minimum loader versions now match what the mod really needs. Most went down, for example on 1.20.1: Fabric API 0.83.0 instead of 0.92.7, Fabric Loader 0.14.21 instead of 0.16.10, Forge 47.1.0 instead of 47.3.0.
• Fabric 26.2 now asks for Fabric Loader 0.19.3, which Architectury API 21.0.7 already required.
• Fabric 26.1.2 now asks for Fabric Loader 0.19.5 or newer: Architectury API 20.1.14 crashes the game at startup on older loaders.
• NeoForge 26.3 now starts at 26.3.0.37-beta (1.1.0 said 26.3.0.0-beta).

Unchanged

• Same Minecraft versions and loaders as 1.1.0. Placing, pulling up and shooting rope work as before.

Compatibility

• Install on both server and client (Rope adds a block, an item and an entity).
• Fabric needs Fabric API and Architectury API. NeoForge needs Architectury API. Forge needs nothing else.
• NeoForge 26.3.0.48-beta and later need Architectury API 22.0.4 or newer, with or without Rope: 22.0.1 itself stops the game at startup there.
• Modpacks that override the rope recipe on 26.3 must use the 26.3 advancement format ("recipes" instead of "recipe"). A ready example is in the repository's modpack-datapack-examples/minecraft-26.3.

No version was removed.