How ent0248/zenithproxy_3c3u_ofline_repair works
ZenithProxy’s documented purpose is to repair offline-account login on servers that accept both premium and offline accounts. The sampled runtime centers on Authenticator: it selects offline profile creation or configured Java authentication, manages a persisted authentication cache, and refreshes cached credentials in the background. Device-code login can emit an event and optionally open a browser. The excerpt does not show the proxy’s broader connection flow or the implementation of createMinecraftProtocol, so those links are omitted.
Main entry points: Authenticator.java Authenticator
Components 9
Account Login
- Authenticator
Authenticator.java - Offline Profile
Authenticator.java - Java Auth Manager
Authenticator.java
Auth Cache
- Auth Cache File
Authenticator.java - Token Refresh
Authenticator.java
Device Login
- Device Code Handler
Authenticator.java - Login Event
Authenticator.java - Web Browser Helper
Authenticator.java
Other components
- Proxy Operator
Connections 8
- Authenticator → Offline Profile: creates profile
Authenticator.java - Authenticator → Java Auth Manager: starts configured login
Authenticator.java - Authenticator → Auth Cache File: loads cache
Authenticator.java - Java Auth Manager → Auth Cache File: saves session
Authenticator.java - Token Refresh → Auth Cache File: loads and saves
Authenticator.java - Token Refresh → Java Auth Manager: refreshes credentials
Authenticator.java - Device Code Handler → Login Event: posts event
Authenticator.java - Device Code Handler → Web Browser Helper: optionally opens
Authenticator.java