Skip to content

LoginCustom 1.0.0

Latest
Latest

Choose a tag to compare

View all tags
@imstaxdev imstaxdev released this 09 Aug 22:12
v1.0.0
3667433

LoginCustom 1.0.0

LoginCustom 1.0.0 is the first supported stable release for Minecraft 1.21.x and 26.x. It combines secure offline-mode authentication, verified Premium accounts, two-factor authentication, proxy synchronization, Folia support, and production diagnostics in one maintained release line.

Downloads

GitHub release packages:

  • LoginCustom-1.0.0-Minecraft-1.21.x.zip — Java 21
  • LoginCustom-1.0.0-Minecraft-26.x.zip — Java 25
  • SHA256SUMS.txt — checksums for every JAR and package

Each package contains dedicated Bukkit/Spigot, Paper/Purpur, Folia, Velocity, and BungeeCord JARs plus the compile-time public API artifact. Install only the variant matching the process. Proxy networks also require the matching plugin on every backend.

Modrinth provides the platform JARs as separate downloads.

Stable highlights

  • Argon2id password hashing with random salts and a versioned external pepper keyring.
  • Verified Premium linking through Minecraft's official connection handshake.
  • TOTP two-factor authentication with one-use recovery codes.
  • Locally generated 128x128 QR map that is locked temporarily and never replaces player items.
  • Dedicated Folia builds with entity-aware scheduling.
  • SQLite standalone storage and MariaDB network storage.
  • HMAC-signed, expiring, replay-protected proxy sessions.
  • Complete pre-authentication movement, command, chat, inventory, interaction, damage, teleport, vehicle, and server-switch restrictions.
  • Configurable login location through /setlogin and spawn-login.
  • Permission-aware help and tab completion for /logincustom, /lc, /2fa, and destructive confirmations.
  • Encrypted login-address history and authentication-attempt inspection.
  • English, Spanish, Portuguese, and French messages.
  • PlaceholderAPI, public API, lifecycle events, Modrinth update checks, and optional anonymous bStats metrics.
  • /logincustom doctor for storage, security, scheduler, queue, secret, and integration checks.

Security changes

  • MariaDB, HikariCP, Password4j, and bStats are shaded into LoginCustom's private namespace.
  • No SQLite driver classes are bundled in the modern platform JARs.
  • Passwords, TOTP values, recovery codes, shared secrets, and reusable tokens are excluded from audit output.
  • Paper/Spigot command logging is checked before credential commands become available. If LoginCustom disables an unsafe setting on first start, restart the server as instructed.
  • TOTP QR creation is local and sends no enrollment secret to a third-party QR service.
  • Full addresses are AES-256-GCM encrypted; address matching uses HMAC-derived fingerprints.
  • Database or signed-channel failure keeps unauthenticated players blocked.

Upgrading from a beta or development build

  1. Stop every proxy and backend process.
  2. Back up the database and every LoginCustom .key file together.
  3. Remove old LoginCustom JARs.
  4. Install the correct 1.0.0 artifact on every process.
  5. Keep the original password-peppers.key, address keys, database, and network secret.
  6. Start the complete deployment.
  7. Restart once if LoginCustom reports that it corrected unsafe command logging.
  8. Run /logincustom doctor on each backend.
  9. Test one non-Premium login, one 2FA login, and—on a mixed network—one verified Premium login.

Do not create a fresh pepper keyring for an existing database. LoginCustom intentionally rejects a database claimed by a different keyring.

Compatibility notes

  • Minecraft 1.21.x uses Java 21 artifacts.
  • Minecraft 26.x uses Java 25 artifacts.
  • Folia requires LoginCustom-Folia.jar; the Paper artifact is not a substitute.
  • Velocity/BungeeCord Premium mode requires MariaDB, the proxy plugin, backend plugins, correct forwarding, matching signed-session configuration, and network-isolated backend ports.
  • Legacy and Downgrade releases remain archived and are not part of stable 1.0.0 support.

Validation

  • Complete Gradle test suite and both modern assemblies passed.
  • Repeated builds produced identical JAR SHA-256 hashes.
  • Final 1.0.0 Paper JARs started with SQLite on Minecraft 1.21.11/Java 21 and Minecraft 26.2/Java 25.
  • A real MariaDB integration round trip passed for migration, account data, TOTP, recovery codes, and deletion.
  • Folia startup was verified on 1.21.4, 1.21.5, 1.21.6, 1.21.8, 1.21.11, 26.1.2, and 26.2.
  • Modern artifacts were checked for correct bytecode, version descriptors, relocated libraries, and absence of bundled SQLite classes.

Read Installation, Configuration, Security, and Support before production deployment.

Assets 5
Loading