Unity Light

Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.

Triggers

• Adding or tuning lights
• Setting up scene lighting
• Batch-enabling/disabling lights
• 添加或调校灯光、布置场景照明、批量开关灯光

Unity Light Skills

BATCH-FIRST: Use *_batch skills when operating on 2+ lights.

Operating Mode

• Approval (default): mutating skills (light_create, light_set_properties, light_set_properties_batch, light_set_enabled, light_set_enabled_batch, light_add_probe_group, light_add_reflection_probe) need user grant; grant triggers a single server-side execution that returns the result.
• Auto / Bypass: those skills execute directly.
• Query skills (light_get_info, light_get_properties, light_find_all, light_get_lightmap_settings) are SkillMode.SemiAuto — they run in all three modes without grant.
• This module contains no Delete / PlayMode / Reload / high-risk skills (no NeverInSemi); to remove a Light, call gameobject_delete from the gameobject module.

Guardrails

DO NOT (common hallucinations):

• light_add does not exist → use light_create (creates a new light GameObject)
• light_set_color / light_set_intensity do not exist → use light_set_properties (sets color, intensity, range, shadows together)
• light_delete does not exist → use gameobject_delete on the light's GameObject
• light_set_shadow does not exist → use light_set_properties with the shadows parameter
• shadows values are the Unity enum members None / Hard / Soft. Input is matched case-insensitively ("soft" still works) but responses always echo the capitalised form, so compare against Soft, not soft, when verifying

Routing:

• For lightmap baking settings → light_get_lightmap_settings (this module)
• For reflection probes → light_add_reflection_probe (this module)
• For light probe groups → light_add_probe_group (this module)

Object Targeting: All single-object skills accept name (string) and instanceId (int, preferred). Provide at least one. path (hierarchy path) is also accepted where noted.

Skills Overview

No batch needed:

• light_create - Create a light
• light_get_info - Get light information (light_get_properties is an alias of it)
• light_find_all - Find all lights (returns list)
• light_add_probe_group - Add a Light Probe Group with optional grid layout
• light_add_reflection_probe - Create a Reflection Probe at a position
• light_get_lightmap_settings - Inspect Lightmap baking settings

Light Types

Skills

light_create

Create a new light.

Returns: {success, name, instanceId, lightType, position, color, intensity, shadows}

light_set_properties

Configure light properties. Every parameter is optional and omitted ones keep their current value.

Returns: {success, name, applied, skipped, lightType, color, intensity, range, spotAngle, shadows} — applied lists the parameters that took effect, named exactly as you passed them (the colour channels appear individually as r, g, b, a, not lumped under color), and skipped the ones the light type cannot carry (a range on a Directional light, a spotAngle on anything but a Spot), each with the reason. A parameter in neither list was not supplied.

An unrecognised shadows value rejects the whole call with SEMANTIC_INVALID + validValues and applies nothing, so a typo can no longer leave a half-configured light behind.

light_set_properties_batch

Configure multiple lights. Each item accepts: name/instanceId/path (identifier) + r, g, b, a, intensity, range, spotAngle, shadows (all optional). This batch is all-or-nothing: a bad shadows value fails that item with SEMANTIC_INVALID + validValues and names the object in target, and rolls back every item the call already applied.

Returns: {success, totalItems, successCount, failCount, results: [{target, success, lightType, applied, skipped, color, intensity, range, spotAngle, shadows}]} — applied/skipped follow the same rules as light_set_properties (a range on a Directional light, or a spotAngle on anything but a Spot, is listed in skipped, not an error).

unity_skills.call_skill("light_set_properties_batch", items=[
    {"name": "Light1", "intensity": 2.0, "r": 1, "g": 0.9, "b": 0.8},
    {"instanceId": 12345, "intensity": 1.5, "shadows": "soft"},
    {"name": "Light3", "intensity": 2.0}
])