id	summary	reporter	owner	description	type	status	priority	component	resolution	keywords	cc
129	Rebuild levels if package contents were changed	Iritscen	Christian	"We got a request from s10k that I think is worth considering. As a modder, he feels discouraged from building a mod package for his new level and using the AEI to reinstall it continuously during development because the AEI will rebuild a whole set of levels instead of just the ones with his changed files. Thus he prefers to just manually change and rebuild levels 0 and 31 (his level's number) without using packages.

I know the AEI already tries to be smart and only rebuild levels with changed mod selections, but in this case there's no change in the ''selection'', only in the ''contents'' of a package. His suggestion was:


""I think you could detect if the package has changed with the following info:
- number of files of the package in the last installation vs number of files in the current installation
- modified date of all files of the package in the last installation vs modified date of all files in the current installation
- md5 (or any other hash of your choice) of all files of the package in the last installation vs md5 of all files in the current installation
If any of the conditions above for any file differs from previous installation you know that the package contents have been changed (and then proceed to the re-installation).

You would need to save the previous installation information somewhere (maybe sqlite or even a file).""

Does this sound reasonable? I think that s10k is not the only modder who has been manually editing his level files. Paradox tends to do the same thing, and I think it's because we haven't given them a convenient enough workflow."	enhancement	new	major	AEI2