Tags
Creators
Details
1.3.0-snapshot.9+26.1.1-forge
Compatibility
Changes
Ninth snapshot of the 1.3.0 line.
Added
- Moves a legacy accessor-only Mixin when one target, an exact owner-scoped field redirect, and an unchanged descriptor prove the new owner. It follows Mixin's implicit-name rules and adds
@Mutableonly when the shim marks that destination as mutable.
Fixed
- Repairs legacy block random-tick accessors after the field moved from
BlocktoBlockBehaviourand became final. Calls through a proven setter now refresh every cached block state, so the new value reaches random-tick scheduling. - Updates 48 same-contract
GameRulesconstants after Fabric intermediary names expand to retiredRULE_*spellings on 26.1 and newer. Retromod leaves the changed fire-tick rule and three inverted boolean rules untouched because a field rename cannot preserve their values. - Transforms explicitly selected
aotandbatchinputs when their metadata omits the source Minecraft version. Retromod applies only matching-loader shims available on the selected host, while automatic scans still leave unknown-version native mods alone. - Prevents
<target,<=target, and>targetFabric constraints from being mistaken for native target declarations. Exact target predicates and matching wildcards still pass through unchanged. - Uses the detected Minecraft host version for transforms started from the in-game compatibility screen. A 26.2 client no longer prepares those mods as 26.1 output.
- Takes an immutable snapshot of a mod's classes before parallel Fabric, Forge, or NeoForge transforms begin. Frame rebuilding and post-remap adapters no longer risk reading a class while another worker replaces it.
- Preserves the implementation namespace of bundled MixinExtras libraries while still translating legacy calls from mod code. Nested-jar transforms no longer disable MixinExtras initialization and break unrelated Fabric API mixins that use
@Localparameters. - Applies matching common API bridges during known-source CLI and AOT transforms. API release numbers stay outside Minecraft version-chain searches.
- Selects library API repairs outside the Minecraft graph while still gating host-versioned API repairs. Explicit same-version CLI and AOT transforms can apply those providers.
- Updates staged resource and data packs through Minecraft 26.2, including current minor pack formats. Data packs run compatible 26.x content migration when needed, while legacy resource packs run item-definition and content migration only during an actual format upgrade.
- Processes staged resource and data packs on Fabric, Quilt, Forge, and NeoForge instead of limiting pack work to Fabric startup.
- Reads the Minecraft dependency from
quilt.mod.jsonand keeps it authoritative when a jar also contains Fabric metadata. The shared Fabric artifact carries both metadata files and uses entrypoint contracts Quilt Loader can invoke, so Retromod does not publish a separate Quilt artifact. - Keeps the Windows and Unix release builders on the same version, Minecraft matrix, integrity checks, artifact counts, and checksum output.
build.shandbuild.batnow delegate to the canonical builders.
Changed
- Updates JUnit Jupiter from 5.10.1 to 6.1.3 and the release publisher's
charset-normalizerfrom 3.4.9 to 3.5.1.
Accessor owner moves still refuse multiple Mixin targets, mixed-purpose interfaces, unmatched companion accessors, conflicting destination fields, method-shaped redirects, and descriptor changes. Unknown-source fallback has no exact starting version, so a precise metadata version remains safer. Pack migration refuses unknown targets, malformed metadata, newer-only input, overlays, and conflicting paths. Those sources remain staged. The removed fire-tick boolean and inverted game rules need value-aware adapters.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:fUS6bo71:5Bqd6UzS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fUS6bo71:5Bqd6UzS"
}

