Links
Tags
Creators
Details
All versions
1.9.0
Release
VelocityResourcepacks 1.9.0 (build 624)last year 3,164
Compatibility
Minecraft: Java Edition
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.x
Platform
Velocity
Changes
- Support Minecraft versions up to the current 1.21.8 release
- This includes multi-pack support starting with 1.20.3 clients (defined via the
packsoption). Older client versions will still only apply one pack (the first from the list) - On 1.20.3 or newer clients packs are now removed directly when they should no longer apply rather than the empty pack being used to reset it
- Added a config option to toggle the appending of the hash to the pack's url (
append-hash-to-url, enabled by default to keep old behaviour. On modern Minecraft client versions this should no longer be necessary as MC-164316 was fixed in 1.20.3) - Added the ability for the plugin to automatically update the hash of a pack based on a path on the machine the plugin is running on. (
local-pathpack config option, this does not host the pack!) Useful for when your webserver runs on the same machine as you Minecraft server or you can deploy the pack in your pack build setup to both your webserver and Minecraft server at the same time. Please note that if you are running in a container like Pterodactyl you need to do additional configuring to expose the files inside the container! - Added support for AuthMeVelocity, LibreLogin, LibrePremium, OpeNLogin, nLogin and JPremium authentication plugins
- Support sending of resource packs before joining (only possible on Velocity for now)
- Added a warning for when certain hosts are used for packs that have been known to cause pack downloads to break (Dropbox, Google Drive, Mediafire. The last two are blocked completely)
- Added new language files: Simplified Chinese by Q2297045667 and Brazilian Portuguese by Logikoz
Please note that there might be more changes since this update:
Download new builds here!
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:Vepot5T4:PhUwm3C7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vepot5T4:PhUwm3C7"
}

