Links
Tags
Creators
Details
0.1.0-beta.4
Compatibility
Changes
Rift Gun 0.1.0-beta.4
The fourth public beta of Rift Gun, adding new endgame modules, significantly improving Portal Gun rendering performance, opening portal fuels to datapacks, and completing a major internal portability refactor.
Highlights
- Added the Zero-Point Fuel Module, providing unlimited use of the currently loaded portal-fluid profile.
- Added the Creative Module, granting all Portal Gun module functions at their configured maximum values.
- Added the Advanced Basic Module as a new endgame crafting component.
- Significantly reduced Portal Gun item rendering overhead through synchronized visual state and cached model variants.
- Added datapack support for custom Portal Gun fuels.
- Improved Matter Anchor configurability.
- Completed a major internal architecture refactor in preparation for future Minecraft-version and mod-loader ports.
Details
New Modules
Zero-Point Fuel Module
- Makes the currently loaded portal-fluid profile unlimited.
- Preserves the loaded fluid's color, consumption profile, and cross-dimensional capability.
- Provides unlimited Dimensional Portal Fluid behavior when the Portal Gun is empty.
- Does not force the tank gauge to appear full.
- Its survival recipe can be disabled through the server configuration.
Creative Module
- Grants every Portal Gun module function at its configured maximum.
- Unlocks the complete module bay.
- Has no survival recipe.
- Available through Creative mode or administrator commands.
Advanced Basic Module
- Added as the endgame crafting base for the Zero-Point Fuel Module and Eternal Duration Module.
- Its recipe returns all bucket containers.
- The Dragon Egg used in its recipe is not consumed.
Rendering Performance
- Reworked the Portal Gun item renderer around synchronized visual state and cached layered-model variants.
- Fluid-level and module changes now update rendering state only when the gun's contents actually change.
- Removed the previous heavy per-frame model composition path.
- In the tested scene, holding the Portal Gun no longer produced a measurable FPS difference:
118 FPSheld and118 FPSunheld.
Portal Fuels and Datapack Support
- Datapacks can now define additional Portal Gun fuels.
- Fuel definitions can target either a specific fluid or a fluid tag.
- Custom definitions can control display color, cross-dimensional capability, and minimum and maximum fuel consumption.
- Java-based fuel resolvers remain available for integrations requiring dynamic behavior.
- Built-in portal fluids remain compatible with the existing server configuration.
Datapack fuel definitions are loaded from:
data/<namespace>/riftgun/portal_fuels/<name>.json
Configuration
- Added
modules.matterAnchorPreventsDespawn, enabled by default. - When
matterAnchorPreventsDespawnis disabled, Matter Anchor still protects dropped Portal Guns from fire, lava, and explosions but no longer prevents normal despawning. - Added a server-side option to disable the Zero-Point Fuel Module survival recipe.
- Configuration is now exposed to gameplay through immutable snapshots and updated atomically after loading or reloading.
- Fixed a startup failure caused by accessing NeoForge configuration values before they had been initialized.
Internal Architecture
- Unified passenger-tree transfer behavior between normal portal transit and Entity Relocation.
- Added explicit
SUCCESS,PARTIAL, andFAILEDtransfer outcomes. - Reorganized Entity Relocation preparation and active transfer state around explicit transfer sessions.
- Isolated NeoForge-specific configuration, lifecycle events, registration, networking, fuel storage, and rendering integration behind platform boundaries.
- Added architecture tests to prevent NeoForge dependencies from leaking into common core code.
- Decoupled shared Portal Gun visual semantics from the current baked-model implementation, reducing the scope of future renderer migrations.
These changes prepare Rift Gun for future Minecraft-version and mod-loader ports.
Beta 4 remains a NeoForge-only release. Fabric support is not included in this version.
Requirements
- Minecraft
1.21.1 - NeoForge
21.1.140+ - Java
21 - The same Rift Gun version must be installed on both the client and server.
There are no required runtime dependencies other than NeoForge. JEI and RyoamicLights integrations remain optional and are not bundled in the release JAR.
Beta Notice
This is a beta release. Back up your worlds before upgrading.
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:xuEiicZu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kfPLUrbd:xuEiicZu"
}

