Fix Java player skins not rendering on Bedrock when texture signature is absent

[rozqn]

Problem

PlayerEntity's GameProfile constructor calls profile.getTextures(true), which requires a valid texture signature. Every other texture call site uses false:

• skin/SkinManager.java → profile.getTextures(false)
• entity/type/player/AvatarEntity.java → profile.getTextures(false)

When a player's textures property has no signature (signature=null), getTextures(true) throws, the catch sets textures = null, and that player renders as the default (Steve) skin for Bedrock viewers.

This reproduces consistently on Minecraft Java 26.2 (tested via the #6452 preview build): Java players' profiles arrive with the texture value present but signature=null, so all Java players show as default skins to Bedrock players.

Debug log:

Error loading textures for player! GameProfile{name=..., properties=[Property{name=textures, value=<valid skin+cape>, signature=null}]}

Fix

Use profile.getTextures(false) in PlayerEntity, matching the other call sites. The skin/cape URLs are still present and usable without signature verification.

Testing

Built and ran on a Paper 26.2 server with Geyser + Floodgate. Java players' skins and capes now render correctly for Bedrock players.

[Tim203]

This is intentional, unless the method throws an exception that we don't catch.
This looks unlikely though, given that you provided a debug log with the exact message that would be logged when it was catched properly.
Players need to have a skin texture that's signed by Mojang, this is what a vanilla Minecraft client does too.
Are you using a modified client, or am I missing something here?