Tags
Creators
Details
v0.2.2
Compatibility
Required content
Changes
Beta — not yet tested in a headset. The teleport and melee fixes are verified against real Vivecraft and Sable bytecode and covered by unit tests, but no one has yet confirmed them in VR on a moving Sable structure. Please report anything that misbehaves: https://github.com/bh679/vivecraft-sable-compat/issues
What's Changed
- feat(diagnostics): make a tester's latest.log enough to debug from by @bh679 in https://github.com/bh679/vivecraft-sable-compat/pull/1
- ci: add build/test + mixin-target CI and dispatch-only release workflow by @bh679 in https://github.com/bh679/vivecraft-sable-compat/pull/2
- docs: add the Modrinth + CurseForge publishing runbook by @bh679 in https://github.com/bh679/vivecraft-sable-compat/pull/3
New Contributors
- @bh679 made their first contribution in https://github.com/bh679/vivecraft-sable-compat/pull/1
Full Changelog: https://github.com/bh679/vivecraft-sable-compat/commits/v0.2.2
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:Ixiye7RK:6JgjKuhh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ixiye7RK:6JgjKuhh"
}

