Tampermonkey userscript · UNIT3D trackers
It reads the page you are already on: every release name checked against the naming rules, the MediaInfo the uploader posted checked against what the title claims, and each release group linked to where it is internal. Nothing is ever fetched, posted or changed.
Install it, open a listing, and three things are different.
A ✓, ✕ or ? beside each release name. Hover for the reason in one line; click for the full explanation, the corrections and a copyable report.
The -GROUP at the end of a name opens where that group is internal, its other releases here, and the same search on your trackers.
On a torrent's page, what the title claims is compared with the report the uploader posted — resolution, codecs, audio, HDR, languages.
Listings, a member's uploads, bookmarks, playlists, the home page panels, a film's own page, and the moderation queues.
Passed. The supported title checks found nothing wrong — not a promise that the media, the source history or tracker approval were verified.
Corrections found. The guide writes display titles with spaces, so it writes the fix out for you — Dead Silence 2007 2160p UHD BluRay DTS-HD MA 5.1 DV HDR x265-B0MBARDiERS — keeping the dots that belong, like H.264 and DDP5.1.
Your judgement needed. An uncertain category, a rule the title alone cannot settle, or a missing group tag. It asks instead of guessing.
A Rules dropdown in the bar: DarkPeers, Zenith, or a tracker you add. It changes the upload rules and the banned-group list — the naming guide itself is shared — so the same title can be clean on one tracker and rejected on another.
Tracker rules… takes a tracker's banned list pasted straight off its page, plus tick-boxes for the rules that apply. Profiles export and import as JSON.
Audit loaded titles lists every name on the page with its faults as copyable text, and remembers what you checked while browsing so one audit can cover many pages.
Click the group tag at the end of any release name.
Listed as internal at … — every tracker, not just one. DON comes back HDBits and UHDBits; LoRD comes back Bit-HDTV, HD-Torrents and UHDBits.
Then that group's other releases on the tracker you are on, and the same search on each tracker you have chosen for the cross-check.
It ships with a community directory of internal groups — 433 groups across 35 trackers — dated in the source. Because a directory can go stale, every line reads “listed as internal at”, and a group that is not on it is reported as not on it rather than guessed at.
A tracker's line links to it when the script already has that tracker's address, from your cross-check list. Private tracker domains move, so it will not invent one — those lines stay as plain text until you supply an address.
OnlyEncodes+|OnlyWeb GRiMM
BeyondHD|BHDStudio FraMeSToR FLUX|https://beyond-hd.meThe two Add paths append; only “Save list” replaces the whole list. Save tells you what it did — “Saved: 434 entries”, or “— 3 fewer than before” — so a mis-paste announces itself. Clear list puts the shipped directory back.
If another script has already turned that group tag into a link, this one leaves it completely alone — no wrapping, no rewriting, nothing for two scripts to fight over.
On /torrents/pending, /torrents/rejected and /torrents/postponed.
Each row gets Approved / Rejected / Asked the uploader / Left for someone else, ticked with the date so a sweep does not repeat itself. Rejecting or asking prompts for a note.
It records what you decided. It changes nothing on the tracker and never leaves your browser.
Inside the badge dialog: a draft with the corrections numbered in the guide's own words, the release name and its link, and a closing line. Four outcomes, one suggested — a banned group suggests a rejection, not a rename.
Manual checks appear as worth confirming, never as faults. Edit before you copy; nothing is sent.
TMDB title and year against the name. The Type and Resolution filed against what the name claims. The file list — containers, samples, a lone film in a folder, whether a season pack's files agree. Whether MediaInfo or BDInfo was posted. And Dual-Audio / MULTi against the page's own original language.
Where a rule is in hand it is cited, and the finding is an error. Where none is, the finding says so — “the guide in hand states no container rule for this tracker, so check its upload rules.” Nothing invents a rule to sound authoritative.
Alt+Shift+I on a torrent page — or paste a report of your own.
| The title claims | Checked against the report |
|---|---|
| 1080p, 2160p | The actual pixel dimensions, and progressive against the scan type |
| x264, x265, AV1 | The video format the report names |
| DD+ 5.1, DTS-HD MA, Atmos | The default audio track — DD and DD+ kept apart — and the channel layout against the reported count |
| DV, HDR10+ | Whether that HDR format is actually there |
| Dual-Audio, MULTi | The languages in the file, and subtitles for non-English audio |
| REMUX | Chapters, and a TrueHD track's compatibility track where the tracker requires one |
On a torrent page, press vs and capture this release; open the other one and capture that. You get the file lists and sizes compared (with the gap named), the two MediaInfo reports compared, and both releases written out in the block layout WinMerge or meld reads. It does not pick a winner: source, encode quality and provenance are not in a report, and it says so.
Both captures stay in your browser. No companion program, no new permission.
The naming box checks against the chosen tracker's rules, with reference fields — official title, original-language title, service — that make the manual checks decidable, and a searchable list of the 261 streaming-service abbreviations.
Per torrent, kept in your browser, never sent anywhere.
Links, built on the page and opened only when you click them.
/requests gets a search button, and a request's own page shows the links under its title. 58 trackers are built in — 41 of them UNIT3D — each with an editable search address; anything missing can be added.
Only https addresses are accepted, a tracker that cannot carry the search is left out with the reason,
and no login, cookie, passkey or API key is read or stored.
.user.js address and opens its own install page.DarkPeers and Zenith, plus 41 UNIT3D trackers. Which sites run UNIT3D comes from HDVinnie's Private Trackers Spreadsheet; the addresses come from each tracker's own Jackett or Prowlarr indexer definition, because that spreadsheet carries none. Nine UNIT3D sites have no definition to read and are left out rather than guessed at — they are named in the README, and adding one takes a line.
Every tracker is a // @match line at the top of the file: delete a line to stop it running there,
copy one and change the domain to add your own. The list is generated from the tracker catalogue when the script is
built, so the two cannot drift apart.
On a tracker whose rules it does not have, nothing is badged until you choose a rule set from the Rules picker in the bar, or add that tracker under Tracker rules…. A red ✕ on LST citing DarkPeers’ banned list would be quoting a rulebook LST never wrote, so it waits to be told. Everything that needs no rulebook — the Inspector, the vs comparison, the group tags, the cross-check — works there straight away.
Updating later is the same click: Tampermonkey replaces the script rather than adding a second copy. Prefer to do it by hand? Open the file on GitHub, copy it, and paste it over the contents of a new Tampermonkey script.
If you download the file instead, do not double-click it — Windows tries to run a .js file rather than install it.
Keep one copy enabled. If the full DKOKTO Scene Edition is running on the same page, this one stands aside so the two never clash.
Tracker|group group group|https://address.The whole point of the thing, and the part worth checking yourself in the source.
Nothing is fetched, crawled, uploaded or downloaded. Every link opens only when you click it. No API access, and no cookie, passkey or credential is read.
It asks Tampermonkey for three permissions and they are all storage — GM_setValue, GM_getValue,
GM_deleteValue — which is how the vs slots are shared between trackers. There is no
GM_xmlhttpRequest and no @connect line, so it has no way to make a request at all.
Nothing is posted, submitted, approved, rejected or edited on your behalf. It reads the page you are on and tells you what it found.
Every list it keeps lives on your machine with a fixed cap, and is never sent anywhere. Your setup — the trackers you are on, the rules you have added, your internal-groups list — is kept in Tampermonkey's own per-script store, so it is the same on every tracker. What you did on a particular tracker — the audit, the decision log, private notes — stays on that tracker. Both are storage on this machine, not a request.
Where the tool cannot know something it says so rather than guessing, and where it applies a rule it names the rule. That is the design, not a disclaimer.