Links
Tags
Creators
Details
mc26.1.2-v0.1.0-beta.6
Compatibility
Changes
Rift Gun 0.1.0-beta.6 for 26.1.2
Rift Gun 0.1.0-beta.6 is the first public release for Minecraft 26.1.2.
It brings the Rift Gun feature set to the new platform through the multi-version shared codebase. Because the 26.1.2 port is new and has received less real-world testing than the established 1.21.1 build, it remains in beta.
Highlights
- Added full Minecraft 26.1.2 / NeoForge 26.1.2.95+ support.
- Ported the complete Rift Gun feature set to the new rendering, data, networking, and platform APIs.
- Fixed portal travel to distant and never-loaded chunks.
- Restored custom crafting recipe and fluid-transmutation integration with JEI.
- Fixed multiplayer synchronization of datapack-defined fluid transmutation recipes.
- Added the same destination-safety and transit-feedback improvements as the 1.21.1 release.
Details
Minecraft 26.1.2 Port
Rift Gun has been ported to Minecraft 26.1.2 with support for the platform's new APIs and systems, including:
- the new rendering pipeline;
- per-version NBT handling;
- recipe and datapack registration;
- chunk-ticket handling;
- networking;
- client GUI integration;
- resources and model handling.
The 26.1.2 build shares its core gameplay implementation with the 1.21.1 version.
Portal Transit
-
Fixed portal chunk tickets targeting the wrong chunk because of a block-coordinate / chunk-coordinate mix-up.
- Teleports to destinations whose chunks have never previously been loaded now proceed correctly.
-
Transit can now proceed while a distant exit chunk is still loading.
-
Portal timing begins immediately so distant exits can become usable correctly.
-
Fixed an Entity Relocation reservation leak when the target destination is outside the valid world bounds.
-
Out-of-bounds portal placements, destinations, chunk tickets, and relocation exits are now rejected with clear feedback.
Destinations and Feedback
-
Fixed destinations continuing to open portals to a previously selected player.
-
Added notifications for out-of-bounds destinations.
-
Added action-bar feedback when transit is refused because:
- the portal exit is blocked;
- the exit portal is not ready.
Recipes, Datapacks, and JEI
-
Restored the JEI integration on Minecraft 26.1.2.
-
Fluid transmutation recipes are displayed through the custom JEI category.
-
Custom crafting recipes are displayed with the correct 3×3 layout, including:
- Advanced Basic Module;
- Zero-Point Fuel Module;
- Eternal Duration Module recipe chain.
-
Custom recipes also appear correctly in the recipe book.
-
Datapack-defined fluid transmutation recipes now synchronize correctly to clients in multiplayer.
-
Restored the required special recipe codecs and enchanted-book ingredient handling.
-
Clean datapack reloads now complete successfully.
Client and Rendering
- Fixed duplicate background rendering.
- Player-list requests are now guarded while disconnected.
- Bucket and key assets have been restored.
Requirements
- Minecraft
26.1.2 - NeoForge
26.1.2.95+ - Java
25 - The same Rift Gun version must be installed on both the client and server.
There are no required runtime dependencies other than NeoForge.
Known Issues
- A faint light rim may appear around the portal surface. This is cosmetic and remains under investigation.
- RyoamicLights integration is not currently available on Minecraft 26.1.2.
- Shader-pack rendering currently uses a conservative compatibility fallback, so appearance may vary between shader packs.
Beta Notice
This is the first Rift Gun release for Minecraft 26.1.2.
The gameplay feature set is intended to match the 1.21.1 build, but the platform port is newer and has received less real-world testing. Please report any version-specific issues you encounter.
Back up your worlds before updating.
Optional dependencies
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:kfPLUrbd:M8IKLeRQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kfPLUrbd:M8IKLeRQ"
}

