Impaler[WrG said:
Personly I dont see why .ini parsing is so popular, before the SDK when all we had was Python it was nessary, but not that your going to be doing SDK work to make this mod in the first place theirs no need to involve the Python layer, everything could be done with Global Defines which go strait into the Code without mucking around in Python and their loaded from XML which people are already far more familiar with.
I like the ini thing because it allows option to be put in their own file. Especially if you have several mods all with a half dozen or so options, this will fill up a globaldefines file pretty quick, and anyone who has just spent the better part of an hour just reading over globaldefines options knows that that file doesn't need to be any longer.
As for python verse sdk, I'm of the opinion that any and all code that can be done in python should be. For one, when it is written in python, anybody with a text editor can open it up and do what they want with it. For second, python is way more intercompatable then the c++ changes as it requires no compileing or special editors. Just a litle cutting and pasting, amybe a new if/then or two, and boom, save and play.
The question is your goal, do you want to make it more streamlined for users of the mod or more compatable for other modders to incorp into their own creations. If the former sdk is the way to go, but if the latter then python should be used if possible and sdk resorted it when all else fails.
EDIT: Sorry for the off topic post, but I have to defend my beloved Python.
And just to hit on the topic, this mod looks like another winner, if you are in need of testers for it, just pm me TheLopez.
