
SideGate
SideGate is a Minecraft server plugin that provides a hybrid authentication system for mixed-access environments. Premium players can join normally through Mojang authentication, while administrators may optionally allow specific non-authenticated accounts
Tags
Creators
Details
1.0.1
Compatibility
Changes
SideGate v1.0.1 Changelog
New Features & Enhancements
- Hybrid Auto-Detection System
- Implemented intelligent Mojang API integration. The plugin now automatically verifies if a connecting username belongs to a paid Minecraft account.
- Premium Players: Automatically routed through the standard secure login process (preserving skins and UUIDs).
- Guest/Cracked Players: Automatically redirected to the guest injection protocol without manual intervention.
- Config Option:
auto-detect-premium: true(Enabled by default).
- Premium Override List
- Added a
premium-usernamesconfiguration list. - Allows administrators to manually force specific usernames to be treated as Premium, bypassing the API check. This is useful for staff security or in cases of API downtime.
- Added a
- Performance Optimization
- Introduced
ConcurrentHashMapcaching for API results. This minimizes external HTTP requests and prevents login lag during peak traffic. - Added a cache cleanup mechanism to prevent memory overflow.
- Introduced
Bug Fixes & Stability
- UUID Handling: Refined the logic for detecting Offline UUIDs (Version 3) to ensure guest restrictions are applied correctly only to non-premium players.
- Packet Injection: Improved the stability of the
Login.Client.STARTpacket listener to reduce potential conflicts with other protocol-based plugins.
Configuration Changes
- Added
auto-detect-premium(boolean) to toggle the hybrid detection system. - Added
premium-usernames(list) for manual premium overrides. - Updated default messages to clearer, more professional wording.
Upgrade Instructions: To utilize the new features, please regenerate your config.yml or manually add the new auto-detect-premium and premium-usernames keys to your existing configuration.
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:9Qpsvo2Z:humfm0KZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9Qpsvo2Z:humfm0KZ"
}
