Worth reading before promising a customer "you'll never lose a file again": PawTrash covers a lot, but it isn't magic and a few cases are deliberately left out.

What it covers

  • Deletes made through the panel's File Manager.
  • Deletes made over SFTP.

Both paths end up calling the exact same delete operation inside Wings, so coverage is identical for either one.

What it doesn't cover

  • A game server process, plugin, or mod deleting its own files from inside the container doesn't go through Wings at all - that delete is permanent, same as on a Pterodactyl install without the addon. This is an architectural limitation, not a bug: Wings doesn't intercept what happens inside the game process itself.
  • Emptying the trash (Empty trash or Delete selected forever) is irreversible, as you'd expect from "delete forever."

Retention sweep

Automatic purging on retention expiry is lazy: it fires the next time someone lists a specific server's trash, not on a cron or a fixed schedule. A trash nobody ever opens never gets swept on its own. This is a deliberate simplicity trade-off - plenty for the real-world use case, without needing a scheduler of its own inside Wings.

Per-node enable/disable

The enabled/disabled state is fetched by Wings from the panel with a roughly 30-second cache, so it doesn't add a network call to every single delete. A state change can take up to that long to be noticed.

Restoring onto an occupied path

If the original spot already has something new in it, the restore is rejected without touching either the new file or the one in the trash. Clear the path (delete or rename whatever's occupying it) and try again.

Previous: Using the Trash · Next: FAQ