Skip to content

Common Questions & Issues

Jump to bottom
jlagedo edited this page Jun 17, 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 — including the plugin's log file, DiscordBridge.log (written next to node.exe in the plugin folder).

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. The plugin and the bundled Node runtime 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 restart ACT.
  • 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 DiscordBridge.log in the plugin 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. A node.exe runtime is bundled inside the release. Voice runs in that separate process so the plugin can support Discord's DAVE end-to-end encryption while ACT keeps loading the plugin on .NET Framework. Just keep the whole plugin folder together.

What is DAVE, and why did the architecture change?

In early 2026 Discord began enforcing DAVE (end-to-end encryption) for voice. The library version that supports DAVE dropped .NET Framework support, but ACT only loads .NET Framework plugins — so the old in-process voice path could no longer work. This fork moves voice into a bundled Node.js bridge, which keeps the plugin compatible with ACT while staying current with Discord. Full design notes are in the repo's CLAUDE.md.

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

Use Triggernometry. After installing it, 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 existing triggers via the Import button in the Triggernometry tab (choose the option to import existing triggers). 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 marked personal will be routed to the bot.

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?

  • DiscordBridge.log — the Node bridge log (voice/Discord connection), in the plugin folder next to node.exe. This is the most useful one for connection issues.
  • The plugin also surfaces log lines in ACT itself; include both when reporting a bug.

Clone this wiki locally