Skip to content

ImageEmojis Bero

KOKOTO-DEV edited this page Aug 13, 2026 · 1 revision

ImageEmojis-Bero Integration

BlueMapWebChat can integrate with ImageEmojis-Bero without a hard plugin dependency. BMChat preserves canonical emoji token text in web history, replies, DMs, and server-relay payloads, then uses the receiving server's ImageEmojis runtime mapping when building Minecraft chat components.

What this integration does

  • Preserves tokens such as :pack/name: across web/game/reply/relay paths
  • Reads the current ImageEmojis runtime emoji repository through reflection
  • Converts recognized tokens to the receiving server's current private-use glyphs
  • Keeps clickable BMChat sender/reply/link components where possible
  • Falls back safely when ImageEmojis is absent or a token cannot be resolved

Recommended shared emoji directory

Point ImageEmojis-Bero at BlueMapWebChat's emoji tree so the web UI and Minecraft resource pack use the same files:

# plugins/ImageEmojis-Bero/config.yml
emojisFolder: "/BlueMapWebChat/emojis"
templateFormat: ":<emoji>:"
replaceInCommands: true

The resulting path is under the server plugins directory:

plugins/BlueMapWebChat/emojis/<pack>/<name>.png

Recommended BlueMapWebChat behavior

Preserve the token for Minecraft so ImageEmojis can render it:

emoji:
  game-link:
    enabled: false

reply:
  game-click:
    enabled: true
    local-game-chat: true

replaceInCommands: true is important when users put emoji tokens inside /bmchat reply, /bmchat dm, /w, /msg, or similar commands.

Reload after changing emoji files

  1. Run /emojis reload so ImageEmojis rebuilds its resource pack.
  2. Connected players run /emojis update, or reconnect.
  3. BlueMapWebChat refreshes its short-lived runtime token→glyph cache automatically; a BMChat reload is normally unnecessary for emoji-file-only changes.

Server relay

BMChat relays canonical token text, not another server's private-use glyph. Therefore each receiving server can map the same token to its own current resource pack.

To display the same remote emoji everywhere, synchronize the same pack/name files to every receiving server. The chat relay does not copy resource-pack files.

Optional client-side Picker mod

ImageEmojis-Bero 1.9.1 also provides an optional ImageEmojis Picker client companion. It is not required for BMChat or ImageEmojis rendering, but it gives players a searchable graphical picker and inserts the exact token published by the server resource pack.

Features include:

  • Default F8 key, configurable in Controls
  • Live search by pack, emoji name, or full token
  • Preserves chat draft, cursor, and selection
  • Inserts the chosen token into the current chat input
  • When opened outside chat, choosing an emoji sends the token as a normal chat message
  • Reads assets/imageemojis/emojis.json from the active server resource pack, so the client uses the server's exact token/glyph catalog

See ImageEmojis Client Picker for client installation and compatibility.

Troubleshooting

Token is visible as plain text in Minecraft

  • Confirm the same pack/name exists in ImageEmojis-Bero.
  • Run /emojis reload and update/rejoin clients.
  • Confirm the player has the required ImageEmojis permission/resource pack.

Works in Minecraft but not on the web

  • Confirm the matching image exists under plugins/BlueMapWebChat/emojis.

Command emoji does not convert

  • Keep replaceInCommands: true in ImageEmojis-Bero.

Remote-server emoji does not render

  • Synchronize the emoji pack files to all receiving servers. Relay traffic carries tokens, not the resource-pack assets.

Clone this wiki locally