Skip to content
Blueprint extension Live

Crash Detector for Blueprint: know when a Pterodactyl server crashes, and why

A plugin breaks, a mod leaks memory, the server runs out of RAM. Wings starts it again, nobody notices until a customer opens a ticket, and the console that showed the error has scrolled away or was cleared by the restart.

Buy on Gumroad ($5.99) →Crash Detector on SourceXchange →Guide: detect server crashes →

On sale on Gumroad. The SourceXchange listing is coming soon.

Requires
Pterodactyl Panel 1.x with Blueprint, the panel's cron and queue worker
Tested with
Pterodactyl 1.15.1 and Blueprint beta-2026-08
Alerts
About 2 to 4 minutes after a crash
Price
$5.99, one panel

Crash Detector checks every server once a minute. When a server goes offline, or is restarted by Wings, without anyone pressing Stop or Restart, it keeps the last console lines, lists the crash on the server and tells the owner and your staff.

Crashes tab on a Pterodactyl server listing two crashes with run time, memory near the limit and the last console lines
Every crash with its time, run time, memory and last console lines

What Crash Detector for Blueprint does

Tells crashes from manual stops

Start, Stop, Restart and Kill from the panel, API or console page, the typed stop command, reinstalls, backup restores and scheduled power tasks are not reported as crashes.

Keeps the last console lines

The final lines when the server stays offline; when Wings restarted it, which clears the console, the lines from the check just before the crash.

Crash history on the server

A Crashes tab for everyone with console access: time, offline or restarted, run time, memory at the last check with a near-the-limit flag, and the lines as plain text.

Email to the owner

Through the panel's own mail settings, at most one per server every 15 minutes.

Discord for your staff

Every crash on every server in one channel, optionally with the last 10 lines. Only discord.com webhooks, stored encrypted, mentions off.

Crash loop protection

Optional, per server: stop a server after, say, 3 crashes within 15 minutes, with the same signal as the Stop button, instead of letting it restart forever.

How it works

  1. Upload. Put crashdetector.blueprint in your Pterodactyl folder (usually /var/www/pterodactyl).
  2. Install. Run blueprint -install crashdetector. With Blueprint in Docker, also run php artisan migrate --force in the panel container, or restart it.
  3. Configure. Admin → Extensions → Crash Detector: email the owner (on by default), a Discord webhook for your staff with a test button, and whether to include the last 10 console lines.

Screenshots

Crash loop protection set to stop the server after 3 crashes within 10 minutes, and a crash stopped by it
Optional: stop a server that keeps crashing instead of restarting it
Email to the server owner: the server went offline without a stop from the panel, with run time, memory and a link to the console lines
The owner gets an email through the panel's own mailer
Crash Detector admin page with alert settings, the saved Discord webhook, the last check per node and recent crashes
Discord alerts for your staff, check status and recent crashes

How it works

The panel's scheduler runs the check every minute. It asks each node's Wings for the state of all its servers (one request per node, with the node's own token) and reads the console of running servers. Nothing is installed on your nodes.

A suspected crash is confirmed two minutes later, once Wings has sent the panel any power actions made on the console page, so alerts arrive about 2 to 4 minutes after a crash.

Pricing

$5.99One-time purchase

One panel; a test or staging copy is included. Updates within 1.x, full source.

Good to know

  • When Wings restarts a crashed server, the saved lines are from up to a minute before the crash: the restart clears the console, and Wings' own exit message never reaches the panel.
  • Memory is the value of the last check, and several crashes between two checks count as one.
  • A stop made inside the game (an operator typing /stop) is reported as a crash, because the panel cannot see it.
  • A node that cannot be reached is skipped and never produces crash reports.
  • Tested with a stand-in Wings that follows Wings' API; timing and console output of real servers will differ.

Guides

How to detect game server crashes in Pterodactyl and get alerts (Blueprint)

When Wings restarts a crashed server, the console is cleared and nobody is told. Compare state changes with the activity log to tell crashes from manual stops, keep the console lines from before the crash, and send alerts. Crash Detector does this on Blueprint panels.

Read the guide →

FAQ

Who can see the crash history?

The owner, admins and subusers with console access, because it contains console output. Changing crash loop protection needs the permission to stop the server.

Does it need anything on my nodes?

No. It only uses Wings calls the panel is already allowed to make.

Will a node outage flood me with alerts?

No. A node that does not answer is skipped, and its servers start from scratch when it is back, so an outage or reboot that the check notices is not reported as crashes.

Where is the data?

In your panel database (two tables) and the server activity log. Only the Discord message leaves your panel, and only if you set a webhook.

Does it work on Pterodactyl 2.0?

No. It is a Blueprint extension for Pterodactyl 1.x, tested on 1.15.1 with Blueprint beta-2026-08.

Related tools

Blueprint extensionLive

Staff Access for Blueprint

Staff request access to a customer's Pterodactyl server, the owner approves the permissions, and access ends on its own. Logged. Blueprint, no core edits.

Blueprint extensionLive

Server Expiry for Blueprint

Expiry dates for Pterodactyl servers without a billing system: warning emails 7, 3 and 1 day before, suspend at expiry, renew by admin or owner. Blueprint.

Updated 2026-10-25