1.1
Compatibility
Changes
New Features
-
/deepaltsconfigAdmin Command-
Added full support for
/deepaltsconfigwith the following subcommands:/deepaltsconfig status– View plugin state and cache size/deepaltsconfig rebuild– Rebuild the alt graph from IPs (excluding proxy IPs)/deepaltsconfig clearcache– Clear the proxy detection cache/deepaltsconfig save– Force save all plugin data/deepaltsconfig reload– Reload data from disk/deepaltsconfig info– Show detailed statistics and graph metrics
-
Proxy Detection & Filtering
-
Integrated IP-API to detect proxy and hosting IPs:
- IPs marked as proxy or hosting are excluded from graph connections
- Responses are cached for performance and to reduce API calls
- API rate limits (
X-Rl,X-Ttl) are respected to avoid bans
Structural Refactoring
-
Graph logic extracted into its own class (
DeepAltsGraph)- Improves maintainability and future extensibility
- Easier to add new connection logic (e.g. shared usernames, hardware IDs, etc.)
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:gQ09Y3et:YsQB7oPL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gQ09Y3et:YsQB7oPL"
}

