Skip to content

Common Questions & Issues

Jump to bottom
João Amaro Lagedo edited this page Jun 19, 2026 · 20 revisions

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.

Common Issues

The plugin fails to load, or I get an "unable to resolve assembly" error

  • 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, unblock ACT_DiscordTriggers.dll and node.exe individually.
  • Make sure the whole plugin folder is intact: ACT_DiscordTriggers.dll, node.exe, bundle.js, and node_modules\ must all sit together in Plugins\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.

The bot doesn't come online / the Server or Channel list is empty

  • 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 bot scope (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.log in your ACT data folder) for connection errors, and make sure you're on the latest release.

Windows SmartScreen or antivirus blocks or quarantines the plugin

  • This is the bundled node.exe being flagged because it was downloaded from the internet. Unblock the zip before extracting (see above). If your antivirus quarantined node.exe, restore it and add an exception for the plugin folder.

The bot joins the channel but no one hears anything

  • 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.

FAQ

Do I need to install Node.js?

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.

What is DAVE, and why did the plugin need updating?

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.

How do I choose which triggers go to Discord vs. stay as personal callouts?

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.

Can I use TTS.Yukkuri with this?

No, but recent versions of ACT.Hojoring added Discord support, so if you need TTS.Yukkuri you can use that instead.

Where are the logs?

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.

Clone this wiki locally