If an archetype is specified in the spawn, but the user sends a regular
Entity definition, we need to move the attributes defined by the user to
the first entity in the archetype. This is because once the spawn has
operated on the entity, it will also be of type "archetype" and any
extra properties in the root entity will be ignored by the archetype
factory.
There's no reason to use the hacked in "contains" feature for creating
inventory. Instead we can rely on the Archtype features. Any entity
declaration for which we also want inventory created should use an
archetype.
The change is that the "contains" and "character_types" attributes are
removed. Instead there's a "entities" attribute, which is a map. The
keys are the names of the entities as seen to the client, and the values
are the entity specifications.
The "respawning" property makes an entity respawn instead of being
deleted. It intercepts the Delete op and instead of deleting the entity
it moves it to the specified spawn point.
A typical use case of this is to place the property on any user
controlled entity, thus making sure that it's never deleted and istead
respawned when killed or defeated.
All IG code should use the interface of LocatedEntity when dealing
with any entity, rather than sometimes requiring Entity. Add virtual
functions to the interface where required, and modify all other interfaces
to stop them using Entity. This makes the code way cleaner, and much better
de-coupled.
This means we have changed the code to use our shape classes to store the
data, and modified the expected Atlas format to match the more standard
way of expressing shapes in Atlas which the shape classes expect.
