Основное сообщение темы
Reliable game launches with the current Launcher
Authenticated game launches receive the session token through standard input, and profile publication remains compatible with the current Launcher revision.
Game launch authentication
Session-token channel compatibility
The managed Authlib injector accepts the legacy --accessToken 0 placeholder with one valid session-token channel and replaces it in memory with the token delivered through standard input. Actual bearer tokens and duplicate arguments remain rejected.
Для пользователя: Authenticated launches can complete injector setup without exposing the session token in launch arguments.
Launcher compatibility
Catalog-free profile publication
This isolated production hotfix excludes signed Launcher mod-catalog snapshots and their revision-6 requirement. Dashboard mod-catalog functionality remains available.
Для пользователя: Profiles can still be published for the current revision-5 Launcher without requiring a coordinated Launcher upgrade.
Verified production predecessor
The signed additive database migration is bound to the deployed Backend v0.0.3.82 release and its verified database baseline.
Для пользователя: The game-launch fix uses the normal guarded production upgrade path.
Java presets
Clearer Russian names for built-in presets
The built-in G1 and ZGC preset names and descriptions are clearer in Russian; exact legacy built-in draft values are normalized when read, while customized preset text is preserved.
Для пользователя: Russian-speaking users can more easily understand the built-in Java presets without losing their custom draft text.