# Multiplayer Boss Design Philosophy

This project focuses on 4-player cooperative boss encounters.

Bosses are not just enemies.
Bosses are cooperative execution challenges.

## Core Design Philosophy

Boss encounters must test:
- role execution
- positioning
- pattern recognition
- sustained coordination

Boss encounters should not primarily test:
- raw stat checks
- random power spikes
- build luck

## Role Model

Roles are soft ratios.

Players are not locked into hard classes.
Each player contributes a mixture of:
- Tank ratio
- DPS ratio
- Support ratio

Bosses should require total role pressure fulfillment, not specific class presence.

## Combat Identity

Combat is:
- non-target action
- directional dodge-based
- positioning-focused

Survival should depend more on execution than on numerical advantage.

## Signature Pattern Philosophy

Each boss must contain at least one defining signature mechanic.
That mechanic must:
- create a clear player problem
- have a clear expected solution
- produce a clear failure result

Ambiguous solutions are discouraged.

## Revive Philosophy

Revive is allowed, but revive must be risky.
Bosses should react to revive attempts.
Revive should increase encounter tension, not reduce it.

## Sustain Philosophy

There is no hard time limit by default.
Instead, bosses should escalate over time.
Encounters must become harder if players fail to execute properly.

## Build Philosophy

Build strength should support execution.
It should not replace execution.
Players should adapt builds, not brute-force encounters.

## Encounter Identity

Boss equals encounter.

Bosses may include:
- multiple entities
- supporting units
- positional hazards

Adds must serve meaningful gameplay roles, never filler.