Adds an RST column to your faction members list: rolling 7-day respect per member, taken straight from Torn's own chain reports.
Who actually chains in your faction? Open the members list and read it off — one column, one number per member, respect earned in the last 7 days.
The number comes from Torn's own chain reports, so it matches what Torn already shows you for each chain. No spreadsheet, no copying chain reports into a sheet, no third-party site holding your faction's data.
A new RST column appears immediately right of Icons on your faction page:
| 20 / 25 Faction Members | Lvl | Icons | RST | Position | Days | Status |
|---|---|---|---|---|---|---|
| CrimeLord | 41 | 🎖️❤️📋 | 127 | Leader | 105 | Okay |
| WarLord | 38 | 🎖️❤️📋 | 105 | War Chief | 88 | Okay |
| SilientLipsJonny | 26 | 🎖️❤️📋 | 175 | Full Patch Member | 12 | Okay |
| 7FingerFrank | 26 | 🎖️📋 | 9.32 | Full Patch Member | 92 | Traveling |
A faint bar under each value scales it against your top earner, so the pecking order is visible at a glance. Hover any number for the detail: how many chains that member joined, how many attacks, exact respect, average per hit, best hit, and how much of it was milestone bonus.
Every other column keeps working — including the stat-estimate column from FFScouter if you run it. Nothing is moved or removed; the columns each give up a few pixels so the row still fits with no sideways scrolling.
— until you add a key.Works on Torn PDA too — the app injects your API key automatically, so there's nothing to set up.
Not sure the key is right? Test key asks Torn what the key actually is and reports back — its owner, faction, access level — so a typo or a key with too little access is one click to diagnose instead of a guess.
This is the part worth reading, because two honest answers to "how much respect did we earn this week?" differ by a factor of seven, and every faction tool quietly picks one.
Measured on one real week, same faction, same 7 days:
| Source | What it counts | That week |
|---|---|---|
| Chain reports (default) | Only chains that reached 10, using Torn's per-member figures | 443.65 |
| Attack log | Every single attack, summed by respect gained | 3204.05 |
Both are correct. They answer different questions.
Why the gap. Torn only records a chain once it reaches 10 — that faction had four of those in the week (10, 13, 34 and 50 long). The other ~2,700 respect came from dozens of chains that died at two or three hits and appear in no chain report anywhere. So:
Switch between them any time in the panel under Where the respect comes from. Chain reports are the default, and the cheaper of the two by a wide margin.
Chains pay a flat bonus at 10, 25, 50, 100, 250, 500… — worth 10, 20, 40, 80, 160 respect and so on. Those bonuses appear only in chain reports; they are nowhere in the attack log, and the attack row that landed the milestone carries an ordinary respect value like any other hit. The script adds them to whoever landed them, and you can turn that off.
If you have seen another tool claim to filter "bonus hits" from attack data, that is guesswork — the flat bonus simply isn't in that data.
Everything lives in one panel, opened from the column header.
| Setting | What it does |
|---|---|
| API key | Limited access or higher. Stored on your device only. Show unmasks it, Test key validates it against Torn. |
| Where the respect comes from | Chain reports (default) or the full attack log. See above. |
| Rolling days | 1 to 30. Default 7. The window always ends now, so it rolls with the clock. |
| Refresh every | 1 to 240 minutes. Default 10. |
| Add milestone bonuses | Chain reports only. On by default. |
| Attack log options | Attack log only: count regular / chain / war / retaliation / overseas hits, include failed attacks, and a cap on how many pages to fetch. Two presets: all attacks, or chain hits only. |
| Hover tooltips | The per-member breakdown on hover. |
| Refresh now / Rebuild cache | Force an update, or throw the cache away and rebuild from scratch. |
One key, one purpose. The key is stored on your own device (via GM_setValue, falling back to localStorage) and is sent to api.torn.com and nowhere else. No analytics, no telemetry, no third-party server, and the key is never written to logs — any error message it prints has the key stripped out.
Access level: Limited, with faction API access on your position. Make a key at Settings → API Key, or preferences.php#tab=api.
In chain-report mode a refresh is:
GET /v2/faction/chains?limit=100&sort=DESC&from=<window start>
GET /v2/faction/{chainId}/chainreport (only for chains not already cached)
A chain report never changes once the chain has ended, so each one is fetched exactly once and cached by chain id forever. After the first build, a refresh is normally a single request — the chain list — plus one more if a chain is still running. Attack-log mode costs one request per 100 attacks instead, which on an active week is nine or ten.
Requests carry &comment=FactionRespectColumn so Torn staff can attribute the traffic, are spaced 800 ms apart, and only the visible tab polls. Several tabs share one cache and one lock, so ten open Torn tabs cost the same API budget as one.
If Torn returns an error the script surfaces the code and message, backs off instead of hammering the key, and keeps showing the last good numbers. It clears a stored key on codes 1, 2, 13 and 18 (empty, incorrect, disabled or paused) rather than retrying it forever.
The numbers don't match the faction tool I already use. Very likely, and it usually isn't a bug in either. Check three things: which source the other tool uses (chain reports vs every attack — see the table above), what its window really is, and whether it counts milestone bonuses. A quick test: pick one chain, open Torn's own report for it, and compare a single member. This script's chain-report mode will agree with Torn to the penny.
A member shows 0 but I know they've been hitting. In chain-report mode, 0 means they landed nothing in a chain that reached 10. Solo hits and short chains don't appear. Switch to the attack log if you want those counted.
Why is the column called RST? The row is a fixed width, and "Respect" was clipping. Hover it for the full explanation.
Does it work on mobile? Yes. The column narrows, the settings panel becomes a full-screen sheet with proper tap targets, inputs are 16px so iOS doesn't zoom, and there's no sideways scrolling.
Does it do anything in-game for me? No. It reads the API and the page, and adds a column. It never attacks, never joins a chain, never takes any action on your behalf.
Does it slow the page down? No. It caches to your browser, only the visible tab refreshes, and the DOM work is a single cell per row, debounced.
Does my faction need to install it? No. It's yours alone, reading your faction's data with your key.
3.24, 82.7, 115, 45.7k). The exact value is in the tooltip.api.torn.com.Built against the Torn API v2 (/faction/chains, /faction/{id}/chainreport, /faction/attacks).
Written by Microddot [4347781]. Bugs and suggestions: message me in Torn.
Licensed MIT.
Enjoying it? Send a Xanax to Microddot [4347781]. 💊