Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 months ago
Updated 2 months ago
All versions
1.0.1
Release
1.0.15 months ago 35
Uploaded by
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
- Hardened fallback texture proxy redirects so they can't reach localhost or private network targets
- Fixed trusted nginx client IP handling for join/hasJoined without trusting spoofed forwarded headers from public clients
- Added app-level rate limiting for admin login and Yggdrasil auth endpoints
- Removed admin session cookie auth and tightened HTTPS detection behind local proxies
- Bounded public fallback profile and texture proxy caches so high-cardinality requests can't grow memory forever
- Hardened animated GIF cape validation without breaking optimized GIF subframes
- Added same-port HTTPS for admin login when you do not have a separate reverse proxy port
- Exposed same-port HTTPS settings in the admin panel with bounded TLS handshake timeout
- Hardened texture resolving and caching to avoid stale skin/cape state and race-condition bugs
- Reused FentLib's shared player face renderer for client account heads
- Replaced automatic orphaned local provider cleanup with an opt-in prompt on server delete to avoid wiping providers shared across Minecraft instances
- Improved local Wawel Auth credential detection and added configurable credential hiding for unsupported providers
- Improved the public site and admin panel
- Added 67minecraft publishing and filled in Modrinth/CurseForge metadata
- Moved server.dat backups to config/wawelauth/backups
- Force player skull rendering to go through Wawel Auth instead of Et Futurum, when installed
Supplementary resources
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:LncX1fVM:yDHTvOys"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LncX1fVM:yDHTvOys"
}

