Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 2 weeks ago
All versions
1.21.8-1.3.8-forge
Release
Vivecraft 1.21.8-1.3.8-forge2 months ago 52
Compatibility
Minecraft: Java Edition
1.21.6–1.21.8
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Changes
- add option to disable the screen dimming while sleeping
- reduce opengl log spam on repeated errors
- update Russian, British and Simplified Chinese translations
- add dewdrop watering cans to roomscale bow exclusion
- speed up menuworld loading slightly
- fix server crash when players without the mod attack with boots attack damage modifier set
- fix reverse bow not working without dualwielding
- fix offhand projectiles not aiming in the offhand direction without dualwielding
- fix vr keyboard not popping up on some mod text fields
- fix vr hands with entity model features 3.2+
- fixes hands being invisible with player animator
- fix freemove direction with epic fight
- fix crash with colorwheel, for correct visuals use colorwheel 1.2.7+
- fix first person fire not rendering with shaders when gui is set to with shader
- fix menuworld brightness with Sable
- fix some keybinds not working outside vr, like export menuworld
- fix hands being different brightness on both eyes on block borders
26.1:
- fix gui occlusion in 3rd person
1.21.11:
- fix map background rendering
1.21.6+:
- fix nausea only affecting some parts of the world
1.21.5+:
- fix nausea effect not being reduced, just the portal effect was reduced
1.20.6-1.21.11:
- fix nausea/portal effect reduction with iris shaders not working
1.21.3+:
- fix cape rotation on vr players
1.21.1:
- fix spyglass with first person player model showing twice on neoforge
1.19.2/1.18.2:
- fix iris vivecraft camera uniform
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:wGoQDPN5:OxUXmOvF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wGoQDPN5:OxUXmOvF"
}

