Algo Design: Scenarios

Scenario: The event series (as text output) modified by a character's stats.

Scenario example:
Event 1: Olmec is offered a challenging task.  (environmental prompt)
Event 2: Olmec turns down the challenging task. (character response)
Event 3: Effects (stat changes) on Olmec and his environment due to his decision such as an increase or decrease in stress and life difficulty. (environmental response)

Comments

Post a Comment

Popular posts from this blog

App Idea: Task Ranker

 July 23rd, 2025 Priorities: Ranks your tasks according to how well they match your core values. Your core values each carry an importance score. Higher scores mean a more cherished value. A task is rated on how well it fulfills a core value. Such an app would provide the user with the most meaningfully rewarding task at any given moment. Addendum, August 3rd, 2025: I call this measure 'eudaimonic utility.' The higher the meaningfulness of a task, the more eudaimonic utility that task represents. This can be contrasted with 'hedonic utility,' which measures pleasure. Eudaimonic utility can also be contrasted with 'experiential utility' which measures the satisfaction of psychological richness or variety. Reading: -Chapter 2 of Human Compatible by Stuart Russell -Life in Three Dimensions by Shigehiro Oishi
Read more

Ledgers, Ledger Objects, Event Scripts, Statuses and Scenarios

Here, ALO and ELO stand for Agent Ledger Object and Environmental Ledger Object, respectively. Both are examples of Entity Ledger Objects (ELOs from here on out). Event Scripts modify the features and associated stats of ELOs. Status is the text description of an ELO state or change. The Scenario is formed by the interaction among one or more ELOs, their Event Scripts and Statuses. This post is a continuation of: https://quantasticjourney.blogspot.com/2024/11/narrative-development-environment.html?m=1
Read more