Mod setings
Posted: 06 Dec 2006, 13:09
Basically, have mods define settings for game (comm ends, starting res, etc). Most notably the Comm ends is important. I wouldn't want people playing my version of TLL without comm ends, EE would not want (probably) it beeing played with comm ends, etc.
Something like this:
I don't know well how to add some things like unit restrictions. I can think better about it.
This would simple down settings, add standardization (instead of some playing CommEnds with 10K res, CommContinues with 1K res and limited D-Gun range, etc) while allowing diferences. It would simple down the life for the lobby, since it would have, instead, a list of non-default settings available with possible values (later, new options could be added to mods settings without one single change in the lobby). Would allow for mods to define standards or only ways of playing.
I know that, for example, word can be spread that Spring:1944 should be played with X resources instead of regular Y, but it's not the same thing.
Something like this:
Code: Select all
[CommEnds]
{
Value1=1;
Description1=Player looses when commander dies!;
Overridable=1;
[possibility1]
{
Value1=0;
}
[possibility2]
{
Value1=1;
}
}
[StartingResources]
{
Value1=1000;
Description1=Metal!;
Value2=1000;
Description1=Energy!;
Overridable=1;
[possibility1]
{
Value1=100;
Value2=100;
}
[possibility2]
{
Value1=5000;
Value2=5000;
}
}This would simple down settings, add standardization (instead of some playing CommEnds with 10K res, CommContinues with 1K res and limited D-Gun range, etc) while allowing diferences. It would simple down the life for the lobby, since it would have, instead, a list of non-default settings available with possible values (later, new options could be added to mods settings without one single change in the lobby). Would allow for mods to define standards or only ways of playing.
I know that, for example, word can be spread that Spring:1944 should be played with X resources instead of regular Y, but it's not the same thing.