Tags
Creators
Details
2.4.1+sponge
Compatibility
Changes
Fixed
The address count in the startup log was always the same number.
Every start reported covering 9223372036854775807 addresses, which is Long.MAX_VALUE and reads like a broken counter. It was not arithmetic going wrong: the total saturated on purpose, but a single IPv6 /64 already holds 2^64 addresses, so with the default feeds the guard tripped on the first IPv6 range every time. The figure never moved with its input, which is the giveaway that it was measuring nothing.
There is no combined total any more, because no long can hold one. IPv4 is counted exactly and IPv6 is reported by range:
VPN lists ready: 65295 entries compiled into 36349 ranges.
IPv4: 31078 ranges covering 392968591 addresses. IPv6: 5271 ranges.
The {addresses} placeholder in refresh-done is IPv4 only and both message files say so.
Config files from 2.4.0 work unchanged.
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:nqiuEiMp:ySWrqvct"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nqiuEiMp:ySWrqvct"
}

