1.8 KiB
STS2 Bot
Terms for observing Slay the Spire 2, choosing actions, and evaluating play.
Language
Run: One game attempt, from its start to victory, death, or abandonment. A seed describes generated content; it does not uniquely identify an attempt.
Session: One period of bot operation. A run can span sessions, and a session can span runs.
Observation: The game information visible at one moment. It is not the complete game state.
Fact: A directly observed value or a result established from known game rules and sufficient inputs. Avoid: Using this term for an unverified prediction.
Estimate: A prediction that depends on assumptions or incomplete game information. Avoid: Guaranteed result, proven lethal
Decision: A proposed next action. A decision does not establish that the game received or applied the action.
Action result: The game's response to an attempted action. Acceptance alone does not establish that the expected change occurred.
Pending game action: An accepted action request that has not yet been reconciled with a fresh observation. Avoid: Completed action
Accepted toggle: An accepted request to change a card's selection status. It does not prove that the card is selected.
Screen flow: Related game screens that form one interaction, such as opening and skipping a card reward.
Run deck: The persistent collection of cards owned during a run, distinct from temporary combat cards and combat piles. Avoid: Treating all visible combat cards as the persistent deck.
Run outcome: The result and progress of one game attempt. It does not establish whether each earlier decision was correct.
Decision label: An assessment of one decision against a stated criterion, such as legality or an expert preference. Avoid: Treating the run outcome as an optimal-action label.