Hello! Currently we have: warzone.wz, which contains the basic stuff and the campaign data. And mp.wz which contains differences for multiplayer games. I would like to change the naming to better work out those differences.
My current ideas: - base.wz: Contains the stuff needed by everything - cam(paign).wz: Contains just the campaign relevant things - m(ulti)p(lay).wz: Contains just the multiplayer relevant data I think that would make it clearer for modders where which files can be found, what is relevant for what types of mods, etc. In addition to that, I would propose stackable mods (mods can have 0 or 1 dependencies, which they are stacked upon). Means: If I want to do a mod which replaces a few textures, I stack on base.wz, which ensures that (a) when I am mounted, base.wz is in PATH, too, and (b) that I am located before base.wz in PATH. To support that I would add a metadata file for each .wz, which contains basic information like on what it is stacked (falling back to base.wz if missing). Additionaly, we could provide fields for authors, email, web-address, license, and possible scripts to run on mount, etc. This would go into trunk aka 2.2 and possibly reuse experience and partly code from my earlier WRF experiments. The first part (splitting of .wz's) is probably easier and stacking behaviour could be hardcoded for a while. I've noticed some rumors about wrf-less mods, which could maybe be done in one run with this. I would like to get a proposal for how this could work, for which filetypes (if not all), about flexibility and other impacts, etc. --Dennis
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
