add health and damage so the player can die

Health, damage, and respawn are SCRIPT PATTERNS, not components. Track health as a numeric warehouse field, subtract it on a trigger or action handler with incrementNumericState (negative by), detect death by comparison, and respawn with spawnEntityFromTemplate. Author it through the AI-safe semantic patch ops.

deal damage on hit and respawn the player

Health, damage, and respawn are SCRIPT PATTERNS, not components. Track health as a numeric warehouse field, subtract it on a trigger or action handler with incrementNumericState (negative by), detect death by comparison, and respawn with spawnEntityFromTemplate. Author it through the AI-safe semantic patch ops.

health that drops when hit and death respawn

Health, damage, and respawn are SCRIPT PATTERNS, not components. Track health as a numeric warehouse field, subtract it on a trigger or action handler with incrementNumericState (negative by), detect death by comparison, and respawn with spawnEntityFromTemplate. Author it through the AI-safe semantic patch ops.

combat where enemies hurt the player

Health, damage, and respawn are SCRIPT PATTERNS, not components. Track health as a numeric warehouse field, subtract it on a trigger or action handler with incrementNumericState (negative by), detect death by comparison, and respawn with spawnEntityFromTemplate. Author it through the AI-safe semantic patch ops.

Combat damage health and respawn scripting

The recipe

Author with project_apply_script_semantic_patch (AI name apply_script_semantic_patch) using only the ai_safe operation pack. Every op that lives inside a handler takes scope: { "kind":"handler", "handlerRef": <handlerKey> }.

Seed health as durable state: writeTypedStateValue { "storeKey":"progress", "recordKey":"player", "field":"health", "valueType":"number", "value": 100 } (defaults storeKey progress, recordKey player).
Make the attacker's shot a verb: addActionHandler { "actionKey":"fire", "handlerKey":"onFire" } (the input action from input-mapping-actions-bindings). Or make contact hurt: give the hazard a trigger ColliderComponent and addTriggerHandler { "handlerKey":"onHurt" }.
Apply damage inside that handler: incrementNumericState { "scope":{...}, "field":"health", "by": -25 }. Negative by subtracts.
Detect death: readTypedStateValue health into a binding (assignTo:"hp"), then branch. For the simplest match-level check use setBooleanState { "field":"dead", "value": true } when health reaches 0.
Respawn: spawnEntityFromTemplate { "templateKey":"player-spawn" } or { "prefabKey": <prefab key> } with a config of validated inline overrides, and reset health with another writeTypedStateValue back to 100.
For a whole-game outcome, transition the match phase from a GessaScript body with ctx.match.setPhase, or use declareWinCondition for count-based wins.

Pitfalls

Do not attach a component named for health or damage; there is none. Health is a warehouse field.
incrementNumericState mutates durable state and carries requiresAuthority; it runs server-authoritatively. Do not expect a client-only visual to persist.
addTriggerHandler takes NO trigger key: its payload has no trigger-identity field. Distinguish hazards by inspecting firstEntityId/secondEntityId or entity tags inside the handler.
The rich addShooterCollectorLoop op is NOT AI-expressible (visual_editor and template contexts only). Compose the loop from the ai_safe primitives above.
For anything the add-only op alphabet cannot express (custom branching, math), drop to replaceScriptFromGessaScript and call ctx.warehouse.* / ctx.match.* directly.

Verify

simulation_run (qa.run.start) to prove health drops on hit and the entity respawns.
project_get_graph_snapshot to confirm the trigger/action handlers and the ScriptComponent binding exist.

The recipe

Pitfalls

Verify

On this page