Tags
Creators
Details
All versions
1.1.9.1
Release
Vanish++ 1.1.9.1 (Velocity)5 hours ago 9
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.6
Platform
Velocity
Changes
[1.1.9.1] - 2026-10-23
Added
/vanish version,/vanish infoand/vinfo: show the running version, whether an update is available (with a click-to-download link to the exact Modrinth version) and where to find help./vhelpnow shows the version at the top too. Needsvanishpp.vanish; everyone else gets the usual unknown-command message, so the plugin stays hidden.
Fixed
- Update checker now follows redirects: Java's
HttpURLConnectiondoesn't follow307/308redirects, which is how Modrinth answered after the project was renamed - so every version up to 1.1.8 silently stopped finding updates. 1.1.9 already switched to the project ID; the checker now also follows up to 5 HTTPS redirects, so a future rename or move on Modrinth's side can't break it the same way. - Velocity update checker never worked: it looked up the project under
update-checker.modrinth-id, whose default (vanishpp) never existed on Modrinth, so proxies were never told about updates. It now uses the project ID like the Paper side, and the misleadingmodrinth-idsetting is gone from both default configs. - Update checks fall back to GitHub: if Modrinth can't be reached or answers with an error, both checkers compare against the latest GitHub release instead (the download link still goes to Modrinth), so one side breaking can't silently stop update notifications again. A daily GitHub Action also checks the exact URL the plugins use and fails as soon as Modrinth stops answering it directly or a GitHub release is missing from Modrinth.
- Update download link could open the Velocity build: the link pointed at the version number, which the Paper and Velocity uploads share. It now uses the exact Modrinth version ID.
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:kbKpK1bc:ecaElUio"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kbKpK1bc:ecaElUio"
}

