WIKI

Mods

3D models

Every model in the game has a key, such as Towers/Gun_1 or Buildings/Radar_1. A mod maps keys to GLB files of its own in models.json; every key it leaves out keeps the game's model. Towers have a page of their own: tower models.

models.json

{
  "version": 1,
  "models": {
    "Towers/Gun_1": {"file": "Models/Gun_1.glb", "material": "imported"},
    "Towers/Gun_2": "Models/Gun_2.glb",
    "Buildings/Factory_1": "Models/Factory_1.glb",
    "Enemies/garden_flyer": "Models/Flyer.glb"
  }
}
  • Keys are case-sensitive, and file paths are relative to your mod's folder. A plain string is the same as {"file": …, "material": "imported"}.
  • Each level and each fusion is its own key: replacing Towers/Gun_1 leaves levels 2 and 3 as they were. Point several keys at one file if its pivots suit all of them.
  • A model changes how something looks, never how it plays: range, damage, footprint and paths stay the game's.

Preparing the GLB

  • Export glTF 2.0 binary (.glb) with every texture embedded, Y up (Blender's +Y Up) and scale 1. A file may be up to 64 MiB.
  • Use indexed triangles with normals (Blender's default). No armatures, skins, animation clips, cameras or lights: the game moves models by their named Empty pivots, so put each moving part under its pivot.
  • Keep the pivots, names, scale, origin and axes of the model you replace. The easiest start is a GLB from one of the examples, imported into Blender and edited.
  • A model that breaks its contract is refused, with a line in the log, and the game keeps its own.

Materials

  • "material": "imported" (the default) keeps your PBR materials: base colour, metal and roughness, normal and occlusion maps, emission. Transparent parts are cut out, not blended.
  • "material": "game" paints the model in Torreta's own look from its vertex colours (COLOR_0), including the insects' chitin and glowing eyes.

Either way the model is built up from the ground, takes hits, breaks apart and gets wet in the rain like the game's own. Keep triangle and material counts close to the game's, above all for insects, which come by the hundred.

Model keys

model_catalog.json in the _vanilla_reference folder of your Mods folder lists every key with its pivots and size. The groups:

KeysHow manyFor exampleKind of mod
Towers/39Towers/Bolt_1, Towers/Gun_2, Towers/Poison_3_Fused …Gameplay mod
Enemies/84Enemies/Castes/atlas, Enemies/dusk_weaver, Enemies/weaver_flyer …Gameplay mod
Allies/7Allies/Commander, Allies/Ranger, Allies/Soldier …Cosmetic
Buildings/5Buildings/Barracks_1, Buildings/Factory_2, Buildings/Radar_1 …Cosmetic
Factory/101Factory/Assembler_1, Factory/Conveyor_4_4, Factory/Splitter_1 …Cosmetic
Environment/80Environment/Arena, Environment/Rubble_Cannon_1, Environment/ExpeditionTowerColumn …Cosmetic · Environment/Arena: Gameplay mod
Markers/6Markers/PartnerCursor, Markers/RadarStop, Markers/TileCursor …Cosmetic
Birds/8Birds/Buzzard, Birds/Raven, Birds/Vulture …Cosmetic
Snakes/2Snakes/HornedViper, Snakes/SandRacerCosmetic
Microfauna/6Microfauna/Ant, Microfauna/Cricket, Microfauna/Shelter …Cosmetic
Attachments/11Attachments/AmmoEjector_Cannon, Attachments/FrostLinkManifold, Attachments/SpentCase_MachineGun …Gameplay mod

Replacing a tower, an insect or the arena makes your mod a gameplay mod, since the game aims and hits with those models. The other groups are cosmetic.

Wearing one of the game's models

Never ship a copy of a game model. A slot can wear one of the game's models kept under another key instead, named with game_model:

"Towers/MachineGun_1": {"game_model": "Towers/Hangar_1"},
"Allies/Hero": {"game_model": "Allies/Commander"}

The model you name must still carry the pivots the slot needs.

Every model you can name, with its picture, key and pivots, is in the game's models. A tower of yours can also stand as any of them: see a tower drawn as a building. The sample mods' own models are not the game's: copy a sample's GLB into your mod's folder to use it.

Lighter from afar

"generate_lods": true makes simpler versions of a dense model when the game loads, drawn when the camera is far away. For a rigid assembly of many separate pieces add "lod_mode": "rigid_parts", which simplifies each piece on its own. Check the result at the zooms you care about.

Insects and the worm

Each difficulty has twelve insect families, and each family a walker and a flyer: Enemies/<family> and Enemies/<family>_flyer on the first difficulty, with dusk_ or night_ before the family on the second and third (Enemies/night_garden_flyer). The families are acrobat, army, bullet, carpenter, fire, garden, harvester, honeypot, leafcutter, trapjaw, turtle, weaver. From wave 6 some insects wear a caste instead, Enemies/Castes/<caste>: atlas, brain, cricket, dragonfly, hornet, jewel, rhino, stag, termite, tiger, tortoise. Bosses are their family's model, enlarged.

  • Keep the insect rig: Body, with Head, Abdomen, Armor, Shield, Leg0 to Leg5 and Wing0 to Wing3 under it, and JawL, JawR, AntennaL, AntennaR, EyesL, EyesR and ShieldHead under Head. Pivots you do not use may stay empty.
  • A walker stands on Leg1, Leg2, Leg4 and Leg5, which need real feet; Leg0 and Leg3 are its front claws.
  • Your geometry is the body the cockpit's shots hit.
  • Something upright that should float rather than walk takes "locomotion": "float" in its models.json entry.
  • Optional: TraitRegenerator, TraitSplitter, TraitShielded, TraitHaste and TraitNecromancer under Body show a champion's organ, and ElytronL and ElytronR under Body hold beetle wing covers.
  • The worm, Enemies/Worm, keeps Body and its six jaws Jaw0 to Jaw5; an optional Mouth Empty under Body places the tower it swallows.

Flying creatures

A flyer uses the same pivots, with its wings under Wing0 to Wing3 (a creature with two wings uses Wing0 and Wing2) and its legs folded. In Blender, X is forward, Y left and Z up; keep Body 5.8 units up and the whole creature, wings beating, within about 40 units of its centre. flight_cycle_speed, from 0.05 to 4 (1 by default), slows or quickens the wingbeat without changing how fast the flyer goes:

"Enemies/garden_flyer": {"file": "Models/Ptero.glb", "material": "imported", "flight_cycle_speed": 0.22}

The flying castes are dragonfly, hornet, jewel and atlas; the other castes walk. Ptero flyers replaces every flyer.

Buildings and factory pieces

Buildings/Factory_1 to _3, Buildings/Barracks_1 and Buildings/Radar_1 keep the moving parts and lamp pivots the catalogue lists (Flywheel, PressHead, Rotor, DishTilt, LampSocketLeft…). Inside the factory, Factory/Assembler_1 to _3, Factory/Splitter_1 and the Factory/Conveyor_* keys are the machines and belts, and Factory/Items/<material> is the cargo box of each material, a new material of yours included.

The factory room

Factory/Room is the floor and walls inside the zoomable factory. It uses the factory's own coordinates, in Godot units: Y up, the top of the floor at Y = 0, a 32-unit grid of nine columns (X from −128 to 128) and seventeen rows (Z from 0 to 512), and the buildable area within X −144 to 144 and Z −16 to 528. In Blender a Godot point (x, y, z) is (x, −z, y). Keep the cells clear and tall details at the edges; no pivots are needed. Cobalt factory room is a complete one.

Ground markers

The tile cursor, the co-op partner's cursor, the range ring and the radar's route are models too:

  • Markers/TileCursor and Markers/PartnerCursor: centred on the origin, fitting a 64 × 64 tile (X and Z from −32 to 32).
  • Markers/RangeRing: a ring of radius 128 round the origin; the game stretches it to each tower's real range. Keep it a ring, not a disc.
  • Markers/RadarChevron (an arrow pointing to +Z, repeated every 32 units along the route), Markers/RadarGuide (side tabs, every 64 units) and Markers/RadarStop (a crossbar where the route is blocked).

Keep them shallow, with the underside at Y = 0. At least one material must be named MarkerSignal (MarkerSignal.001 works too): the game lights it in the placement's colour, green, yellow, blue or red, so model the glowing shape and leave its colour to the game.

Rubble and arena pieces

  • Environment/Rubble_Natural_0 to _2 are the rock piles, and Environment/Rubble_<Tower> each tower's wreck (add _1 and _2 for a different wreck at levels 1 and 2). Name nodes Piece_1, Piece_2… to choose which stones the Collector's magnet carries off on each trip, lowest number first.
  • Environment/Barrier_1 to _3 keep Drill_0 to Drill_4; extra Drill_5, Drill_6… spin too.
  • Environment/Fence (PostLeft, PostRight, Rails), Environment/CollectorClaw (Jaw0 to Jaw2), Environment/Core (the energy core of the cores rule, about 18 units wide and 20 high), Environment/PlainShrubs (the plain's dry shrubs) and Environment/Debris_0 to _2.
  • Environment/Arena replaces the whole arena. For arenas by difficulty and wave, see scenery and board.

Allies

Allies/Soldier, Allies/Reinforcement and Allies/Hero dress the units of a barracks, a reinforcement power and a hero; Allies/Sentinel, Allies/Ranger and Allies/Commander are the Mech Hangar's. They keep Body with Weapon under it, and Shield on all but the reinforcement; the mechs add MechRig, StrideLeft, StrideRight, KneeLeft and KneeRight for their walk. Allies/Parachute is the Ranger's canopy.