I am a little leery of this concept, i dont want modular to be come a thing of the past, and with this it seems it is getting that way, especially since MLF is set to 1, it might mistakenly add certain "stuff" at certain times, because its reading the MLF 1 for loading only? "I'm just saying", i really dont like the game option stuff, best to leave it as a
MLF load by individual personal option(s), that way he/she can load it or unload it during a game and not have it set to the game options in the beginning.
When a person goes from a windows form back to the game, it loads all modules, python etc, all over again???
Screenie is a re-load when coming from a windows back to game mode.
1)Modules and the modular approach will never be a thing of the past.
2)A player does not have to play with ls612's trait set. It's a game option. Under the option, the core trait set is replaced by his. It's not default either... a player must make the choice to play with his, but the choice is a bit easier than fiddling around with settings in files as it can be selected among all the other game options at game setup. (not during the game - those are modderoptions or playeroptions as opposed to GameOptions - it's possible to change a game option during a game but its a major pain in the butt.)
3)MLF 1 just means, yes include this module. Given the method employed, LS612 doesn't have to do these in a module at all but has done so for the benefit of keeping things more organized.
"I'm just saying", i really dont like the game option stuff, best to leave it as a MLF load by individual personal option(s), that way he/she can load it or unload it during a game and not have it set to the game options in the beginning.
A very frustrating outlook considering how badly I loath MLF manipulation being used as game options because its just too big a pain to go in and manipulate them, before, during, after, getting overriden by SVN updates, accidentally overriding the correct defaults on SVN updates...
I have not played with so much of the potential of this mod because I won't manipulate MLF files unless absolutely necessary. How many players out there would feel even more strongly than a modder, who's not making this choice out of a fear of incompetence alone?
Simply put, for 99% of the downloading public, if you've include an option that must be activated by manipulating an MLF file, you haven't actually included the option at all, only files that take up wasted download space.
And if you make that option default, and a player doesn't like it (let's consider the Alternative Timelines for a moment and all the comments we've seen on those) then they get really frustrated that they have to learn how to manipulate the MLF properly to turn it off. I wonder how many players we've lost this way, who just say, "I'm not doing that and I'm not playing with Bear Riders in my game so... next mod please."
That and I'm not seeing any real reason for the uncomfort here??? If it's simply because its a new method, then consider how a non-modder feels about manipulating an MLF!
When a person goes from a windows form back to the game, it loads all modules, python etc, all over again???
Screenie is a re-load when coming from a windows back to game mode.
Purely affects python alone. Has nothing to do with this. Module XMLs do not reload after the initial mod load sequence.