Data file format is unreadable

[verhoevenv]

The .dat files are unreadable, unwritable and unmaintainable. We should move to either something more readable (JSON-like?) or a full-blown scripting language.

It seems useful that we can either keep the current format working, make the new format backwards compatible or provide tools to migrate to a new format.

The new format should not be less powerful, in the end.

[Enet4]

I would go for an existing base format such as XML or JSON, but maybe we can obtain nicer scripts with a new notation.
But I think we should look at the full data model first. Do you happen to have a diagram, or something describing the models and their relations?

[verhoevenv]

Thing is that it's not only data. The effects and conditions are actually behavior. This means we will only get so far with JSON or XML or such thing. It's very limited sorts of behavior, which we could keep as such with some renaming, but it might be a good idea to move to a scripting language in which we get all sorts of conditions and effects for free simply by exposing the right objects + the inherent control structures.

[Enet4]

Sure thing, but if you think of it, scripts ARE data with a syntax. The only main difference is that a script always describes a workflow for some task. JSON or XML is still a superset in terms of what can be represented.

Anyways, we could look into a mid-term, such as JSON with some strings containing interpreted code in some other (possibly custom) language.