DUXPLIMA Documentation

Overview

Every plugin uxmBedrock hooks into and what each turns on.

PluginNeededWhat it turns on
FloodgateYes, on every Paper serverTelling Bedrock players apart, their device, input and layout, forms
GeyserYes, on the server, the proxy or standaloneThe extension: packs per player, items, blocks, heads
PlaceholderAPINoThe placeholders
Nexo, ItemsAdder, Oraxen, CraftEngineNoTheir built packs are converted: items, furniture, blocks, armour, fonts, menu backgrounds
BetterHud, MythicHUD, HappyHUDNoTheir packs are converted and their HUD drawn
CustomNameplates, CustomFishing, LuxDialoguesNoTheir packs are converted
uxmLangNoOne language choice for every UXM plugin
VelocityNoOne pack for the network and proxy command completion, with uxmBedrock-Velocity
ffmpegNo, a program on the machineSmaller sounds

Plugins that protect their pack

Some pack plugins can protect the pack they write so other tools cannot read it. uxmBedrock reads only the built pack; when a plugin's protection keeps it from reading, /uxmbedrock pack report names the plugin, the file and the setting to change.

Plugins built on uxmLib

Menus of UXM plugins already open as Bedrock forms of their own and are not turned into forms again. The choice a player makes with /menus is read by those menus too: a player who chose chests gets chests everywhere.