Enemy Authoring
Define an enemy's identity, HP range, prefab, and the graph that chooses and resolves its intents
Open the Game Card Editor and choose Enemy; enemy mode keeps authored stats, the behavior graph, a live prefab render, and intent analysis together
Authoring order
- In List, select an enemy database, then create a blank enemy or duplicate a unit with a similar role
- In Inspector, complete Basic, Visual, Attributes, and Behavior
- In Preview, check Display, Render, Behavior Summary, and Intents
- Finish with Used By to verify which encounters can spawn this enemy
List area
List
Use +, −, and duplicate after choosing the target database; search filters by name; Tier and Tags narrow the list by difficulty role and project labels; each row shows portrait, name, tier, and inclusive HP range, so the list also works as a quick balance overview
Inspector area
Basic
| Field | What to configure |
|---|---|
| Name | In-game enemy name; a non-empty value also renames the sub-asset |
| Description | Short role or flavor text for UI presentation |
| Tier | Normal, Elite, Boss, or a custom project value used for grouping and filtering |
| Tags | Labels used by filters, selectors, and your own battle logic |
Tier is descriptive until your own systems read it; it does not automatically multiply HP or damage
Visual
Assign Icon for portrait presentation and Template for the prefab spawned in battle; the Render preview uses Template; list rows and Display use Icon
Attributes
HP Min and HP Max define an inclusive starting-HP roll; the editor keeps HP Min at 1 or higher and HP Max at or above HP Min; use equal values for deterministic encounters; use a range when small run-to-run variation is intentional
Behavior
Click Edit FlowGraph to author intent selection and enemy actions; the chips below the button summarize graph counts such as pattern nodes, leaf intents, and actions; A complete enemy graph must both choose what the UI announces and resolve what happens during the enemy phase
Intent patterns can be sequential, weighted, conditional, or one-time; the chosen leaf intent supplies the planned action; action paths then change battle state and play presentation effects; if the UI shows an intent but the turn does nothing, inspect the action path rather than the encounter
Preview area
Display
Display combines Icon, Name, Tier, and Description into the compact enemy identity used by UI; check that a player can distinguish role and threat without reading the graph
Render
Render instantiates the assigned Template; rotate, pan, zoom, and reset the view to check the prefab's silhouette, pivot, scale, and framing; A correct Icon cannot reveal a broken battle prefab; this frame can
Behavior Summary
Behavior Summary lists the graph entry path in compact form; it confirms that the enemy has an OnEnemyBehaviorStart route and shows the first structural step, but the full graph remains the source of truth for conditions and actions
Intents
Intents reads the authored graph and summarizes reachable leaf-intent groups; the proportional bar and labels show the current Attack, Defend, Multi, or other categories discovered in the graph; use it to catch an enemy whose visible plan set does not match its intended combat role
This is structural analysis, not a simulation of every runtime branch; conditions, weights, and battle state can still change which intent is chosen on a given turn
Used By
Used By lists encounters whose Enemy Units section contains this enemy; click a result to open the encounter and inspect slot order or repeated entries; no results means the enemy is authored but currently unreachable through an encounter
Validation and final check
An empty name is an error; missing presentation assets, an invalid HP range, an empty behavior graph, and graph validation problems are reported in the Workbench
Before moving on, confirm the list row communicates the expected tier and HP, Render shows the correct prefab, Behavior Summary contains the enemy entry, Intents matches the intended move set, and Used By reaches the expected encounters