Traffic Signals Editor

-- Load and inspect traffic signals in the editor
local editor = extensions.editor_trafficSignalsEditor

-- Load signal data from a custom file
editor.loadFile("/levels/myLevel/signals.json")

-- Get all current signal elements
local elements = editor.getCurrentElements()
for id, elem in pairs(elements) do
  log("I", "", "Element: " .. tostring(elem.name) .. " [" .. id .. "]")
end

-- Get structured signals data
local signals = editor.getCurrentSignals()
log("I", "", "Instances: " .. #signals.instances)
log("I", "", "Controllers: " .. #signals.controllers)
log("I", "", "Sequences: " .. #signals.sequences)

-- Set custom signals data
editor.setCurrentSignals({
  instances = {},
  controllers = {},
  sequences = {}
})

-- Save signals to disk
editor.saveFile()

-- The editor UI provides:
-- * Signals tab: create/select/position signal instances, assign controllers
-- * Controllers tab: define signal types and state durations
-- * Sequences tab: create phased sequences with multiple controllers
-- * Simulation tab: play/pause/stop traffic light simulation
-- * Shift+Click in viewport to place new signal instances
-- * Gizmo-based transform of signal positions and rotations
-- * Smart object selection for linking TSStatic traffic lights
-- * Undo/redo support for all create/delete/transform operations

-- Signal instance lifecycle:
-- 1. Create instance (position in world)
-- 2. Assign a controller (defines signal type: lights, etc.)
-- 3. Assign a sequence (phases that coordinate multiple controllers)
-- 4. Link scene objects (TSStatic traffic light meshes)
-- 5. Simulate to test timing

-- Controller definitions can be customised per-level
-- via signalControllerDefinitions.json