The player fantasy

Required

Every game starts with what the player gets to be and feel. OpenGDD asks for that first, in a short fantasy block at the top of 01-overview.md. The block comes before any rule. Only a # title line, or an HTML comment, may stand above it.

01-overview.md, straight after the title

You are a small forest spirit, a mote of light in a dying woodland.
You leap, cling, and glide through roots and ruins, rekindling what the decay took.
The forest grieves in silence, and answers every light you restore.
Feel: luminous, melancholy, hopeful.
NOT: grimdark, gory, hopeless.

The block has three parts:

one or more fantasy statements: what the player is and does, at most 280 characters together;
one Feel: line with three to five adjectives;
one NOT: line naming the tones, genres or directions the game must avoid. You may write Anti-references: instead of NOT:.

Each fantasy statement ends with ., ! or ?. A statement may wrap across lines. One statement is enough. If you add more, each should describe a different part of the experience.

The builder uses the block to decide everything the rules leave open. The builder is the person, team or AI that turns your package into a game. In this example, decay should feel sad rather than horrifying, because the block says NOT: grimdark.

What the block is not:

Not marketing text. It is written for the builder.
Not a feature list. Later chapters define the features.
Not a place for references. Names of tuning values, runtime values, typed references such as tuning: or palette:, and links to other chapters are not allowed here. Plain numbers are fine.

The validator (the checking tool) counts the characters and the adjectives for you. If anything else comes before the block, it reports the code FANTASY_POSITION.

Full rules: OpenGDD specification, §1a.