- summary: Fighters appear in the fight: either as ready-made actors or as summon descriptions.
- area: Game.Action
Fighters appear in the fight: either as ready-made actors or as summon descriptions.
Kind struct · Area Game.Action
The GameActionFightEvent.summons action: one or more fighters join the fight
(summoned creatures, invocations, companions). The oneof
Summons.summons says how they are described.
READ IT LIKE THIS
1. Summons.summons_by_actor (SummonsByActor): each new fighter is a complete
ActorPositionInformation - add it to the fight as it is.
2. Summons.summons_by_context_information (SummonsByContextInformation): each
entry describes one kind of summon (SummonContextInformation) and lists its
instances; build one fighter per instance from the entry.
3. The summoner is GameActionFightEvent.source_id.
WHAT THE CLIENT DOES. Both branches end the same way: the client turns every new
fighter into an ActorPositionInformation and spawns it (look, characteristics,
team, cell, visibility).
Not sent on its own — it travels inside GameActionFightEvent.summons. proven
Used by
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | summons_by_actor | SummonsByActor | Set when the new fighters come as ready-made actors - see SummonsByActor. | never |
| 2 | summons_by_context_information | SummonsByContextInformation | Set when the new fighters come as summon descriptions - see SummonsByContextInformation. | never |