v26.1-rc
Compatibility
Required content
Changes
Overview
v26.1-rc is the release candidate after v26.1-beta, focused on recipe completeness, gameplay polish, and late stability work before the final v26.1 release.
Changes
- Added several missing or expanded recipes, including
Universe Banquet,Universe Bucket,Ender Dragon Spawn Egg,Wither Spawn Egg,Rainbow Thingcooking, andSupreme Blockuniverse cooking. Universe Banquetnow grantsRegeneration VIIfor10minutes when eaten.- Reduced the minimum valid frame size for both custom portals to
3x4, making portal setup easier. Harvest Continentnow repopulates farm animals in its core biomes, improving the dimension's ambient life and resource availability.- Updated summon structure handling so mob summoning no longer depends on structure facing, and adjusted the
Sculk Behemothsummon layout. - Improved
Universe Librarycontainer behavior, including more reliable open/close handling and better shift-click interaction. - Fixed the root
Universeadvancement trigger to unlock from the intended item. - Fixed the
Universe Workstationrecipe book carousel behavior. - Refreshed the
Item Hubitem model and texture presentation, and updated theSupreme Blocktexture. - Standardized how
Universeequipment handles enchantments so restricted items now consistently reject vanilla enchant application paths.
Internal
- Refactored
Universe Libraryto use the standard container opener lifecycle. - Improved summon structure and portal detection internals for better edge-case handling.
- Cleaned up Java declaration formatting logic in
build.gradle. - Updated mod metadata links and refreshed the mod icon.
- Refreshed the project
README.
Compatibility
- Minecraft
26.1 - Fabric Loader
0.18.4+ - Java
25+
Compare
https://github.com/roeyqian/Magnatour/compare/v26.1-beta...v26.1-rc
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:xu8wy0oC:h33aXxYL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xu8wy0oC:h33aXxYL"
}

