BlueMapWebChat

4.5.3

Fixed

• When chat is hidden from logged-out users, expired or revoked sessions now immediately clear visible chat history, pinned messages, DM/group state, and chat-related modals.
• Connected browsers now receive an auth-expired SSE event when a session expires, is logged out from another tab, or is revoked from web/admin or /bmchat revoke.
• Notification text now strips Minecraft color codes and formatting codes before being sent to browser notifications, mobile/background Web Push, and the local notification inbox.
• Fixed duplicated Discord-to-web messages by de-duplicating Discord events by message ID before publishing them to the web chat.

Changed

• Added a dedicated server notification mode in user notification settings:

  • all — receive all server notifications
  • join-leave — receive only join/leave server notifications
  • off — disable server notifications

• Consolidated browser notification defaults and mobile/background Web Push notification defaults into a single notifications: configuration section.

Migration notes

In 4.5.3, notification category preferences now use notifications.* as the default configuration source.

Previously, browser notification options and mobile/background Web Push options were configured separately under browser-notifications: and web-push.notify-*. These legacy keys are still read for migration and backward compatibility when the new notifications.* values are missing.

Use the following block as the new default notification configuration:

# Browser notifications and mobile/background Web Push notification defaults.
# These server-side allow limits apply to both notification delivery paths.
# Users can still narrow these options in Chat settings.
#
# Legacy browser-notifications.* and web-push.notify-* keys are still read
# when notifications.* is missing, but new configs should use this block.
notifications:
  enabled: true

  # true = notify only when the tab/window is hidden, minimized, or not focused.
  only-when-hidden: true

  notify-normal-chat: true
  notify-dm: true
  notify-group-chat: true
  notify-mentions: true
  notify-replies: true

  # true = allow users to receive server notifications.
  # Users can still choose all, join/leave only, or off in Chat settings.
  notify-system: true

  notify-keywords: true
  notify-own-messages: true
  show-message-preview: true

The following legacy keys are still read only for migration and backward compatibility:

browser-notifications.*
web-push.enabled
web-push.notify-*
web-push.show-message-preview

For new installations and updated configs, move notification category preferences into notifications:.

The web-push: section should now be used only for Web Push transport settings, such as VAPID keys, subject, notification title, subscription file, and TTL.

Existing configs do not have to be rewritten immediately. However, if both notifications.* values and old legacy values are present, the notifications.* values should be treated as the intended configuration. Server owners who want a clean config can replace the old browser notification and Web Push notification preference blocks with the new notifications: block above, then keep only Web Push transport settings under web-push:.