UnrealIRCd supports third-party modules for extended functionality. atl.chat manages these via a declarative list file and an automated install process during the Docker image build.Documentation Index
Fetch the complete documentation index at: https://docs.allthingslinux.org/llms.txt
Use this file to discover all available pages before exploring further.
Module list
Third-party modules are declared inapps/unrealircd/third-party-modules.list. The file format is:
- One module name per line (e.g.,
third/showwebirc) - Lines starting with
#are comments - Empty lines are ignored
| Module | Purpose |
|---|---|
third/showwebirc | Shows WebIRC/WebSocket information in WHOIS replies |
third/metadata | IRCv3 draft/metadata — avatars, message colouring, status texts |
third/react | IRCv3 draft/react — message reactions |
third/redact | IRCv3 draft/message-redaction — REDACT command for message deletion |
third/relaymsg-atl | atl.chat fork of RELAYMSG for stateless bridging |
Installing modules
Modules are installed during the Docker image build. TheContainerfile reads third-party-modules.list and runs unrealircd module install for each entry:
- Find the module at modules.unrealircd.org
-
Add a line to
apps/unrealircd/third-party-modules.list: -
Rebuild the Docker image:
-
Reference the module in
unrealircd.conf: -
Restart or rehash the server:
Verifying modules
To check which modules are loaded on a running server:Enabling modules
After adding a module to the list and rebuilding, reference it inunrealircd.conf with a loadmodule directive:
metadata module:
relaymsg-atl module for bridge integration:
Related pages
- IRC Stack Overview — UnrealIRCd and Atheme overview
- IRC Configuration — env vars, config templates, and module loading
- IRC Operations — rehash vs restart for module changes
- Bridge Overview — the relaymsg-atl module powers bridge integration