Tags
Creators
Details
All versions
1.4.0-beta+neoforge-26.2
Beta
1.4.0-beta for 26.2 neoforge3 days ago 40
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client-side
Changes
1.4.0-beta
Breaking Changes
- feat(api): add modifier pipeline phases (55b4bdd)
- PerspectiveModifierChain.register now requires a modifier ID and PerspectiveModifierPhase.
- refactor(api): align perspective control lifecycle (780ed86)
- PerspectiveAPI.getCurrent now returns null when no perspective actively controls the camera, and the internal Runtime contract now receives enabled-state changes.
- fix(impl): stabilize perspective transitions (d0ed807)
- Orthographic height now interpolates even when a transition changes projection mode.
- refactor(api): require camera entity in callbacks (6244046)
- PerspectiveContext.cameraEntity now has a non-null return contract.
- refactor(api): apply modifiers before transitions (1cdbd35)
- Remove PerspectiveModifierPhase and the phase parameter from PerspectiveModifierChain.register.
- refactor(api): isolate transition algorithms (715f6e4)
- remove Transition#getBlendPower and Transition#setBlendPower. The persisted blend-power key is now specific to the fixed-start chasing-rotation algorithm.
Features
- feat(api): define controllable perspective semantics (5846076)
- feat(api): expose previous camera state (8b31405)
- feat(impl): add feed-forward transition algorithm (7e4fcae)
- feat(impl): add easing to feed-forward transitions (f53a752)
- feat(impl): allow runtime transition algorithm switching (f85f959)
- feat(api): add configurable easing function to transitions (e32ce42)
Bug Fixes
- fix(logic): reevaluate perspectives after level changes (734ea1d)
- fix(logic): avoid repeating post-transition effects (24072c0)
- fix(logic): isolate final camera callbacks (15cb101)
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| perspective_api-1.4.0-beta+neoforge-26.2-sources.jar | Source jar | 153.37 KiB |
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:LIqveQm1:3wBPqwlL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LIqveQm1:3wBPqwlL"
}


