mapinfo/modinfo.cfg I'll write 'mod' instead of 'map/mod' in the upcoming paragraphs.
Why modinfo.cfg and not mod.info? And to me the syntax looks a bit crufty (but I guess it is like that because you have a parser at hand for that). What's the sense of gameversion? Older versions of the game won't be able to understand that file (they do not look for it at all) and thus ignore it. Newer versions may be able to understand that file, BUT they MUST NOT trust that information. "trust" as in "oh, it says it's 2.2, so I can happily load it' and 'it's 2.0, so I cannot load it --> REFUSE' (although the mod probably works quite well). So, no matter what you do with that information, the game has to evaluate the mod by itself and see if it can apply it or not. My proposals for additional fields: licence-url last-change dependency (yes, a map/mod can be built upon another; mod-name + version) e-mail (instead of putting that into authors?) publication-date acknowledgment co-author Which fields are allowed how often? If I understand it correctly, author_s_ is a n array, but what is if there is only one author? Then the name would be inappropriate. I'd prefer to have several "author" and probably (mentioned above) "co-author" and "acknowledgement" as well. Just think of some really big mods, that took weeks of hard work. Not everybody is an author, but you'd like to thank people that really helped you during the development of that mod. Did you ever play Starcraft? Well, you could add some colours to the map-description by using ASCII control characters. Probably a less ugly method could be incorporated into the proposal? And what could be done about plagiarism? People taking mods of another person and then just rebranding it? I'd really like to have that problem addressed. So far, - Kreuvf _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
