## Moves ##

Moves are written as a comma separated list of commands to be pressed in sequence.

* __Numbers:__ Direction (numpad)
* __Letters:__ Attack buttons (currently, _A B C D_)

So

     2,1,4,A

means press and release _down_, press and release _down-left_, press and release _left_ and finally press _A_.

## Fighter ##

Fighters are state driven. The current states and transitions are

	Drawing of what the states and transitions are right now (or the states for Harold). Maybe with a simple label for transition type/condition.

Input based transitions are distinguished by a thicker line.

Fighter also stores the user's input.

## Status ##

A list of statuses affect a fighter each frame. Statuses on a fighter are obtained from

* Entering a state
* Other fighter's action (?)
* The environment (?)

Statuses from a fighter are removed by

* Timeouts
* State exit

## Initialization ##

A file specifies the state and transitions for each playable character in the following way.

_What follows looks like the description of a class and its (possible) members. Is there any particular reason you want this stored as string instead? Because it can be altered at runtime is my only guess now._

_It also looks like [STATE] should be [MOVE] right now._