Label format change ('!missing' actions):
- "add TrueMoozic (renamed from truemusic)" → "add TrueMoozic B42"
- "add truemusic" → "add truemusic B41"
Build context lives in the suffix; the alias-rename hint was redundant
because the user already sees the original mod_id in the warning text.
RV Interior Expansion ordering (B42):
PROJECTRVInterior42 → RVInteriorExpansion → RVInteriorExpansionPart2
map folders: map_distanciado → map_aquatsar → rvupdate → rv2 → Muldraugh, KY
Authors didn't declare loadAfter in mod.info; new modpack rules file
data/modpack_rules/rv_expansion.txt establishes the chain. Triggers fire
when either expansion wsid (3618427553 / 3622163276) is in input.
20 lines
845 B
Plaintext
20 lines
845 B
Plaintext
; RV Interior Expansion (B42) — bundled sorting_rules.txt
|
|
; Triggers:
|
|
; - 3618427553 (RVInteriorExpansion, map folder rvupdate)
|
|
; - 3622163276 (RVInteriorExpansionPart2, map folder rv2)
|
|
; Auto-injected by app.py:_modpack_rules_for() when either trigger wsid is
|
|
; in the user's input. User-supplied rules are appended afterward and
|
|
; override these on conflicting keys.
|
|
;
|
|
; Authored ordering: PROJECTRVInterior42 → RVInteriorExpansion → RVInteriorExpansionPart2.
|
|
; The expansion mods don't declare these loadAfter relationships in their own
|
|
; mod.info, so without these rules sortof has nothing to base the cluster
|
|
; ordering on (PROJECTRVInterior42 is in PREORDER slot 7 already; expansions
|
|
; just need to chain off of it).
|
|
|
|
[RVInteriorExpansion]
|
|
loadAfter=PROJECTRVInterior42
|
|
|
|
[RVInteriorExpansionPart2]
|
|
loadAfter=RVInteriorExpansion
|