-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make templates for everything in YAML #12
Comments
fabio-t
added a commit
that referenced
this issue
Nov 5, 2017
…mplex yaml parsing, but still not there - yet
fabio-t
added a commit
that referenced
this issue
Nov 10, 2017
…ml files; I can directly use the artemis-odb component which is great
fabio-t
changed the title
Make templates for all entities in YAML
Make templates for everything in YAML
Nov 12, 2017
Item templates are almost done - the structure is there and it already works (tested with crafting). What needs to be done is putting the right character and colour for each item, and changing all specific functions like |
fabio-t
added a commit
that referenced
this issue
Nov 14, 2017
fabio-t
added a commit
that referenced
this issue
Nov 27, 2017
…or basic terrain types; also, for #12, terrain data is loaded from yaml files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The smart way would be to implement a yaml serialiser/deserialiser for artemis-odb itself, so as to have component mappings.
But we'll go the easy way first: parse the yaml file and manually check a list of possible keys, then convert them to components as appropriate.
We are already doing it for primary attributes (and then we create secondary attributes), but stuff is still missing:
The text was updated successfully, but these errors were encountered: