Skip to content

Trigger Software

Jump to bottom
João Amaro Lagedo edited this page Jun 19, 2026 · 1 revision
ACT Discord Triggers mascot

This plugin doesn't create triggers of its own — it takes the callouts your existing trigger software already makes and plays them through the Discord bot, so your whole party hears them. This page explains how to set that up with the three trigger systems it works with:

✅ First, make sure the bot is in a voice channel. None of this reaches Discord until you've connected the bot and pressed Join Channel on the Discord Triggers tab — see the First-Time Setup Guide. While the bot is in a channel, triggers are routed to Discord; after you Leave Channel, they go back to playing only on your own PC.

🧩 How it works (the one rule)

The plugin works by taking over ACT's own "play text-to-speech" and "play sound" functions while the bot is in a voice channel. That means there's a single rule that covers every trigger tool:

Any trigger that plays its audio through ACT is automatically sent to Discord.

So the whole job is just telling your trigger software to route its audio through ACT instead of playing it on your own computer. How you do that depends on which tool you use — see the relevant section below. You can use more than one at the same time; anything that ends up playing through ACT is picked up.

🎯 ACT Custom Triggers (built-in)

ACT's own triggers (the Triggers tab in ACT) already play through ACT, so there's nothing extra to configure — once the bot is in a voice channel, their text-to-speech and sounds go to Discord automatically.

The only limitation is the sound format: ACT's built-in trigger interface only lets you attach .wav files. If you want MP3/OGG/FLAC sound effects, use Triggernometry or Triggevent instead (see Supported audio formats).

🔧 Triggernometry

Triggernometry is an ACT plugin, so it runs inside ACT alongside this one. You tell it to hand its audio to ACT:

  1. Install Triggernometry (download its release and add it on ACT's Plugins tab, the same way you added this plugin).
  2. On the Triggernometry tab, open Settings → Edit Configuration → Audio tab.
  3. Tick both boxes:
    • Use ACT for playing text-to-speech
    • Use ACT for playing audio files
  4. Bring your triggers in with the Import button on the Triggernometry tab (choose the option to import your existing triggers).

That's it — your Triggernometry callouts now play through ACT, and from there to the Discord bot.

Keeping some callouts personal

Want a few triggers to stay only on your PC (not sent to the party)? Edit that trigger and set its option to override the hook sound to the ACT setting. Every trigger except the ones you mark personal will be routed to the bot.

🛰️ Triggevent

Triggevent (by xpdota — source) is a separate application, not an ACT plugin. It talks to ACT over OverlayPlugin's WebSocket, and that same connection is how it hands its callouts to ACT for the bot to pick up.

Prerequisite: OverlayPlugin WebSocket

Triggevent needs OverlayPlugin's WebSocket server running in ACT (this is how Triggevent connects to ACT in the first place):

  1. Install OverlayPlugin in ACT (use the latest fork).
  2. Start OverlayPlugin WSServer from within ACT (on the OverlayPlugin tab). Triggevent's default address, ws://127.0.0.1:10501/ws, matches this out of the box.

Route Triggevent's audio through ACT

In Triggevent, open its settings and find the Websocket tab (under the advanced/connection settings):

  1. Confirm it shows Connected to ACT. If not, check the OverlayPlugin WS URI and that the WSServer is running.
  2. In the TTS and Sound area, enable:
    • Use OP WebSocket for TTS (also labelled Enable TTS) — this sends spoken callouts to ACT. On by default.
    • Use OP WebSocket for Sound (also labelled Enable Sounds) — this sends sound-file callouts to ACT. ⚠️ Off by default — turn it on if you want sound effects in Discord, not just TTS.

With those enabled, Triggevent sends its callouts to ACT, the plugin catches them, and the bot plays them in your voice channel.

💡 Fallback options. Triggevent also has "Local TTS as Fallback" and "Local Sound as Fallback" settings. These let it fall back to playing on your PC if it can't reach ACT — handy as a safety net, and they don't cause callouts to play twice when ACT is connected.

❓ Nothing reaching Discord?

  • Is the bot actually in a voice channel? Press Join Channel on the Discord Triggers tab — routing only happens while it's connected.
  • Did you enable the "play through ACT" option in your trigger tool (the steps above)? If audio still plays only on your PC, that toggle is off.
  • For Triggevent, make sure OverlayPlugin WSServer is running and Triggevent shows Connected, and that Use OP WebSocket for Sound is on (it's off by default).
  • Test a trigger locally first to confirm it makes a sound at all, then check the Common Questions & Issues page.

🔗 Related pages

Clone this wiki locally