> For the complete documentation index, see [llms.txt](https://nodemods.gitbook.io/nodemods-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nodemods.gitbook.io/nodemods-docs/event-guard/discord.md).

# Discord Integration

## Overview

Event Guard provides comprehensive Discord integration through webhooks, allowing you to monitor your server's security in real-time.

## Webhook Setup

### Creating Webhooks

1. In Discord:
   * Open your server settings
   * Navigate to Integrations > Webhooks
   * Create New Webhook
   * Name it appropriately (e.g., "Event Guard Errors", "Event Guard Bans")
   * Copy the webhook URL
2. In `server-config.lua`:

```lua
local webhookUrls = {
    errors = "your-error-webhook-url",
    cheaterActions = {
        log = "your-detection-webhook-url",
        ban = "your-ban-webhook-url"
    }
}
```

## Log Types

### Error Logs

* Script errors
* Configuration issues
* System warnings

### Cheat Detection Logs

* Detailed ban reasons
* Player information
* Event data
* Event tampering attempts
* Salt manipulation
* Heartbeat failures

## Webhook Message Format

Each webhook message includes:

* Title with action type
* Player details (name, ID, ping)
* Event information
* Timestamp
* Color coding for severity

## Best Practices

1. **Channel Organization**:
   * Create separate channels for different log types
   * Use channel permissions to restrict access
   * Set up notification rules
2. **Webhook Security**:
   * Keep webhook URLs private
   * Store URLs in server-side config only

## Custom Integration

You can customize the


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nodemods.gitbook.io/nodemods-docs/event-guard/discord.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.