Skip to main content
Tags are Fire’s custom command system, allowing you to create reusable text responses, embeds, and automated replies. This guide covers everything from basic tags to advanced slash command integration.

​
Tag Basics

​
Creating Your First Tag

1

Create a tag

/tag create welcome Welcome to our server! Please read the rules.
2

Use the tag

/tag welcome
# or simply: !welcome (if using prefix commands)
3

List all tags

/tag
# Shows all available tags in the server
Tag Name Requirements: (src/commands/Tags/create.ts:7-8)
  • 1-32 characters
  • Letters, numbers, hyphens, underscores only
  • Cannot match existing Fire command names (e.g., cannot name a tag “ban”)

​
Tag Management Commands

/tag view <name>
# See the raw content without triggering the tag

​
Advanced Tag Features

​
Tag Aliases

Create multiple names for the same tag: 
/tag alias <original-tag> <alias-name>
Example: 
/tag create serverrules Please follow our community guidelines...
/tag alias serverrules rules
/tag alias serverrules guidelines

# Now all three commands work:
# /tag serverrules | /tag rules | /tag guidelines
Aliases don’t count toward your tag limit. Create descriptive aliases to make tags easier to discover.

​
Slash Command Integration

Convert your tags into native Discord slash commands: 
/tag slash
# Toggles slash command mode for tags
When enabled:
  • All tags appear as native Discord slash commands
  • Members see tag suggestions when typing /
  • Better discoverability for new members
  • Professional appearance
Requirements for slash commands:
  • All tag names must be valid (alphanumeric, hyphens, underscores)
  • Fire needs proper permissions
  • There’s a cooldown of 10 minutes between enabling/disabling
Invalid tag names will prevent slash command activation. Fix names first: src/commands/Tags/slash.ts:63-69
Ephemeral Slash Tags: 
/tag slash ephemeral
# Toggle whether tag responses are visible only to the user

​
Delete-on-Tag (dtag)

Automatically delete the command message when using a tag: 
# Use dtag prefix instead of tag
/dtag welcome
!dtag rules

# Your command message is deleted, only tag response remains
Perfect for:
  • Keeping channels clean
  • Info commands in help channels
  • Quick responses without clutter
  • Professional appearance

​
Tag Content Formatting

​
Text Formatting

Tags support full Discord markdown: 
**bold text**
*italic text*
__underline__
~~strikethrough~~
||spoiler||
`code`
```code block```
> quote

​
Mentions and References

# Tags can include:
@User mentions
@Role mentions
#Channel mentions
<:emoji:id> custom emojis
Mentions in tags will actually ping users/roles. Use with caution or consider using escaped mentions: \@Role to display without pinging.

​
Embeds in Tags

Fire tags support embedded content for richer responses. While embeds are created separately, they can be attached to tags for professional-looking messages.
Embeds make tags more visually appealing. Use them for:
  • Server rules and guidelines
  • FAQ responses
  • Welcome messages
  • Information panels

​
Tag Limitations

Free Servers:
  • Maximum 20 tags (src/commands/Tags/create.ts:74-75)
Premium Servers:
  • Unlimited tags
  • Edit tags beyond position 20 in the list
  • Maximum 2,000 characters per tag (src/commands/Tags/create.ts:58-59)
  • Same as Discord’s message limit
  • Embeds don’t count toward this limit
Creating/Editing/Deleting tags:
  • Requires Manage Messages permission
Using tags:
  • Available to all server members
  • Can be restricted by channel permissions

​
Best Practices

​
Naming Conventions

Use Clear Names

Choose descriptive, memorable names:
  • ✅ serverinfo, apply, rules
  • ❌ info1, tag2, xyz

Consistent Style

Pick a naming pattern and stick to it:
  • Lowercase: faqhelp
  • Hyphenated: faq-help
  • Camelcase: faqHelp

​
Tag Organization Strategy

1

Categorize Tags

Group related tags with prefixes:
  • faq-roles, faq-bots, faq-rules
  • apply-staff, apply-partner
  • info-voice, info-premium
2

Create Common Aliases

Add intuitive shortcuts:
  • serverinfo → si, server, info
  • frequently-asked → faq, questions
3

Document Tags

Keep a list of tags for moderators:
/tag list
# Copy to a staff channel for reference

​
Content Writing Tips

Effective Tag Content:
  1. Be concise - Get to the point quickly
  2. Use formatting - Bold key information, use line breaks
  3. Include links - Direct members to relevant resources
  4. Stay updated - Review and update tags regularly
  5. Test thoroughly - Verify mentions, links, and formatting work
Example Well-Written Tag: 
**How to Apply for Staff**

We're always looking for helpful members! Here's how to apply:

1. Be active for at least 2 weeks
2. Have no recent warnings
3. Fill out the form: https://example.com/staff-application

Questions? Ask in #support

​
Workflow Automation

Create quick-answer tags for common questions:
  • howtoticket - Instructions for ticket system
  • reportuser - How to report rule violations
  • boostperks - Server boost benefits
Streamline new member experience:
  • welcome - Welcome message with server tour
  • getstarted - First steps in the server
  • roles - How to get roles
Speed up common mod responses:
  • warned - Explanation after warning
  • slowmode - Why slowmode is enabled
  • locked - Channel lock announcement

​
Tag Monitoring

​
Check Tag Usage

/tag info <name>
Reviews tag information including:
  • Total uses
  • Creator
  • Creation date
  • Last modified
Regularly review tag usage statistics to:
  • Identify most useful tags
  • Find outdated or unused tags
  • Optimize your tag library
  • Update frequently-used tags with better content

​
Maintenance Routine

1

Monthly Review

Check all tags for outdated information, broken links, or deprecated content.
2

Usage Analysis

Use /tag info on each tag to see which are most used. Consider removing tags with zero usage after 3+ months.
3

Content Updates

Update tags to reflect:
  • New server rules
  • Channel changes
  • Role updates
  • Event information

​
Advanced Use Cases

​
Interactive Reply Tags

When you reply to a message while using a tag, Fire will reply to that message: 
# Someone asks: "How do I get verified?"
# Reply to their message with: /tag verified
# Fire replies to them with the verified tag content

​
Multi-Language Support

Create language-specific tags: 
/tag create welcome-en Welcome to our server!
/tag create welcome-es ¡Bienvenido a nuestro servidor!
/tag create welcome-fr Bienvenue sur notre serveur!

​
Template Tags

Create reusable templates for announcements: 
/tag create event-template
**Event Name:** [NAME]
**Date:** [DATE]
**Time:** [TIME]
**Location:** [CHANNEL]

React with ✅ to RSVP!

​
Troubleshooting

Check:
  • Tag name is spelled correctly
  • Tag exists: /tag list
  • Fire has permissions to send messages
  • You’re using the right prefix or slash command
Verify:
  • You have Manage Messages permission
  • Tag name follows naming rules
  • Free servers: You haven’t hit the 20 tag limit
  • Name doesn’t conflict with Fire commands
Ensure:
  • Slash mode is enabled: /tag slash
  • All tag names are valid (alphanumeric, hyphens, underscores)
  • Wait a few minutes for Discord to update
  • Fire has required permissions

​
Next Steps

Premium Features

Unlock unlimited tags and more

Best Practices

Optimize server management

Build docs developers (and LLMs) love

Get started for freeTalk to us