error¶

Something went wrong — here's what happened.

What is it?¶

error contains information about a failure that triggered an error-handling command. It's your bot's "incident report" — what broke, when, and (sometimes) why.

In normal commands, error is null. Everything is fine. Nothing to see here.

It only shows up in two special places: the ! error handler (when a script throws) and HTTP error callback commands (when a request returns a non-2xx status).

When would you use it?¶

• Log failures to the owner in your ! handler
• Send user-friendly fallback messages after a crash
• Handle API errors gracefully in HTTP error callbacks (404, 500, rate limits)
• Inspect stack traces for debugging (sanitized — internal paths are redacted)

Pair with owner for alerting and http_response for successful HTTP flows.

Try it — script errors (! handler)¶

When any command throws, the ! command runs with:

// Inside the ! command
Bot.sendMessage(owner.mail, "Error: " + error.message)
Bot.inspect(error.stack)

Try it — HTTP error callbacks¶

When an HTTP request fails and routes to an error callback, error is the full HTTP response object (same structure as response in http_response):

// Inside an HTTP error callback command
if (error.status === 404) {
  Bot.sendMessage("Resource not found.")
} else if (error.status === 429) {
  Bot.sendMessage("Too many requests. Slow down!")
} else {
  Bot.sendMessage("API error: " + error.status)
}

Which handler ran?¶

Good to know¶

• error is read-only and exists only during error-handling command execution
• The ! handler is the right place for logging and graceful fallbacks — don't let users see raw stack traces
• Stack traces in the ! handler are sanitized for safety