Torn Loadout Share

Shows shared defender loadouts on Torn attack pages. Firebase backend, no registration.

Installer ce script ?

Poser une question, écrire un avis, ou signaler le script.

Auteur

Sigtran

Installations quotidiennes

Installations (total)

Notes

0 0 0

Version

1.0.7

Créé

19/03/2026

Mis à jour

20/03/2026

Taille

42,7 ko

Licence

MIT

S'applique à

torn.com

Torn Loadout Share (Desktop)

Shows shared defender loadouts on Torn attack pages. When you attack someone, you can see their weapons and armor—even if you don't have the Gunshop perk—by pulling loadout data from a shared Firebase database. No registration, no API key, no account required. If you’re on Torn PDA, install the PDA-only version instead:

- https://greasyfork.org/en/scripts/570408-torn-pda-loadout-share

What It Does

When you view an attack (sid=attackData)
- The script parses the defender’s loadout from the native Torn response (when available).
- If it finds defender items, it uploads the defender loadout to Firebase so other users can see it later.
When you load an attack page (loader.php?sid=attack&user2ID=*)
- The script fetches the defender loadout from Firebase using the defender’s user2ID.
- If a saved loadout exists, it renders the defender’s:
  - Weapons (Primary, Secondary, Melee, Temporary)
  - Armor/model overlay on the defender model
Shared by badge
- When a loadout was submitted by someone else, a small badge appears showing who shared it (with a link to that profile).

What You See
Weapons
- Primary, Secondary, Melee, Temporary
- Displays up to 2 mods and 2 bonuses per weapon (with hover titles)
- Shows:
- Melee ammo as infinity
- Temporary ammo as 1
Armor / Model overlay
- Visual overlay on the defender model (Helmet, Chest, Pants/Legs, Boots, Gloves)
- Slot 10 is ignored (on many pages it behaves like body cosmetics and causes inconsistent results)
Visual-only armor overlay
- Armor overlay uses pointer-events: none so it should not interfere with Torn’s native hover behavior.

Requirements
A userscript manager (Tampermonkey, Violentmonkey, Greasemonkey, etc.)
Access to Torn attack pages: https://www.torn.com/loader.php?sid=attack&user2ID=*

- No Torn API key or registration needed

Privacy & Data

Loadout data is stored in a shared Firebase Realtime Database.
The script also reports error/debug info to Firebase if something goes wrong (page path, target IDs, and the error message), to help fix issues.

- No sensitive personal data is collected beyond what’s needed to identify attackers/defenders and help debugging.

Limitations

Loadouts only show for defenders who already have a saved entry in Firebase.
Torn’s DOM may change; if the script breaks after a Torn update, you may need a new version.

- If defender items aren’t present in Torn’s response, the script may not be able to upload/parse a loadout for that target.

Desktop vs PDA

Desktop (this script): upload + render.
PDA (read-only): only renders from Firebase; does not upload.
- https://greasyfork.org/en/scripts/570408-torn-pda-loadout-share

Greasy Fork