Skip to content
3 Death Saves

Snoot

Uninstalled modules leave settings and flags behind in your world. Snoot finds that data and deletes it.
How It Works View on Foundry Support on Patreon

What it does

Section titled “What it does”

Every module you install writes data into your world. Most of that data stays behind when you remove the module. Snoot scans world settings, flags on world documents, flags on compendium documents, user flags and settings, and the client settings stored in the browser you are running it in. It groups what it finds by the module that owns it, then deletes the entries you pick. Client settings live only in the browser that stored them. Each player has to log in and run Snoot on their own machine to clear their copies.

Module statuses

Section titled “Module statuses”

Snoot tags every module it finds as Active, Inactive, Orphaned, or System. Orphaned means the module is no longer installed. Foundry core and system data stays out of the results until you turn on the matching scan toggle in Settings.

Stale settings

Section titled “Stale settings”

A module can be installed and enabled and still hold dead data in your world. When a module renames or removes a setting key, the old value stays in storage with nothing declaring it. Snoot marks those keys Stale and reports them alongside the orphaned data. A key an active module has not declared yet counts as Pending instead of Stale. Snoot leaves Pending keys in place when you sweep stale settings in bulk.

Cleaning

Section titled “Cleaning”

One click cleans every orphaned module at once. Separate buttons sweep every inactive module and every stale setting. A row in the module list cleans everything that one module owns. You can also open a single namespace, read the keys and values, and delete one entry at a time. Snoot cannot restore a deleted setting or a removed flag. Back up your world before you clean anything.

Next steps

Section titled “Next steps”

Support

Section titled “Support”