DUXPLIMA Documentation

Screens

The player list, chat, scoreboard, titles, boss bars, name tags and holograms on Bedrock.

SwitchScreenWhat a Bedrock player gets
tab-listPlayer listTab shows Java's tab: header, footer, names, faces, ping and scores, laid out as on Java
java-chatChatNarrow and low on the screen as on Java, on the PC layout; lines nine units apart in Java's font, players' messages included
scoreboardSidebarPolished lines, blank and repeated lines kept; the score numbers Java does not show are hidden
scoreboard-artSidebarPlaced, spaced and darkened as Java's sidebar, for any number of lines; the title's picture
titlesTitles, subtitles, action bar, boss barsPolished text
name-tagsName tagsGradients, faces and pictures from whatever plugin sets them
hologramsText displaysPolished text

Java's tab

Bedrock's player list takes no header or footer, so the pack replaces it with a screen of its own. Pressing Tab (or the touch button) shows what a Java player sees: the header, the players in Java's order (spectators last, then team and name) with their team prefix and suffix, face, ping and list score, up to 20 a column, then the footer. Blank and repeated header and footer lines are kept. Off, Bedrock players get Geyser's plain list.

Name tags that ride

Java draws no name tag over a player something rides, and name tag plugins such as CustomNameplates draw their tag as a text display riding the player. With name-tags on, such a player shows only the plugin's tag on Bedrock too, at Java's height. A player in a team of the server's keeps the team's own name tag setting.

Blank sidebar lines

Bedrock drops a sidebar line that is empty and shows lines that read the same once. Each such line is sent with a few spaces of its own, so every line of a Java sidebar shows, whether a plugin draws it with scores, teams or packets.

The changes to Bedrock's own screen files are the injection points of gui.conf. Each is a best reading of Bedrock's screen files; when a Bedrock update moves an element, repoint it there.