-
Notifications
You must be signed in to change notification settings - Fork 0
Common Questions & Issues
If the solutions below don't fix your problem, please open an issue on GitHub with screenshots and as much detail as possible — and attach the diagnostics log, ACT_DiscordTriggers-diagnostics.log, from your ACT data folder (%AppData%\Advanced Combat Tracker\). It combines all of the plugin's logs into one file and is the single most useful thing to include.
- Did you follow the First-Time Setup Guide, including the prerequisites?
-
Unblock the zip before extracting — right-click the downloaded
.zip→ Properties → tick Unblock → OK. If you already extracted, unblockACT_DiscordTriggers.dllandnode.exeindividually. - Make sure the whole plugin folder is intact:
ACT_DiscordTriggers.dll,node.exe,bundle.js, andnode_modules\must all sit together inPlugins\ACT_DiscordTriggers\. Don't copy out just the.dll. - When updating, replace the entire folder with the new release — don't swap only the
.dll. All of the bundled files are updated together. - Always restart ACT after adding, removing, or updating plugins. Enabling/disabling is not enough.
- If you use OverlayPlugin, make sure it's the latest fork, not the older ngld or rainbowmage builds.
- Confirm the bot token is entered correctly on the Discord Triggers tab, then click Connect (or enable Auto Connect).
- Make sure the bot was actually invited to your server with the
botscope (see Step 2). A bot that isn't in any server has no servers/channels to list. - The bot only lists voice channels it has permission to View and Connect to — check its role permissions on the server.
- Check the diagnostics log (
ACT_DiscordTriggers-diagnostics.login your ACT data folder) for connection errors, and make sure you're on the latest release.
- This is the bundled
node.exebeing flagged because it was downloaded from the internet. Unblock the zip before extracting (see above). If your antivirus quarantinednode.exe, restore it and add an exception for the plugin folder.
- Make sure the bot has the Speak permission in that voice channel.
- Confirm the trigger is actually configured to play TTS or a sound (test it locally first).
- If you route triggers through Triggernometry, see the FAQ below about which triggers get sent to Discord.
No. Everything the plugin needs is bundled inside the download — including a node.exe file you'll see in the folder, which is what lets the bot connect to Discord voice. You don't have to install anything extra; just keep the whole plugin folder together.
DAVE is Discord's end-to-end encryption for voice, and Discord has made it mandatory for voice channels. The original plugin couldn't speak it, which is what stopped it from working. This fork was rebuilt to support DAVE, so it connects to Discord voice again. There's nothing you need to do differently — it just works.
Yes. On the plugin's Output page, choose This PC (local). All TTS (including the neural ONNX voices) and trigger sounds — with the same effects, auto-leveling, and master limiter — play on your computer's default speakers/headset. No bot, token, or Discord login is needed, and the Discord connection, voice-channel, and audio-quality sections hide themselves in this mode. Local output starts the moment you select it. See Output mode. Switch back to Discord bot any time to share callouts with your party.
The plugin sends a trigger to Discord whenever that trigger plays its audio through ACT. With Triggernometry, go to Triggernometry Settings → Edit Configuration → Audio tab and check the boxes for "Use ACT for playing text-to-speech / audio files", then import your triggers via the Import button. For any trigger you want kept personal, edit it and set the option to override the hook sound to the ACT setting — every trigger except those is routed to the bot.
Full setup for Triggernometry, Triggevent, and ACT's built-in triggers is on the Trigger Software page.
On the Text-to-Speech page you choose a voice engine:
- Windows (SAPI) uses the text-to-speech voices already on your PC. It's fully offline with nothing to download.
- ONNX — neural plays modern neural voices that sound much more natural. Each voice is downloaded the first time you pick it, then runs offline. There are 60+ voices across several languages, split into Fast (Piper — light on CPU) and Natural (Kokoro — most realistic, heavier on CPU).
Full details are on the Settings & Configuration → Text-to-Speech page.
Neural (ONNX) voices have to be downloaded before they can speak. If a voice isn't on your PC yet, the Text-to-Speech page shows a Download button — click it and wait for the progress bar to finish (the voice then shows a ✓). Until a voice is downloaded, callouts using it are skipped. Also remember that Test (and any callout) only plays once the bot has joined a voice channel.
By default they're saved under %AppData%\ACT_DiscordTriggers\models. To put them somewhere else (say a drive with more room), open Text-to-Speech → Advanced → Models folder and click Pick a folder. Voices already in the new location are detected automatically.
Synthesis uses your CPU. On the Text-to-Speech page open Advanced → CPU usage and choose Low · 1 (gentlest while gaming) or Balanced · 2. You can also switch the Quality toggle to Fast (Piper), which is much lighter than Natural (Kokoro).
No, but recent versions of ACT.Hojoring added Discord support, so if you need TTS.Yukkuri you can use that instead.
The plugin keeps an always-on diagnostics log — there's nothing to enable.
-
ACT_DiscordTriggers-diagnostics.log— in your ACT data folder (%AppData%\Advanced Combat Tracker\). This is the one to send when reporting a problem: it combines everything the plugin and bot did into a single, time-ordered file. - The easiest way to find it: on the plugin's Information page, click Open log folder.