protectcord-forge-1.1.5.jar
Curse Maven Snippet
What's new
π ProtectCord v1.1.5 Released
Release Type: Feature Release
Version: 1.1.5
This update introduces a powerful new Account Per IP Limit system alongside a major performance upgrade to the /checkip API, delivering dramatically faster player connection checks and improved abuse prevention.
π§© Technical Breakdown
First request
- Not cached
- IP history is built
Second request
- Cached via Cloudflare D1 + KV
Cache duration
- Cached for 1 hour
- Automatically refreshed on reuse after expiry
| Request | Expected Response Time |
|---|---|
| 1st | 1,000ms β 2,000ms |
| 2nd+ | 5ms β 50ms |
All other ProtectCord endpoints are already cached via Cloudflare KV and respond almost instantly.
π New Feature: Account Per IP Limit
ProtectCord can now limit the number of Minecraft accounts that may connect from the same IP address at the same time. This helps prevent account stacking, shared-IP abuse, and connection flooding.
π§ Configuration
account-per-ip-limit:
enabled: false
max-accounts: 3
enforcement: "BLOCK" # "BLOCK" or "KICK_OLDEST"
βοΈ Options
enabledβ Enable or disable the feature (default:false)max-accountsβ Maximum allowed accounts per IP (default:3)enforcement- BLOCK β Deny new connections when the limit is reached
- KICK_OLDEST β Kick the oldest session to allow a new connection
β¨ Feature Highlights
- Thread-safe session tracking using
ConcurrentHashMap - Automatic cleanup when players disconnect
- Whitelisted players bypass the limit
- Local/private IP addresses bypass checks
- Custom kick messages with placeholders (
{max},{current}) - Real-time logging of session additions and removals
- No behavior changes when disabled (default)
π¬ Custom Messages
messages:
account-limit-reached: |
&c&lConnection Limit Reached
&7Maximum accounts per IP: &c{max}
&7Current connections from your IP: &c{current}
&7Please disconnect another account before connecting.
account-limit-kicked: |
&c&lYou have been disconnected
&7A new account connected from your IP address.
&7Maximum accounts per IP: &c{max}
π§ Technical Details
β New Classes
SessionInfoβ Stores session data (player name, UUID, connection time)SessionManagerβ Thread-safe IP session trackingPlayerDisconnectListenerβ Cleans up sessions on disconnect
βοΈ Modified Classes
ProtectCordPluginβ Initializes session tracking and listenersConfigManagerβ Added 5 new configuration gettersPlayerConnectionListenerβ Account-limit check runs before API validationconfig.ymlβ New configuration section and messages
π Logic Flow
Player connects β
PreLoginEventFeature enabled & player not whitelisted
SessionManager.canConnect()validates IP usageIf limit exceeded:
- BLOCK β Connection denied
- KICK_OLDEST β Oldest session disconnected
Session added on successful join
Session removed on disconnect
π Performance Impact
- ~130 bytes per session
- O(1) lookups
- Thread-safe synchronization
- Automatic cleanup prevents memory leaks
β‘ Massive /checkip API Performance Upgrade
Weβve pushed a major API update that drastically reduces latency for the /checkip endpoint used by ProtectCord across game servers, websites, and platforms.
π Cloudflare-Powered Caching
- 1st request per IP: ~1,000ms β 2,000ms
- Subsequent requests: 5ms β 50ms
- Up to 200Γ faster after the first check
Once a playerβs IP has been screened, ProtectCord can return safety data almost instantly on future connections β a massive improvement for login systems and VPN/proxy detection.
π Why This Matters
- Faster player logins
- Near-instant VPN & proxy detection after first check
- Reduced server-side login delays
- Stable performance during peak traffic
β Compatibility
- Fully backward compatible with v1.1.0
- Feature disabled by default
- No breaking changes
π Thank you for using ProtectCord This release delivers stronger protection and significantly faster performance across the board.
This mod has no additional files