Documentation
Back to tutorials

Customization

Custom Messages

Customize approved Discord-facing GearCheck messages without breaking buttons, evidence prompts, scoring, or review logic.

Who uses it

Managers and staff who own server tone

Where it lives

Dashboard > Custom Messages

Goal

Server-specific message copy that still preserves GearCheck's required workflow text and merge fields.

Before You Start

  • Message-template management permission.
  • A clear idea of the tone your guild wants.
  • A test thread where you can preview a real workflow.

Steps

1

Choose a governed surface

Start with surfaces GearCheck exposes for customization, such as dashboard copy, upload instructions, or result-summary helper text. Do not expect raw custom embeds for workflow-critical areas.

2

Keep required fields

Some templates require fields such as default instructions or default body. Those fields preserve evidence requirements, buttons, and operational meaning. If the page warns that a field is missing, fix it before saving.

3

Preview before saving

Use preview data to check how the message reads for a normal member. Look for confusing tone, missing evidence instructions, or raw IDs where names should appear.

4

Test in Discord

Run a real gearcheck flow after saving. Confirm buttons still appear, evidence prompts are still accurate, and score/review language remains canonical.

Launch Checklist

  • Preview renders without validation warnings.
  • Discord message still includes the required evidence instructions.
  • Buttons/select menus still appear and work.
  • Reset to default is available if the custom text confuses members.

Common Pitfalls

  • Removing required default copy because it feels repetitive.
  • Putting policy decisions in a custom message instead of the build settings.
  • Using custom emoji that only works in one guild without a readable fallback.

Related