New version of engine.json based on new schema

This isn't ready for primetime, but it is a start.
The new_engine.json is a concrete example of the
Construct --> Scheme --> Content approach I worked
out in the API Google Doc. It is a messy cut/paste
job that needs cleanup and testing but it's a start.
New version of engine.json based on new schema

This isn't ready for primetime, but it is a start.
The new_engine.json is a concrete example of the
Construct --> Scheme --> Content approach I worked
out in the API Google Doc. It is a messy cut/paste
job that needs cleanup and testing but it's a start.
Updated engine.py and tests

Everything now works with the new engine.json.
This is a proof of concept commit. If I stick
with this structure for engine files, I will
need to make a number of improvements to
engine.py. More precisely, engine.py will
have to be smart enough to know how to make
a character without knowing which Schemes
to expect in the engine.json file.
Merge branch 'structure' of github.com:AgathaTheWitch/Otrera into structure
New version of engine.json based on new schema

This isn't ready for primetime, but it is a start.
The new_engine.json is a concrete example of the
Construct --> Scheme --> Content approach I worked
out in the API Google Doc. It is a messy cut/paste
job that needs cleanup and testing but it's a start.
Updated engine.py and tests

Everything now works with the new engine.json.
This is a proof of concept commit. If I stick
with this structure for engine files, I will
need to make a number of improvements to
engine.py. More precisely, engine.py will
have to be smart enough to know how to make
a character without knowing which Schemes
to expect in the engine.json file.
Merge branch 'structure' of github.com:AgathaTheWitch/Otrera into structure
ROADMAP and TODO updates
Restructed content.json for new data model

This commit breaks tests, so hopefully I won't
dilly-dally on finishing the bigger task.

The goal here is to make content.json reflect the
Construct --> Scheme --> Content data model. This
required shifting around a lot of keys and rewriting
much of content.json by hand.

The goal is to have content.json be almost entirely
root keys that refer to pieces of content. The only
exceptions are the "List" and "Types" keys, which
are embedded in content.json for a few convenience
methods (more on that later)

This commit accomplishes this first goal. Next is the
likely more irksome task of trying to make engine.py
work with this new model.
Fixed engine.py to work with new data model

Tests are passing and the player module works
too. There are some little decisions I'll have
to revisit. Things like capitalization, style.
Also, as I've said before, engine.py needs to
get a lot smarter.

This commit paves the way for merging the
structure branch with master. Just need one more
commit getting the add and edit content modules
working.
Propery added concept of types to engine and game

Not sure if this data model will stick, but it
works for now!

There are now 'Type' objects in the game's
content.json. These are created from a template
in the engine.json. For now these objects only
have two functions:

1. Create restrictions on content based on
character traits. For example, make it so that
swords can only be used by fighters, or an ice
spell can only be used by females, etc.

2. Define some field on a piece of content based
on its type. This is for situations where you want
to create subcategories of schemes. For example,
you do not want to separately define the defense
rating of every piece of armor. Instead, you want
all metal armor to have defense = X, and all
leather armor to have defense = Y, etc.

There are some limitations as to the sort of data
you can use in these two cases, and the parser will
need to be smart about certain cases.
Updated the addContent module

addContent can now add content!

Loose thread: Need to re-create the update_LISTS
method. There is a big dictionary of lists in
content.json for easy searching. Whenever new
content is created, the name has to be added there.
Should be a quick patch.
Fixed editContent to work with new structure

We should be ready to merge structure with
master. OOh Rah!
Merge pull request #13 from AgathaTheWitch/structure

Structure