Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 11 months ago
Updated 2 months ago
All versions
1.3.15-1
Release
Vivecraft-Spigot-Extension 1.3.15-12 months ago 4,450
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.8–1.8.9
Platforms
Folia
Paper
Purpur
Spigot
Changes
- fix dualwielding triggering some item change triggers from other plugins
- fix roomscale shield blocking not triggering shield disables for weapons that should disable them, like axes
- fix roomscale shield blocking not working when players in creative attack while flying and standing still
- fix roomscale shield blocking not accounting for shield bypass data components
- fix roomscale shield blocking with 2 shields only blocking correctly for the main hand
- fix roomscale shield blocking not causing knockback for explosions
- fix error spam with some plugins that add dummy creepers/enderman
- fix loading on paper with java 25
- add option to nerf roomscale shield blocking, by allowing to disable them on any hit for a set amount of time
- vrChanges.roomscaleShieldCooldown specifies the tick count the shield will be disabled
- vrChanges.roomscaleShieldCooldownDamageTrigger specifies at what damage amount the cooldown will trigger
- add pvp permissions to be able to handle pvp exclusions per player
- permissions are:
- vivecraft.no-pvp-standing-vs-standing
- vivecraft.no-pvp-standing-vs-seated
- vivecraft.no-pvp-standing-vs-nonvr
- vivecraft.no-pvp-seated-vs-seated
- vivecraft.no-pvp-seated-vs-nonvr
- permissions are:
- add setting to kick players with a too low vivecraft version (affects VR and NONVR players)
1.9-1.21.4:
- fix missing shield blocking sound with roomscale shield blocking with low damage attacks
- fix roomscale shield blocking not damaging shields that are undamaged
supports Minecraft 1.8.8 - 26.2
supports all features of Vivecraft 1.3.15
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:o8TGTrsR:a5Q05ibQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o8TGTrsR:a5Q05ibQ"
}

