Notable Breaking Changes

[hallister]

@b-cumber @Greg-Donaldson @crockj72

This is going to affect you guys the most. I'm going to be pushing some major changes to the orm branch this weekend:

• A new demo.yaml "scenario" is going to be added. This isn't a true scenario but an example one we can use for testing.
• The current database loading mechanism will be removed, to be replaced by a config generated by whatever game is selected. By default, this will load demo.yaml.
• .dat parsing files will be removed. We will no longer need them with the move to YAML config.
• the database Session will be created by the server and passed into functions/methods by the API.

If you are currently working on something that breaks as a result of these changes, please push to a new branch and let me know so I can remerge into master at the appropriate time.

As we are no longer using dat files, the method we use to store dat file data will also change (for example, the actions.dat files has a bunch of weird "nicknames" and abbreviations we won't use at all).

[Greg-Donaldson]

So... are we only going to be supporting scenarios now?

[hallister]

Yes and no. A scenario (in our sense of the word) can be anything from a specific game scenario to everything in the game. But for now I think the goal is to get a functioning playable scenario, at the very least.

[andyleejordan]

I've been under the assumption that our server-team development took place on your repo, I wasn't receiving notifications for new issues on this one.

[hallister]

Forked repos don't have an issues tab.