06
Compatibility
Changes
Changes Made to Address Content Rules:
Removed external API calls: Eliminated ipify.org and ipapi.co geolocation lookups that sent data to undisclosed remote servers Added explicit webcam consent: Webcam capture now requires a separate opt-in dialog (second confirmation screen) after initial system data consent Added server control: New /thelibrary config enablewebcam on/off command allows server admins to disable webcam capture entirely No undisclosed data collection: System info (name, username, computer name) sent only to the game server player connects to - no external APIs
All data collection is now transparent and user-controlled. Complies with Rule 1: "Be designed to upload any data to a remote server... without clear disclosure."
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:UJroP45J:TOvgMZIW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UJroP45J:TOvgMZIW"
}

