1
Compatibility
Changes
Plugin Functionality Automatic IP Binding: Upon a player's first login to the server, their UUID (unique identifier) and IP address are automatically stored in the ipdata.yml file. This ensures seamless IP registration without requiring any action from the player. IP Verification on Login: Each time a player logs in, the plugin compares their current IP address with the one stored in ipdata.yml. If the IP does not match, the login is denied, and the player receives a customizable error message (default: "§cYour IP does not match the registered IP for this account!"). This protects accounts from being accessed from unrecognized devices or networks. IP Unbinding Command: The plugin provides the /ipdel <player_name> command, accessible only to server operators. This command removes the IP binding for the specified player, allowing them to log in from a new IP on their next attempt. Command-related messages (e.g., success, error, or no binding found) are fully customizable. Customizable Messages: All plugin messages are stored in the lang.yml file, which is generated in the plugins/IPLock/ folder on first startup. Messages support Minecraft color codes (§) and placeholders (e.g., {player} for the player’s name, {error} for error details). Examples of customizable messages: Login error: "§cYour IP does not match the registered IP for this account!". Successful unbinding: "§aIP binding for {player} has been removed!". Command error: "§cUsage: /ipdel <player>". Administrators can edit lang.yml to modify text, language, or style without rebuilding the plugin.
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:G37Mnsq5:OzvWqMmf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:G37Mnsq5:OzvWqMmf"
}
