1.1.0

New Features

• Per-server key authentication — Servers can now set a server.key in their config. Clients are prompted with a GUI window to enter the key on first join. The key is saved to config/LoginDaddy/serverlist.json and 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 /login step entirely and are released from limbo automatically. Sessions persist across server restarts and are stored in config/LoginDaddy/sessions.json.

Changes

• Config directory moved — logindaddy.properties is now generated at config/LoginDaddy/logindaddy.properties instead of the server root folder. To migrate: just copy your existing logindaddy.properties into the config/LoginDaddy/ folder and everything will work like nothing changed.

• SQLite database moved — logindaddy.db is now created at config/LoginDaddy/logindaddy.db instead of the server root folder. To migrate: copy your existing logindaddy.db into the config/LoginDaddy/ folder alongside the properties file. If you're using MySQL, there's nothing to move.

• New config property — server.key added to logindaddy.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 CommunicationsException and No operations allowed after connection closed errors after the server had been idle long enough for MySQL's wait_timeout to close the connection. The database now validates and reconnects before every operation, and additionally performs a keepalive check after every world save cycle.

1.0.3

Bug Fixes

• Fixed stuck "Loading terrain..." screen when reconnecting after having ridden a boat, horse, or any other entity. Vanilla was saving the vehicle into the player's NBT on disconnect and restoring the passenger relationship before the client finished loading, causing it to hang indefinitely.
• Fixed ghost entity warnings (Fetching packet for removed entity, Duplicate entity UUID) that appeared in logs on every login.

Changes

• Operators can now use commands from ingame.
• Pressing the "Title Screen" button on the death screen now correctly sends a respawn packet before disconnecting, so the server processes the death properly instead of leaving a dead entity behind.
• The Disconnect button in the pause menu is now hidden while the player is in the limbo/authentication phase, preventing players from bypassing the login flow.
• Removed vehicle restore on login. vehicles are no longer saved or restored across sessions.

Minor bug fixes

Now supports fabric loader 0.18.2 and up

DO NOT USE THE 1.0 VERSION! USE THIS VERSION INSTEAD!

1. Fixed a bug that previously made it impossible to play in singleplayer with this mod installed for some people.
2. Fixed a bug that previously made it so you were teleported to the overworld if you died, didn't respawn(letting the death screen active) and rejoining to respawn which led to you teleporting to the overworld with spectator mode!

LoginDaddy

A Fabric mod for private friend servers. Requires players to have the mod installed on their client, be on the whitelist and authenticate with a password before they can play.

How it works

1. Player connects → sent to an invisible limbo dimension
2. Server checks if the client has LoginDaddy installed (handshake). No mod = kicked
3. Server checks if the player is whitelisted. Not whitelisted = kicked
4. Player registers or logs in with a password
5. Player is teleported back to where they joined from

Join/leave messages and tab list are hidden until authentication is complete.

Requirements

• Minecraft 1.21.11
• Fabric Loader 0.18.4+
• Fabric API

Setup

Server

1. Drop the mod jar into your mods/ folder
2. Start the server once to generate logindaddy.properties
3. Edit logindaddy.properties with your database credentials
4. Add players to the whitelist (see commands below)

Client

Players need the same mod jar in their mods/ folder. The client side only handles the handshake — no configuration needed.

Configuration

logindaddy.properties is generated in the server root on first launch.

# sqlite (local file) or mysql
database.type=sqlite

# MySQL only — ignored if using sqlite
mysql.host=localhost
mysql.port=3306
mysql.database=logindaddy
mysql.username=root
mysql.password=

⚠️ Never commit "logindaddy.properties" to version control.

It contains your database credentials.

Commands

All admin commands require the server console (no in-game access).

Player commands (in-game, only usable during authentication):

License

MIT