Extensibility
Scryer’s core stays small. Integrations with the outside world are plugins, and each configured use of a plugin is a provider instance.
Plugin
Section titled “Plugin”A plugin is a WebAssembly package that adds a provider type to Scryer. Plugin kinds:
- Indexer plugins for trackers and Usenet indexers, plus generic Newznab and Torznab.
- Download client plugins.
- Notification plugins, including the Plex, Jellyfin, and Emby library refreshers.
- Subtitle plugins for providers and for enhanced sync.
- Rule pack plugins that install sets of custom rules.
- Archive extraction for RAR, ZIP, and 7z payloads during import.
You manage plugins in Settings → Plugins. Installing one makes its provider type available on the matching settings page. The Plugins guide covers support tiers and manual installs.
Provider
Section titled “Provider”A provider instance is one configured use of a plugin’s provider type: a specific indexer with your API key, a specific download client at a specific URL. The plugin supplies capability and fields; the instance stores your values.
One plugin can back many instances. Two Newznab indexers are two instances of one plugin.
Provider Catalog
Section titled “Provider Catalog”The provider catalog is the list of plugins Scryer can install, with versions and compatibility. Refreshing it in Settings → Plugins reveals new plugins and updates for installed ones.
Built-In, Installed, And Overridden Plugins
Section titled “Built-In, Installed, And Overridden Plugins”A built-in plugin ships inside the Scryer binary. An installed plugin came from the catalog. An overridden plugin is a built-in replaced by an installed version, usually to pick up a fix ahead of a Scryer release. Revert to bundled undoes the override.
Plugins are labeled official when published by the Scryer team and community otherwise. Beta marks a plugin that works but has not seen wide use yet.