Concepts
Every game object the community ever declared — weapons, projectiles, turrets, armours, explosions — pulled out of the scripts inside 376 mod archives. Browse what they are and how they work without opening a mod in Tribes.
Search all 15784 concepts on one page →
Browse by kind
Cobbled from the base game
The community's cleverest reuse: objects that ship no new art and instead weld several existing Dynamix models into one by script — a pack that plants the base tree, a gun spliced from two base weapons. all 823 → (a further 8,515 community entities reuse a single base model — every entity page shows the base shape it borrows).
Most forked
The names mods argued about most — each variant is a different opinion about what the thing should do. Limited to entities in 5+ mods.
Most copied
The community's greatest hits, by how many mods shipped them.
Most agreed on
Shipped widely and almost never altered — copied verbatim, mod after mod. Limited to entities in 20+ mods.
All types
How to read this
An entity is a name; a variant is an opinion about what that name means. When two mods ship Railgun with different fire rates, that's two variants of one entity. Agreement is the share of mods on the single most-shipped variant: 97% means everyone copied the same thing, 12% means nearly every mod built its own.
Retail vs community. Entities marked Dynamix are declared by the retail game. Their variants are matched against a reference copy of base/scripts.vol, so a variant marked RETAIL is property-identical to our reference — Tribes shipped patches, so another build we don't hold may differ. It is never a claim to be "the original".
We don't claim lineage. Nothing records which variant forked from which. Variants are described by how they differ from the retail or most-shipped version — never as descended from it. Dates in these archives are unreliable (one mod stamps every file three years before the game shipped), so chronology is deliberately not used to rank or attribute anything.