All versions
0.3.12
Release
VoidRP UI 0.3.12last month 3
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platforms
Paper
Purpur
Changes
0.3.12
Pages are lighter on the network, and the cursor follows your hand more closely.
- Only the part that changed is sent. A page used to be resent in full on every change: a scroll, a hovered row. It is now split across three boss bars at the edges of scrolling lists and menus, and only the pieces that changed go out. Scrolling the example shop dropped from 17 KB to 7 KB per notch.
- The cursor is 20 ms closer to your hand (45 ms behind instead of 65). While you move, it aims slightly ahead of the last reading. After a sudden stop it goes about 10 units past the target and settles back within ~75 ms. You can tune this with
input.predictioninconfig.yml(default0.35,0restores the old behaviour) or live with/vui debug predict <value>. - The cursor now reaches the very top of the screen. It used to vanish over the top 19 units.
Also since 0.3.8
- Pages survive what happens to the player.
- Death closes the page, like the game's own menus.
- A teleport that turns the player (e.g.
/spawnwith a facing) no longer throws the cursor to the edge. - Travelling to the Nether and back no longer "presses" a number key on the page.
pack.publish-dirfor servers that host the pack themselves. The plugin copies fresh pack archives there on every start. It also checks at startup thatpack.urlserves the pack it just built, and says so in the log. This fixes "Failed to load 1 of 1 packs" after an update.
Updating
- The resource pack changed in this version. With
pack.publish-dirset, or the built-in pack server, there is nothing to do. - If you host the pack yourself without
publish-dir, upload the new archives fromplugins/VoidRpUI/. - A page now uses 4 boss bars: 3 for the page and 1 for the cursor. With PacketEvents installed, other plugins' bars are still hidden while a page is open.
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:K6cjpywA:NAuAnbqT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K6cjpywA:NAuAnbqT"
}

