Star ✨ on GitHub

Troubleshooting

The fastest way to diagnose the most common Moonlink + voice issues.

When something doesn’t work, don’t guess — narrow it down.

This checklist is ordered from “most common” to “less common”.

1) The bot doesn’t respond to commands

  • Did you set the correct prefix?
  • Did you enable Message Content Intent (Portal + code)?
  • Is the bot reading messages in that channel?

2) The bot joins voice but no audio plays

This is almost always one of these:

  • Your node is not reachable (wrong host/port/firewall).
  • Wrong node password.
  • You forgot voice packet forwarding (rawpacketUpdate) when not using a Connector.

Quick checks

  • Ensure you see a node ready/connected log.
  • Turn on debug: true and read the Moonlink debug output.

3) Players randomly die / disconnect

  • Check your node’s CPU/memory.
  • Enable avoidUnhealthyNodes and set thresholds.
  • Enable autoMovePlayers so failover can happen.

4) Node selection feels wrong

If you have multiple nodes:

  • Confirm selectionStrategy in config.
  • If you want predictable routing, use priority strategy and set each node’s priority.

5) What to log (minimum)

For a clean but useful production log stream:

  • nodeConnect, nodeDisconnect, nodeError
  • playerSwitchedNode
  • socketClosed (voice-level failures)