All versions
24.0.0-1.21.1
Release
Immersive Vehicles - 1.21.1 - 24.0.03 months ago 42.2K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Immersive Vehicles 24.0.0
Important Stuff:
- Ported Immersive Vehicles to 1.21.1 NeoForge
- Fixed crash when IV and AdAstra are installed simultaneously
- Fixed tile entites such as benches & fuel pumps dissapearing randomly
Additions:
- Added a variable that triggers when looking at a defined hitbox group
- Added compatibility with cold sweat so players no longer freeze at high altitudes when riding a vehicle.
- Added Fr*nch translation
- Added comatibility with Jade so entity_builder_rendering no longer pops up constantly
- Added the ability to set a custom frequency of sin and cos variables
- Added back mouse yoke for planes. Togglable with C.
- Added a freecam function that disconnects client camera from vehicle orientation. Togglable with Ctrl by default.
- Added additional customizable keyboard keys, up to 10 from the initial 4
- Added the ability to bind mouse buttons in controls
Fixes:
- Fixed external fuel tank parts not doing fuel operations properly
- Fixed faulty particle spawning mechanics.
- Fixed Y2K button not working on servers.
- Fixed spelling in the handbooks
- Fixed whacky hitbox outline rendering in F3+B
- Fixed constant entity collision sounds when riding create trains.
Changes:
- Auto-Heli level is now false by default.
- Players now receive a part scanner on join on first world join.
- Increased fuel flow rate from external fuel tanks.
- Changed AllowExternalDamage to be true by default
- Changed builder_entity_rendering to no longer react to pistonPushReaction
- Create Cardboard Boxes now add mass to a vehicle
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:BCzBuhJ5:B9xnlDrC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BCzBuhJ5:B9xnlDrC"
}


