Message tags

Message tags communicate additional details in an IRC protocol message, such as the services account a user is using. End-users typically do NOT see the actual raw message tags in their client, but their IRC client can use them to display additional useful information (eg: registered account status, history playback, etc) or make better decisions (eg: if the user is trusted, should be auto-banned, etc).

Technical information
A JOIN looks like this in regular IRC protocol: If a client has enabled message tags and other capabilities it may look like this instead:

Clients need to indicate support for receiving message tags, either by a specific CAP (such as ) or by indicating support in general for message tags.

The general rules on message tags parsing are described in https://ircv3.net/specs/extensions/message-tags.html

Supported message tags
UnrealIRCd supports the following message tags:

Changelog
Changes between UnrealIRCd versions (in chronological order):
 * label: In UnrealIRCd 5.0.0, 5.0.1 and 5.0.2 the tag was, and the capability was  . This because the specification was still in draft at that time. Starting with UnrealIRCd 5.0.3 the draft/ prefix was dropped.
 * unrealircd.org/userhost: added in UnrealIRCd 5.0.3
 * unrealircd.org/userip: added in UnrealIRCd 5.0.3
 * +typing: added in UnrealIRCd 5.0.5
 * draft/bot: added in UnrealIRCd 5.2.0
 * +draft/reply: added in UnrealIRCd 5.2.0
 * unrealircd.org/json-log: added in UnrealIRCd 6.0.0
 * unrealircd.org/geoip: added in UnrealIRCd 6.0.4
 * bot: added in UnrealIRCd 6.0.4.2 (in addition to existing draft/bot, which will be removed at a later point)

Support for other message tags
In UnrealIRCd every message tag, including client message tags, need to have a message tag handler, usually added via a module. See FAQ: How can I allow other message tags?.