Tags
Creators
Details
All versions
0.5.23
Release
Jarvis AntiVPN 0.5.232 months ago 18
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Folia
Purpur
Spigot
Changes
- New: /antivpn doctor. One screen that tells you whether Jarvis is working and, if it isn't, what to check: licence, protection, clock, live panel channel, the IP your players arrive with and how many blocks are loaded. Each line green, amber or red. In all 27 panel languages.
- New: your blocks survive a restart. If the server restarts while Jarvis is unreachable, the blocks from the last sync keep applying instead of the server starting with none. They stop as soon as Jarvis answers again, and timed blocks still expire on time. Turn it off with bans: { persist: false }.
- New: the Paper build runs on Folia. The same jar covers Paper, Spigot and Folia: it uses Folia's regionised schedulers when it detects one and the usual scheduler otherwise. Before, it relied on a scheduler Folia does not have.
- New: the console says when Jarvis is not protecting you, and keeps saying it. Warnings that did not exist before, repeating while the problem lasts instead of being said once and then forgotten: Jarvis cannot be reached or your licence was rejected; the address arriving is not the player's (a proxy in front without IP forwarding, so nobody is being checked at all); the live panel channel has been down long enough that blocks and settings from your panel are not arriving; and a login that was let in without being checked because Jarvis accepted the connection and never finished answering.
- Protection now comes back on its own after an outage. While Jarvis is unreachable the connector lets players in so your server keeps running; getting back was tied to the next player login, and if that one probe never answered, every login kept going through unchecked until you restarted. The periodic ping now closes it as soon as Jarvis answers, a stalled probe is retried, and the console tells you.
- /antivpn whitelist, unwhitelist, blacklist and unblacklist now say when nothing was sent because the server isn't linked to a licence yet, or the licence was rejected, instead of reporting a network problem.
- Verified on Velocity 4.0 (with Floodgate), Velocity 3.x, BungeeCord and Paper.
- Other minor fixes and cleanup.
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:HTRGHm9r:RWZi3Yxj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HTRGHm9r:RWZi3Yxj"
}

