Client QoL / visual / audio:
grassier-grass, perception, inventory-particles, fwa,
advancement-plaques, keybind-atlas, held-item-tooltips, zume, sound,
extreme_sound_muffler, now-playing, cat_jam, loot-journal,
travelers-titles
Libraries:
moonlight, shatterbyte-lib (OctoLib), runiclib, delight-lib,
lodestonelib, mossylib, puzzles-lib, mru, fragmentum, smartbrainlib,
blueprint, coroutil
perception and sound carry side = "client", so neither is installed on the
dedicated server.
Two of the libraries are dependencies that Modrinth metadata does not
declare, so packwiz cannot resolve them automatically: perception hard-links
OctoLib and dungeons_delight links runiclib. Adding them up front means the
later stages resolve without a missing-class crash.
Mazes is a NeoForge 1.21.1 mod that adds a Maze Generator block: place it,
open the GUI, and it builds a flat, configurable maze on the block's own
level. The border is a subtractive cell mask cut out with pencil/rectangle
tools, so it can fill odd shapes and rooms instead of only a rectangle.
The mod is not on Modrinth or CurseForge, so the jar is hosted as a release
asset on yonlu/mazes and referenced with a packwiz url metafile. It targets
NeoForge 21.1.0+, so the pack's 21.1.251 is fine, and side is "both" because
it registers a block entity and network payloads.
FTB Teams was the only thing holding FTB Quests down -- FTB Quests' 1.21.1
build requires it, and its bytecode references dev/ftb/mods/ftbteams in 14
classes including the event handler, so it breaks at runtime without it. With
quests unused, the whole block goes. XMod Compat only bridged
Quests/Chunks/Ranks, all of which are now gone.
FTB Library stays because FTB Backups 3 builds its config UI on it
(Panel/Theme/Widget/ConfigGroup/ConfigValue/SNBTCompoundTag, 13 classes, and
it does not bundle them despite declaring only neoforge). Architectury API
stays because FTB Library references it in 47 classes.
Verified before removing: FTB Library and FTB Backups 3 reference ftbteams,
ftbquests and ftbxmodcompat in zero classes each, and nothing else in the pack
references them.
CurseForge-sourced mods drop from 9 to 5; pack is 146 mods. OPAC's built-in
party system is now the only one, so primaryPartySystem should be left at its
default rather than pointed at ftbteams.
FTB Chunks is the only mod in the FTB suite that nothing else depends on --
FTB Quests requires FTB Library and FTB Teams only, and ships no claim-chunk
task type -- so it can leave without touching quests. Open Parties and Claims
takes over claims and force-loading, and the Xaero's suite restores the
minimap, world map and waypoints that b0542f9 removed.
The three Xaero's entries are byte-identical to the ones b0542f9 deleted, so
this reverts the map half of that commit rather than integrating anything new.
Xaero's + OPAC is also the pairing both projects document: the world map
displays OPAC claims and lets you claim and forceload from the map screen.
Drops config/ftbchunks-client.snbt and the .packwizignore negation that
shipped it, since the FTB Chunks minimap it enabled no longer exists. Also
keeps authoring/review material and migration scratch out of the pack index.
Server-side follow-up (not shippable, lives in the world save): set
maxPlayerClaimForceloads to 25, point primaryPartySystem at FTB Teams, and
decide claims.forceload.offlineForceload.
It is distributed via CurseForge metadata only, which packwiz cannot
fetch automatically and forces a manual download. Remove it so the pack
stays fully automatic; Iris Veil Compat retains the Create Aeronautics
visual fix for Veil under shaders.
DH was optional (default on), which still lets launchers/exporters skip
it and left the server's LOD data unused. Drop the [option] block so it
is required and installed for every client.
Integrate Iris + shader packs, better-leaves bump, and fresh-animations
extensions alongside the server-side Clumps/C2ME/Noisium work on main.
index.toml and pack.toml regenerated with packwiz refresh.
The server generates and serves DH LODs, but DH was opted out by default,
so clients never received them. Default it on (still optional/opt-out) so
players get server-side distant terrain out of the box.
Removes the Xaero mapping suite -- Xaero's World Map, Xaero's Minimap,
Xaero Train Map and the Waystones compatibility -- and enables the FTB
Chunks minimap, so FTB Chunks provides all mapping.
Xaero Train Map and the Waystones compat had to go with the maps: the
former declares a required dependency on xaeroworldmap, and the latter
references only xaero/common and xaero/minimap classes. Nothing in the
pack declared a dependency on xaeros-minimap.
The minimap needs an explicit config because FTB Chunks computes
minimap.enabled once as !hasOtherMinimapMod() and then persists the
result. With Xaero's Minimap installed that resolved to false and was
written into players' configs, where it sticks, so removing the other
minimap mod alone would not re-enable it. config/ftbchunks-client.snbt is
the location the mod itself documents for modpack defaults, and unlike
defaultconfigs/ it also overrides configs that already exist.
.packwizignore moves from excluding config/ wholesale to config/* plus a
negation, so this one modpack-default config ships while server config
stays untracked.
Adds an [option] block so Distant Horizons is a user-toggleable mod instead
of always installed, matching how Controlify is already declared.
default = false expresses opt-in wherever the consuming exporter supports
it: modrinth/export.go reads only Optional, so in an mrpack the mod becomes
a toggle (that format has no off-by-default concept), while
curseforge/export.go reads Default and marks it optional-and-disabled.
Nothing in the pack depends on or conflicts with Distant Horizons, so no
other mod is left unsatisfied by it being skippable.
Adds Waystones plus two integrations that hook mods already in the pack:
Waystones: Sable (Create Aeronautics addon) and Xaero's Minimap & World
Map - Waystones Compatibility.
packwiz auto-resolved Balm as Waystones' required library; it was then
added explicitly as well, which was a no-op, so there is only one Balm
metafile.
Balm's Modrinth environment is client_or_server, which packwiz flags as
ambiguous ("one of these is unnecessary") and records as side = both.
That is the right call here: Balm is a library needed wherever Waystones
runs, and Waystones is client_and_server.
All four pinned versions are NeoForge 1.21.1 releases, and each jar's
sha512 was re-verified against its recorded hash.
Content and QoL: Emotecraft, Ping Wheel, Nature's Compass, Farmer's Cutting:
Twilight Forest, Ars Nouveau's Flavors & Delight, Ocean's Delight, End's
Delight, Twilight's Flavor & Delight, Legendary Tooltips, Dynamic FPS,
Subtle Effects, Enchantment Descriptions, Entity Culling, Xaero Train Map,
Jade Sable Compat, Sable: Physics Compat, Apothic Category Compat,
Gravestone x Curios API Compat.
packwiz auto-resolved four required libraries that were not in the pack:
Iceberg and Prism (Legendary Tooltips), Prickle and Bookshelf
(Enchantment Descriptions).
Each pinned version was confirmed to be a NeoForge 1.21.1 build and each
jar's sha512 re-verified against its recorded hash. Sides are derived from
Modrinth's environment metadata; packwiz maps server_only to both on
purpose because such mods also work in singleplayer, where the client is
the logical server (dedicated_server_only is what yields "server").
Farmer's Cutting: Twilight Forest is published as a mod as well as a
datapack, and the neoforge mod variant is what gets pinned.
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.
logan
yonlu