Repository navigation
Compatibility
Wawel Auth supplies skins; drawing them in the modern format is up to a skin renderer: Salamander, SimpleSkinBackport, or Ears. See Skin rendering for what each combination draws.
Wawel Auth has explicit client-side compatibility for authlib-injector: launcher session import and correct skin resolution.
This is mainly a convenience feature. Wawel Auth already handles multiple Yggdrasil / authlib-injector-compatible providers directly, so authlib-injector is normally unnecessary on Wawel Auth clients. Server-side authlib-injector is not supported.
When Server Utilities is present, Wawel Auth makes Server Utilities player identity handling provider-aware. Team member, ally, moderator, enemy, and ownership operations use UUID/provider-aware player keys instead of relying only on plain names.
Server Utilities player lookups can use player@provider for stable offline targets. Plain names are not guessed when they would be ambiguous.
Server Utilities player head icons and tab-list skin cache use Wawel Auth's provider-aware skin resolver, so skins can resolve through the correct trusted provider.
When Better Questing is present, Wawel Auth makes Better Questing player target resolution provider-aware. Better Questing admin commands, copy-progress commands, and party invite/kick flows can resolve player@provider, with provider-qualified tab completion where applicable.
Better Questing name and party sync packets include provider identity metadata so clients can distinguish players that come from different auth providers.
ArmoredArms 1.3.9 ships its own Wawel Auth integration, written for an older Wawel Auth, which fails when armor is equipped. Wawel Auth turns it off, so ArmoredArms draws the first-person arm with its regular player renderer, where Salamander adds the sleeve.
Model Citizens figures are given a player's name. Wawel Auth finds that player like other plain names, so figures show the skin of the server's player, and Salamander draws them in the modern format.