Tower.defense(): Program The Fight

Program the fight.

In tower.defense(): Program the Fight, towers do not decide for you. Place one on the board,
open its controller and build the rule it will follow when the machines arrive.

There is no syntax to type. The visual language introduces conditions, comparisons and logical
choices in plain words, one idea at a time. You can start with “fire at the nearest enemy” and grow
toward compact IF/ELSE behaviours that react to armour, position and pressure.

Three towers. Three ways to think.

• Sentry — a direct weapon whose target and ammunition choices matter.
  
• Lance — a deliberate line shot that rewards timing and alignment.
  
• Warden — a support controller that scans, marks and slows threats for the rest of the plan.

Each placed tower keeps its own controller. Save a useful program as a blueprint, reuse it elsewhere
and adapt the local copy without destroying the original.

The board is part of the code.

Maintenance zones offer real placement choices rather than fixed universal sockets. Elevation can
extend useful reach. Barriers and rooftop structures can break line of sight. A perfect rule in the
wrong position is still the wrong solution.

Test it. Understand it. Deploy it.

Run a lab rehearsal to watch a tower's exact decisions. Pause, step and rewind the result, then
inspect why a target was chosen. When the plan says what you mean, deploy it into the live fight.

Clearing the route is only the first result. Protect the relay, respect hardware and block budgets,
and solve without unnecessary live changes to earn the strongest evaluation.

Logic puzzles inside a real tower defence.

The campaign is built for people who have never programmed as well as players who enjoy optimizing
a clean solution. SOFIA guides the maintenance channel, but the final behaviour is yours.

• Single-player tower defence driven by visual programs
  
• Readable IF/ELSE, comparisons and logical operators without typed syntax
  
• Sentry, Lance and Warden controllers with different tactical roles
  
• Placement, elevation and line-of-sight puzzles
  
• Deterministic rehearsals with causal inspection
  
• Reusable blueprints and per-tower local edits
  
• Optional hardware and code-block optimization goals