Links
Tags
Creators
Details
1.1.0
Compatibility
Required content
Changes
1.1.0
New Features
-
Per-server key authentication — Servers can now set a
server.keyin their config. Clients are prompted with a GUI window to enter the key on first join. The key is saved toconfig/LoginDaddy/serverlist.jsonand reused automatically on subsequent joins. If the server key changes, the client is prompted again to enter the new one. -
Session caching — Players who have successfully logged in are remembered by IP for 48 hours. On rejoin, if their IP and username match a valid session, they skip the
/loginstep entirely and are released from limbo automatically. Sessions persist across server restarts and are stored inconfig/LoginDaddy/sessions.json.
Changes
-
Config directory moved —
logindaddy.propertiesis now generated atconfig/LoginDaddy/logindaddy.propertiesinstead of the server root folder. To migrate: just copy your existinglogindaddy.propertiesinto theconfig/LoginDaddy/folder and everything will work like nothing changed. -
SQLite database moved —
logindaddy.dbis now created atconfig/LoginDaddy/logindaddy.dbinstead of the server root folder. To migrate: copy your existinglogindaddy.dbinto theconfig/LoginDaddy/folder alongside the properties file. If you're using MySQL, there's nothing to move. -
New config property —
server.keyadded tologindaddy.properties. Leave it empty to disable the key requirement entirely.
Bug Fixes
-
Fixed players being returned to the limbo dimension after re-joining. The limbo dimension (
logindaddy:limbo) was being persisted to the database on disconnect and then loaded back as the return destination on the next join. The saved dimension is now always sanitized before writing to or reading from the database. -
Fixed MySQL connection drops causing
CommunicationsExceptionandNo operations allowed after connection closederrors after the server had been idle long enough for MySQL'swait_timeoutto close the connection. The database now validates and reconnects before every operation, and additionally performs a keepalive check after every world save cycle.
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:Eqa79iIC:wC3U45kq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Eqa79iIC:wC3U45kq"
}

