Tags
Creators
Details
All versions
0.5.26
Release
Jarvis AntiVPN 0.5.26last month 118
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
- An unlinked server keeps telling you it is not protected. Until the connector is linked to your account, it is not protecting your server. The full warning saying so appeared once, at startup, and on a busy proxy it is gone within seconds; after that, each new link came as a bare line in English that did not say it. The full warning now comes back every 10 minutes for as long as the server stays unlinked, and stops by itself once it is linked. It is written in your language: the machine's at first, and the one from your panel account as soon as you open the link.
- Staff see the linking link in game, ready to click. While the connector is not linked, anyone with the
jarvis.adminpermission (server operators, on Paper) gets the same three lines in chat when they join, in the language of their game. At most once every half hour per person, never with a link about to expire, and it stops as soon as the server is linked. The link only goes to premium (online-mode) sessions: without premium a name proves nothing, so staff get the warning and the console keeps the link. A Paper server behind a proxy says nothing in chat, since the connector belongs on the proxy. - Paper: the panel now shows which client each player joins with. On Paper 1.20.4 and newer the game sends this detail earlier than it used to, before the player exists on the server, so the connector never got to see it and nearly every player came up without it. The 0.5.25 change for this detail arriving late did not cover this case. It is now read from Paper itself. Spigot works as before.
- Behind Docker or HAProxy, the per-address limits no longer lock out your players. If the real player address does not reach the server (Docker, HAProxy or a filter without IP forwarding), everyone arrives from the same private address, and the connection-burst and players-per-address limits started turning people away once a few were in. Those limits now only apply to internet addresses. The console warning about IP forwarding is still there: until you fix it, Jarvis cannot see your players' real address.
/antivpn doctorno longer ticks what it has not checked yet. The player IP line came up green before anyone had joined, and the clock line came up green with an offset that had never been measured. Both now stay neutral until there is something to go on, so the report no longer ends in "all good" on a server nobody has joined yet.- And a few smaller fixes. Updating is replacing the jar and restarting, with no config changes. Same requirements as 0.5.25: Velocity 3.x and 4.0, BungeeCord, Paper / Spigot / Folia, Java 17 or newer.
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:EIYSaVwb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HTRGHm9r:EIYSaVwb"
}

