Torrent Inspector 2.3.0

Tracker rules

Build a rules profile for a tracker, check one you already have, and run a release name through it to see exactly what it would say. A profile is data — the script never executes anything in one.

This page runs the userscript's own profiles.js, rules.js and naming.js, built in at publish time — so what it says here is what the script says. Nothing is fetched, nothing is stored, and nothing you type leaves the page. You do not need the script installed to use it.

Build a profile

Fill in what the tracker publishes. The JSON appears below as you go.

Who the tracker is

Where this tracker goes its own way The shared book or music template then stands aside and only the rules judge them; the folder standard has a torrent page's file list checked too (one root folder, numbered tracks, no NFO/TXT/URL).

Banned release groups

Rules to include

Starting points, in this tracker's own words once added — edit the JSON afterwards to reword or add your own.

Fill in a key and a name to see the profile.

Paste this into the script under Tracker rules… → Paste or load. Nothing in it is run as code: patterns are compiled as regular expressions and matched against a title, and one that will not compile is refused with the reason rather than swallowed.