1.1.3
Compatibility
Changes
Version: 1.1.3 Release Type: Major Feature Update & Critical Bug Fix
Critical Fixes - bStats Metrics Collection
Fixed:
-
bStats Data Collection - Fixed plugin disabling itself before bStats could send metrics
- Previously: Plugin called
disablePlugin(this)when API key missing - This caused: Plugin to shutdown before bStats sent data to server
- Result: Missing installation data on bStats dashboard
- Fix: Removed
disablePlugin()call, plugin now stays enabled but inactive - Impact: All installations now tracked, regardless of configuration status
- Previously: Plugin called
-
bStats Server Detection - Folia now properly tracked on bStats
- Uses plugin ID 24623 (shared with other platforms)
- bStats built-in "Server Software" chart automatically detects "Folia"
- No need for custom platform chart - bStats handles it natively
- Impact: Folia shows up correctly as "Folia" in Server Software statistics
-
bStats Custom Charts - Added Minecraft version tracking
- Added "minecraft_version" chart showing MC version breakdown (1.8-1.21)
- Better analytics for understanding version distribution
- Helps identify which Minecraft versions are most popular
New Features - Account Per IP Limiting
This release introduces a comprehensive system to limit the number of Minecraft accounts that can connect from the same IP address simultaneously, with full Folia thread-safety.
New Features:
- Account Per IP Limit - Limit simultaneous connections from the same IP address
- Configurable maximum accounts per IP (default: 3)
- Two enforcement modes: BLOCK or KICK_OLDEST
- BLOCK mode: Prevents new connections when limit reached
- KICK_OLDEST mode: Automatically kicks oldest session to allow new connection
- Whitelisted players automatically bypass limit
- Disabled by default for backward compatibility
- FOLIA-SAFE: Thread-safe session tracking with ConcurrentHashMap
- FOLIA-SAFE: Synchronized methods for atomic operations
- Local/private IPs bypass tracking (127.0.0.1, 192.168.x.x, etc.)
Configuration:
# Account Per IP Limit
account-per-ip-limit:
enabled: false
max-accounts: 3
enforcement: "BLOCK" # "BLOCK" or "KICK_OLDEST"
# New messages
messages:
account-limit-reached: |
&c&lConnection Limit Reached
&7Maximum accounts per IP: &c{max}
&7Current connections from your IP: &c{current}
account-limit-kicked: |
&c&lYou have been disconnected
&7A new account connected from your IP address.
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:y05wfnBZ:Zy58hGC9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y05wfnBZ:Zy58hGC9"
}

