Ludic Objective

A Ludic Objective is a task with a target state and a condition of fulfilment: what is to be achieved and how it shows that it has been achieved - checkmate, more goals than the opponent, the last card played, the dragon at zero hit points. It is mandatory or optional and stands in a hierarchy of intermediate and ultimate goals. It is set by the Ludic Corpus or by an agent: whoever gives themselves an objective - the best time in a speedrun, the castle in the sandbox, the self-imposed restriction - makes a determination and thereby shifts the boundaries of the corpus, as far as their Ludic Sovereignty reaches. In sandbox games this is the normal case.

The objective is a regulation with terminal scope, a special form of Ludic Regulation: it determines when something counts as fulfilled. It says what for one acts - the Ludic Activity says what one does, the Ludic Argumentum why. The objective is not the drive: the task stands in the corpus, the agent brings their own why (Human Agent Motivation). An agent can take on a posed task, leave it aside or set one of their own; the difference between a posed and an adopted task is the design asymmetry.

In everyday language

• “goal” (largely): What is to be achieved in the game and how one can tell it is achieved (“the goal is to …”). Does not distinguish the task the game sets, the intention of the designers and the drive of the players.

Place and design access

Place on the axis: CORPUS - the objective is a determination of the corpus, even when an agent sets it: the agent then acts on the corpus by virtue of their Ludic Sovereignty. It is not a pattern: what makes up an objective can be reconstructed from scope, target state and evaluation; its stack orders types and aspects.

Design access: designable - target state, condition of fulfilment, hierarchy and degree of obligation are determined. Whether an agent takes on the task is not designable but addressable.

Relations on the axis:

• CORPUS: the objective is a special form of Ludic Regulation - regulation with terminal scope - and inherits its edges; its condition of fulfilment is a condition in the sense of regulation. Not every regulation poses a task: free building does without. The Ludic Activity opens the space in which objectives are pursued - an ultimate goal can also lie above all activities; Ludic Actions serve their fulfilment. The Ludic Argumentum grounds the objective in the fiction, where there is one - not in chess. The Ludic Appearance communicates it: goal display, progress, victory screen. With the Ludic Temporal Structure it corresponds: the victory condition often coincides with the end but is not the same (§5).
• FORM: the form spans the space of possibilities of objectives - which tasks can be posed and who ascertains their fulfilment: the program in a digital game, to the hundredth of a second, the players at the table.
• PROCESS: in the process it is checked whether the condition of fulfilment obtains. The ultimate goal holds terminally; intermediate goals are fulfilled in the middle of the match and set the pace.
• AGENT–PROCESS: objectives influence the Ludic Fabula - goal, comeback - and help organise the Ludic Ductus on the side of the game: nearness to the ultimate goal escalates, a reached intermediate goal relieves. Their fulfilment influences what has an after-effect on the agent (Ludic Effectus).
• AGENT: the objective addresses Human Agent Motivation without determining it: it offers a task; what agents want, feel and whether they take it on lies with them. Following Leontiev, it stands at the level of action: what is offered is the posed task, what lies with the agent is the adopted or self-set one.
• AGENT–CORPUS: Ludic Sovereignty authorises agents to set objectives for themselves or to change posed ones - widely in Minecraft, not at all in chess. The Ludic Frame constrains which objectives are coherent in it: in a crime story one convicts the culprit, in a city builder one does not.
• INTENT: the Ludic Desiderata inform which tasks a game poses.

The trias at this concept

At the objective “defeat the dragon”:

Regulation - target state and condition of fulfilment: the dragon’s hit points are at zero; then the gate opens. Appearance - how the task is communicated: the health bar above the dragon, the quest log entry, the music that swells on a hit. Ascription - what the fulfilment counts as in the fiction: “free the kingdom” - or “kill the last animal of its kind”.

Where regulation and ascription diverge, coherence costs arise: a functionally clear objective staged as a heroic triumph can open a moral rift - unintended or as critical design, as in Spec Ops: The Line. Many objectives stand at the zero point of ascription: checkmate means nothing outside the game.

Delimitations

Delimitation from Human Agent Motivation

Against Human Agent Motivation: task and drive. The objective is the task - determined, with a condition of fulfilment, whether or not an agent takes it on. Motivation is the drive from which an agent engages; the agent brings it along. One player can leave the main goal aside and still play with joy, another follows it exactly. Whoever sets themselves a task invents not a motivation but an objective.

Delimitation from Ludic Argumentum

Against the Ludic Argumentum: what for and why. The argumentum justifies the task in the fiction - a premise and the reason why one must act now. The objective determines when it is fulfilled: “save the village” - “dragon at zero hit points”. The argumentum can stand at the zero point: in chess the urgency comes solely from the winning condition and zugzwang, and the why lies wholly in the objective.

Delimitation from Ludic Temporal Structure

Against the Ludic Temporal Structure: fulfilment and end. The temporal structure determines when a process ends - after 90 minutes, after the last round, when no cards are left. The objective determines when a task is fulfilled. The two often coincide but are not the same: a 0-0 ends without a win, a stalemate without checkmate, and Tetris ends without any victory condition at all.

Examples

• Chess: ultimate goal checkmate, not deniable. Stalemate ends the game without anyone winning - end is not victory.
• Civilization: several victory conditions side by side; the players choose which to pursue.
• Breath of the Wild: the ultimate goal can be left almost entirely aside; the world is dense with intermediate goals and optional tasks.
• Pandemic: a shared condition of fulfilment, no victory condition against the co-players.
• Tetris: a task without a victory condition - hold out as long as possible, raise the score.
• Speedrun and sandbox: the best time under 60 minutes or the castle in Minecraft are set by the players themselves - determinations by virtue of their sovereignty.
• Dixit: the task depends on the role - whoever tells wants to be guessed by some, not by all.

Explanation

Every game poses tasks - sometimes explicitly (“score 100 points”), sometimes unspoken (“survive as long as possible”), sometimes nested (“build a civilisation and lead it to victory by one of four paths”). These are the Ludic Objectives, in German Spielaufgaben. Some you also set yourselves: the best time, the finest castle, the run without damage.

A task is not the same as a drive. The game poses the task; why someone plays, they bring along themselves. One follows the main goal exactly, another leaves it aside and still has fun.

Design questions: how does the game recognise that the task is fulfilled? In competitive games this is a victory condition, but not every task has one. Is there one big goal and intermediate goals that lead to it? Must the task be pursued, or is it voluntary? What kind of task is it - reach, find, create, improve, solve, remove, defend? And: does the game end when the goal is reached - or are those two different conditions?

Usage context

Dimension	Classification
Phase	Development (primary: shape tasks, success and victory conditions, the hierarchy of ultimate and intermediate goals and determine them as regulation); ideation (secondary: an objective-driven game? how deniable?); evaluation (did the objectives carry the hoped-for courses and effects? reachable, legible, fair?)
Tool type	generative (objective stack, section A: types) and structuring (section B: aspects - statement, success condition, victory condition, hierarchy, deniability, type)

Theoretical foundation

• Debus (2019), Unifying Game Ontology (main source): adopted are the hierarchy of ultimate and proximate goals, the ten imperative goal types (as an open palette), the distinction between victory and end condition, the universals permanent/transient and deniable/undeniable. Modified: Debus’s “goal” oscillates between game and agent - LUNA separates the task in the corpus from the drive in the agent.
• Juul, Half-Real: “valorized outcome” as a precursor of the victory condition.
• Salen and Zimmerman, Rules of Play: “winning conditions” and “goals” as a central design element.
• Schell, The Art of Game Design: goals as one of the four core elements.
• Costikyan, “I have no words & I must design”: goals as an indispensable component.
• Leontiev, Activity, Consciousness, and Personality: activity, action, operation - the objective stands at the level of action, with the deviation that in LUNA the corpus poses the task.
• Delimited: Deci and Ryan (SDT) ground Human Agent Motivation, not the objective.

Aspects

Aspects (section B of the stack, OB-A1 to OB-A6; not a closed taxonomy): objective statement (explicit or unspoken); success condition (determined as a condition of the regulation); victory condition (the competitive special form of the success condition - an aspect, not a term of its own); hierarchy (ultimate versus intermediate goals); deniability (mandatory or voluntary); objective type (the kind of target state).

Types (section A, OB-01 to OB-14): Debus’s ten imperative goal types as an open palette, not a closed taxonomy - only target states, not activities; Reach only spatially or as a threshold -, plus LUNA’s own types. Four classes:

Class	Types
core - standalone target states	Reach · Remove · Find · Solve · Optimize · Deliver
action-adjacent - only with a success condition	Obtain · Create · Configure
objective-or-action - only when the state itself is the goal	Choose · Synchronize
preserving - maintaining rather than changing	Survive · Defend · Evade

The types overlap (family resemblance); that is the reason for keeping them as a palette.