Client-side NeoForge 1.21.1 dynamic lighting for held and placed light
sources. Modrinth reports server_side as unsupported, so packwiz writes
side = "client" and the jar stays off the server.
The Modrinth version metadata lists Fabric API as a required dependency,
but that entry is not loader-scoped. The NeoForge jar actually depends
only on its JarJar-bundled lambdynlights_runtime, so packwiz failing to
resolve Fabric API is expected and no fabric-api metafile is added.
Client-side NeoForge 1.21.1 mod that walks the player forward on a
toggleable keybind. Modrinth reports server_side as unsupported, so
packwiz writes side = "client" and the jar stays off the server.
Replaces CurseForge metadata downloads with direct Modrinth CDN URLs for
every mod in the pack that Modrinth actually hosts, so those jars no longer
need the CurseForge API to resolve: apotheosis, apothic-attributes,
apothic-combat, apothic-enchanting, apothic-spawners, architectury-api,
patchouli, placebo.
Each was matched to the Modrinth file whose sha1 is identical to the
CurseForge file already pinned in the pack, so no mod version changes.
Apothic Attributes is the one exception: the CurseForge and Modrinth jars
both report 1.21.1-2.10.1 but differ by a single build timestamp inside
META-INF/MANIFEST.MF, with every other archive entry byte-identical.
Nine mods stay on CurseForge because they have no Modrinth project at all:
AllTheLeaks, Collapsible Groups, The Twilight Forest, and the six FTB mods
(Backups 3, Chunks, Library, Quests, Teams, XMod Compat). FTB is
CurseForge-exclusive, as are the other three.
Download hashes move from sha1 to sha512, packwiz's format for Modrinth.
Adds four NeoForge 1.21.1 creature/companion mods, all sourced from the
Modrinth CDN:
- Critters and Companions
- Adorable Hamster Pets
- Tiny Dragons
- Wings Of Fire!
"Wings Of Fire!" is published under the slug "wings-of-fire!" (the
exclamation mark is part of the name, not a typo), so its metadata file is
named wings-of-fire.pw.toml to keep the path free of zsh history-expansion
characters.
The side change in 0095265 was not followed by packwiz refresh, leaving a
stale hash in index.toml that breaks packwiz-installer with 'Invalid mod
file hash'.