Troubleshooting

Having issues with ScarletHooks? This page covers common problems, error messages, and solutions to help you get your webhooks and configuration working smoothly.

Common Issues & Solutions

1. Messages Not Sending to Webhooks

• Check the webhook URL:
  Make sure the URL is correct and not set to null in your config.
• Webhook service is down or rate-limited:
  Try the URL in your browser or with another tool to verify it works.
• Check for typos:
  Even a small typo in the URL or config key will prevent messages from being sent.
• Restart or reload:
  After changing the config, use .hooks reload settings or restart your server.

2. Clan Webhook Not Working

• Did you create the clan entry via command?
  Use .hooks add <clan-name> or .hooks afp <player-name> before editing ClanWebHookUrls.json.
• Is the webhook URL set in ClanWebHookUrls.json?
  Make sure the entry exists and the URL is correct.
• Did you reload webhooks?
  Use .hooks reload webhooks after editing the JSON file.

3. Settings Not Updating

• Did you reload settings?
  Use .hooks reload settings after editing ScarletHooks.cfg.
• Are you editing the correct file?
  The config should be in BepInEx/config/ScarletHooks.cfg.

4. Placeholders Not Replaced

• Check for typos in placeholder names:
  Use {playerName}, {clanName}, and {targetName} exactly as shown.
• Unsupported placeholder:
  Some placeholders may not be available for all message types.

5. Webhook Rate Limiting or Spam

• Enable batching:
  Set EnableBatching = true in your config.
• Increase MessageInterval:
  Try a higher value (e.g., 0.5 or 1.0) to slow down message sending.

6. Errors or Crashes

• Check the server log:
  Look for errors related to ScarletHooks in the console or log files.
• Missing dependencies:
  Ensure BepInEx and VampireCommandFramework are installed and loaded.

Still Need Help?

• Double-check the Configuration Guide and Webhook Routing & Examples.
• If you believe you’ve found a bug, open an issue on GitHub. with details and your config files.