Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated last month
All versions
1.6.0-alpha1
Alpha
1.6.0-alpha1 [FORGE 1.20.1]7 months ago 2,458
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
After longer than I initially planned, ImmersiveMC 1.6.0 Alpha 1 is here!
Major Changes
- Migrated from MC VR API to Vivecraft's official API! This means ImmersiveMC now requires Vivecraft 1.3.3 or later, but no longer requires MC VR API.
- As a consequence of requiring such a recent Vivecraft version, ImmersiveMC now no longer supports Minecraft 1.19.3 or 1.20.2.
- Added support for Minecraft 1.21.11.
Minor Changes
- Made it so a trigger or grip button press is required to open the bag using ImmersiveMC's gesture. This can be disabled in ImmersiveMC's settings if desired.
- Added a petting API to allow for mod developers to more easily add to ImmersiveMC's petting feature.
- Petting now allows petting mobs tamed by other players by default.
- Removed shield blocking, since that's now built-in to Vivecraft.
- Removed the ability for server owners to force players to use ImmersiveMC features.
- Organized ImmersiveMC's
resourcesfolder to have coherent organization, especially for resource pack creators.
Bug Fixes
- Fixed a duplication glitch with ImmersiveMC and FastWorkbench.
- Fixed an issue where a freshly-placed double chest would not be interactable via ImmersiveMC.
- Fixed being unable to throw brown eggs and blue eggs.
- Fixed the configuration screen for custom colors resetting when adding or removing colors.
- Fixed an issue where hoppers and shulker boxes would oddly glide when changing which side items are viewed from.
- Fixed
ItemSwapAmountbeing used in the API, but not provided in it.
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:XJ9is6vj:WETVTrYv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XJ9is6vj:WETVTrYv"
}

