Skip to main content

Emoji

Standard emoji and shortcuts​

Edit config/emoji.js:

OptionEffect
categoriesSet a category to false to hide it from the picker.
onlyEmpty array adds no restriction; otherwise list the emoji and variants to offer. Category and exclusion filters still apply.
excludeEmoji to remove from the picker and its shortcuts.
aliasesAdditional :name: shortcuts mapped to Unicode emoji.

To add :approved:, insert this entry into the existing aliases object:

approved: '👍'

Use 1–96 lowercase letters, digits, underscores, or hyphens for alias names. Keep the comma between neighbouring entries. The emoji must remain enabled by your category, only, and exclude settings.

For a limited selection, set only: ['😀', '👍', '❤️']. These settings control selection and shortcuts; they do not block Unicode emoji pasted into messages or received from other resources.

Emoji names in tooltips follow Config.Locale. The picker search and :name suggestions accept English, Polish, and the configured language.

Apply changes with restart f5_chat.

Custom image emotes​

  1. Add a PNG, WebP, or GIF directly to web/emotes/, for example coffee.png.
  2. Use a filename of 1–32 lowercase letters, digits, hyphens, or underscores, starting with a letter or digit. Keep the extension lowercase.
  3. In the server console, run:
refresh
restart f5_chat

The image appears in the Custom category and is available as :coffee:. No manual list or manifest entry is required. Run the same commands after replacing or removing files.

Recommended image size: 128 × 128 px, with a transparent background where appropriate. Defaults allow 128 custom emotes and 512 KiB per file. Change these limits through Config.MaxEmotes and Config.MaxEmoteBytes in config/config.lua; MaxEmotes = 0 disables custom emotes.

Keep filenames unique. A custom emote takes precedence over a standard alias with the same name. If it does not appear, check the filename, actual image format, file size, configured limits, and that both console commands were run.