Turning it on
1
Enable it in config.yml
plugins/LodeItems/config.yml
2
Let Geyser show custom items
In Geyser’s
config.yml, set add-non-bedrock-items: true.3
Restart the server
Lode Items writes these files before Geyser starts:
packs/lodeitems.mcpackcustom_mappings/lodeitems_items.jsoncustom_mappings/lodeitems_blocks.json
folder to any folder, then copy its packs/ and custom_mappings/ to the proxy’s Geyser folder.
What Bedrock players get
The Bedrock pack is made from the finished Java pack, so packs merged withpack.merge are included too.
Behaviour is all server-side, so it’s the same for everyone: mining speed, drops, events, mechanics, recipes.
Elytras and mob armour
On Bedrock, only the real elytra can glide, and only vanilla horse armour, wolf armour, carpets and saddles fit on a mob. That is built into those items and can’t be added to a custom one. So custom elytras and mob armour are shown to Bedrock players as their base item (material:): they still glide and fit their mob, with the vanilla look. The console lists these items when it builds.
Menus and optional packs
- The item browser and other menus show their plain look (vanilla icons) to Bedrock players.
- Optional packs are Java only:
/packstells Bedrock players so. Geyser sends the same packs to every Bedrock player.
How props are shown
Geyser can’t draw the display entities props are made of. Instead, each Bedrock player who can see a prop is sent an invisible armour stand (only they see it, and it costs no real entity on the server) wearing the prop’s model.Geyser support hasn’t been tested with a Bedrock client yet. If something looks wrong (a block turned the wrong way, a prop floating or facing away), please report it with a screenshot.
