* Four fings for wargfood
** DONE Make Heroes
  - [X] route to serve the form
  - [X] form to enter a name
  - [X] route handler to take the post & persist object
** DONE Enter the tavern
  - [X] Wot's Yer Name, Fella? (make the form)
  - [X] handle post (set a cookie/header)
  - [X] make a tavern page
** TODO Make Campaigns
** TODO Make Monsters (in campaigns)
** TODO Attack Monsters (assign heroes / change status)

* More fings for wargfood
** TODO Setup Auth / User Reg
** TODO Deploy


* Notes & Concepts
** Nomenclature

| Project Managment Term        | Dnd Term                      |
|-------------------------------+-------------------------------|
| Task                          | Monster                       |
| User / Team Member            | Hero                          |
| Landing Page: Overview        | Tavern                        |
| Authorization                 | Doorkeeper                    |
| Sprint                        | Quest                         |
| Project                       | Campaign                      |
| User account creation         | Shrine                        |
|                               | Equipment/Loot                |
| Assignment To A Task          | Melee                         |
| Task Category / Tags          | Monster characteristics       |
| Miss Deadline / Take too long | Hero Death                    |
| Time Budget                   | Hit Points                    |
| Make a task                   | Report Rumor of Beast/Monster |
| Areas of Expertise            | Character Class               |
|                               | Level / Experience            |


Campaigns can have a pace. The pace is used to deduct hitpoints when
nothing happens. Penalty for retreating: Roll a die,lose something
(hp), (equip).  


** TODO Plan Out Task Categories and Character Classes More Thoroughly

Here's the idea: Monsters have characteristics. Heroes' character classes
are determined by the kinds of monsters they defeat.

Should we pick discrete classes of character? Discrete classes of monsters?

E.g. Goblin wizard = ???
     Gelatinous Cube = ???

| Task Category   | Monster Class (smaller)         | Monster Class (Bigger) |
|-----------------+---------------------------------+------------------------|
| Feature         | Boss (dragon warlock elemental) | e.g dragon             |
| Task-SubFeature | orc, goblin, (minions)          | orc chieftan           |
| Task-StandAlone | not-minions (wolf)              | minotaur               |
| Bug 1           | (the undead)                    |                        |
| Bug 2           | (horrible undead)               |                        |


| Different Task Categorization                        |
|------------------------------------------------------|
| coding & debugging (& reproducing bugs) & unit tests |
| user testing                                         |
| devops                                               |
| art                                                  |
| documentation                                        |
|                                                      |

*** Non-task merit earning action

- reporting a rumor that is verified
- verifying a rumor (?)
- lose merit if you rumor is considered specious
- adding context to a rumor (maybe other people give a +1)
- aiding another hero somehow
  

*** Note :  monster reporting and reclassification

When a feature/task/bug is "rumored", the "verifier" should be able to
reclassify it.

there could even be monster promotion mid battle. If it is revealed
that a monster is much much more deadly than initially thought.