Documentation
Back to tutorials

Customization

Server Emojis

Reuse this server's Discord emojis as icons across packs, builds, requirement pages, and scheduling templates instead of relying on generic icons.

Who uses it

Guild managers and staff who curate packs, templates, and requirement pages

Where it lives

Dashboard > Server Emojis

Goal

Staff can register a Discord emoji as a GearCheck emoji, tell native emojis apart from custom ones, and keep a readable fallback everywhere the emoji shows up.

Before You Start

  • Manage Server permission in Discord, since registering or uploading emojis changes server assets.
  • GearCheck installed in the server you're managing.
  • A Discord emoji already uploaded to the server, if you plan to register one instead of uploading a new file.

Steps

1

Sync existing Discord emojis

Open Dashboard > Server Emojis and use Sync Discord Emojis to pull every emoji already uploaded to this server into GearCheck's emoji library. Sync only reads emojis that already exist; it does not create new ones.

2

Upload a new emoji

If the emoji doesn't exist in Discord yet, use Upload to Discord instead. GearCheck creates the emoji on the server through the bot first, then adds it to the library. PNG, JPEG, GIF, and WebP files up to 256 KiB are supported.

3

Register an existing emoji by reference

Already have the emoji's markup or ID? Paste it under Register Existing Emoji. GearCheck verifies the emoji belongs to this server before adding it to the library.

4

Pick it wherever GearCheck shows an icon

Once an emoji is registered, it appears in the icon picker for pack artwork, build categories, requirement page labels, and scheduling role templates, so your packs and templates can match the visual language your server already uses.

5

Give it a readable fallback

Add a readable fallback such as :fire_staff: to every emoji. Shared templates, marketplace exports, and any surface that can't render the raw emoji fall back to this text instead of showing nothing. The Emoji Library's Custom and GearCheck Native tabs and Uses count help you track what's registered and where it's used.

Launch Checklist

  • The emoji shows up under the Custom tab of the Emoji Library, not just in Discord.
  • The emoji has a readable fallback, so a shared template or exported requirements page still makes sense without it.
  • The Uses count matches where you expect the emoji to appear (pack icons, categories, requirement pages, scheduling roles).
  • No emoji still in use shows the Unavailable badge.

Common Pitfalls

  • Deleting or renaming the source emoji in Discord, which breaks any GearCheck emoji built from it.
  • Skipping the fallback text, so a shared template or exported requirements page shows nothing where the emoji used to be.
  • Uploading a file that doesn't meet the format or size limit instead of checking PNG/JPEG/GIF/WebP and 256 KiB first.

Related