Currently, there are several items, mainly deck editor filter lists, that are written as array (tuples) in the code files.

We should move this data to external files for easier updating later.

Maybe we should look at storing the data in xml format as well.

Reason for addition or change: This will ease updates, maintainability and future functionality development.

What version of EoPK are you currently using?0.9.0

As I said in i28, I'm ok with xml as a data storage unit. I can come up with a schema for the data files.

We would need a validator to ensure the xml file is the proper format and we would need a parser to turn the xml data into Python variables. Python may have a module to handle XML and possibly code to handle xml validation given an xml file and its schema file.

Going this route, would we want to turn the user configuration data into an xml file as well?

I have changed the main program entrance to the program.py and now all eopk script files should be in the sys\library.zip file.

This means that when the code gets updated, all we need to do is replace the sys\library.zip on the client.

That will be the next step.

As of r70 all the main game code files are external to the executable.

This means that we should be able to go forward with building an automatic updater.