?
Host a serverModrinth App
Sign in
ModsResource PacksData PacksShadersModpacksPluginsServers
Settings
BlueMapWebChat (BMWC)

BlueMapWebChat (BMWC)

BlueMap/standalone web chat for Bukkit/Paper/Spigot servers with game↔web chat, DMs, groups, server relay, DiscordSRV, media, emoji, notifications, and admin tools.

62downloads
3followers
62downloads
3followers

Compatibility

Minecraft: Java Edition

26.2
26.1.x
1.21.x

Platforms

Links

View source Visit wiki

Tags

Creators

Details

Licensed MIT
Published 3 weeks ago
Updated 8 hours ago

BlueMapWebChat

Chat screen

BlueMapWebChat is a server-side web chat plugin for Bukkit/Paper/Spigot-compatible Minecraft servers. Run it inside BlueMap, as a standalone web chat page, or use both at the same time. No client mod is required for the core chat features.

Highlights

  • Two-way game ↔ web chat with linked Minecraft accounts and optional guest chat
  • BlueMap addon + standalone /chat page with dark/light/high-contrast UI, PIP, draggable/resizable windows, search, replies, pins, and virtual scrolling
  • 1:1 direct messages with local and cross-server recipients, exact server+UUID routing, retry-safe delivery, unread/read state, and shared game/web threads
  • Group chat rooms with public/private visibility, invitations, passwords, retention limits, unread counts, delivery retry protection, and member management
  • Signed server-to-server relay for multi-server communities, including full-mesh or hub layouts, HMAC authentication, hop limits, deduplication, server badges, and source filters
  • DiscordSRV integration plus Discord media caching and optional emoji-link augmentation
  • Uploads and rich previews for images, video, audio, YouTube/Shorts, with optional TikTok and X/Twitter embeds
  • Custom emoji management and optional ImageEmojis-Bero compatibility without a hard dependency
  • Web Push / keyword notifications and administrator update notifications
  • Administration and moderation tools for message hiding, pins, guest/IP mutes, session revocation, custom emoji management, and private-chat metadata
  • Optional read-only DM and group-chat body audit for explicitly allowlisted super administrators; both are disabled by default and every audit page read is logged
  • Built-in UI languages: English, Korean, Japanese, Simplified Chinese

Private messaging and delivery reliability

Cross-server DM targets are identified by server ID + player UUID, so a local player cannot be confused with a same-name player on another server. Remote messages stay pending until the destination confirms storage. Failed or uncertain sends can be retried with persistent relay/client message IDs without duplicating sender or receiver records.

DM and group-chat message state is shown compactly beside the timestamp. Normal successful delivery is silent; pending or failed delivery is shown only when needed. DM messages use a short unread label until the recipient reads them, then show ✓. Group messages show the number of recipients who have not read the message and change to ✓ when everyone has read it.

Multi-server relay

The optional relay supports public chat and private DM routing between multiple BlueMapWebChat servers. Relay requests are HMAC-SHA256 signed and include replay protection, timestamp validation, relay-ID deduplication, hop limits, and origin tracking. Direct and hub topologies are supported.

For cross-server DM delivery/read acknowledgements, every participating server should run the same current BlueMapWebChat release.

Administrator private-chat audit

Private message bodies are not automatically exposed to normal administrators. Optional audit access requires an exact Minecraft name/UUID in private-chat-super-admins and the corresponding feature switch:

direct-message:
  admin-audit:
    enabled: false

group-chat:
  admin-audit:
    enabled: false

Audit views are read-only. Group audit does not join the room or affect read/unread state. Every audit page read records the actor and pagination metadata without copying message bodies into the audit log.

Deployment

Fresh configurations start with the plugin master switch disabled so operators can review storage, authentication, uploads, retention, and web exposure before enabling it. Existing config.yml files are never overwritten. When the configuration review marker is old or missing, BlueMapWebChat creates a copy-ready config-migration-<version>.yml fragment instead.

For public deployments, placing BlueMap and BlueMapWebChat behind HTTPS with Caddy or Nginx is recommended.

Optional integrations

See the bundled README and docs/ directory for full configuration, reverse-proxy, relay, security, migration, and troubleshooting guides.