Things like allowing LUA GUIs and fancy keysets and crap like that - it's all a massive waste of time. Everything like that must be:
Spring has default
Mod has override
User has final control
Not:
Spring has default
L33t hacker can make useful
Mod gets pissed on
Why bother investing 8 hours into making a perfect GUI if it requires action on the part of the lazyass end-user that never reads readmes in order for it to be activated?
Why should every mod have the same GUI? If I install a GUI that I make and I love, then next comes SWTA with a GUI that's perfect for SWTA, and another one for E&E and they all override each other and I kill everyone.
Anything that can't be mod-defined is a waste of your time
Moderator: Moderators
The user should always have the final say. The current
contenders for "mod guis" are certainly not the settings
that I want to use.
That being said, the first release of my LuaUI files should
make you a little happier. If the mod has a "mod_ui.lua"
file, then a menu is brought up at the beginning of the game.
Use Mod GUI? YES | NO | ALWAYS | NEVER
P.S. The mod_ui.lua can have code that loads custom
ctrlpanel.txt and cmdcolors.txt files. It can also ruin^H^H^H^H
modify the keybindings, etc...
contenders for "mod guis" are certainly not the settings
that I want to use.
That being said, the first release of my LuaUI files should
make you a little happier. If the mod has a "mod_ui.lua"
file, then a menu is brought up at the beginning of the game.
Use Mod GUI? YES | NO | ALWAYS | NEVER
P.S. The mod_ui.lua can have code that loads custom
ctrlpanel.txt and cmdcolors.txt files. It can also ruin^H^H^H^H
modify the keybindings, etc...
Oops, I guess I didn't address your ordering correctly,
you did have user as the final override.
The choice to have the spring config files installated
by default (thus blocking mod config files), was mine.
I don't think noobs should be subjected to changing
GUIs without knowing how to revert them to the defaults.
The solution that my LuaUI provides is much cleaner,
and should make even the modsters happy.
Experienced users can rename or remove the default
files if they wish to use the settings provided by the
mods. It's a rather poor system, and that's why it is
being improved.
P.S. Don't forget that L33t hackers can distribute their configs.
There may even be non-L33t hackers using some LUA files
right now.
you did have user as the final override.
The choice to have the spring config files installated
by default (thus blocking mod config files), was mine.
I don't think noobs should be subjected to changing
GUIs without knowing how to revert them to the defaults.
The solution that my LuaUI provides is much cleaner,
and should make even the modsters happy.
Experienced users can rename or remove the default
files if they wish to use the settings provided by the
mods. It's a rather poor system, and that's why it is
being improved.
P.S. Don't forget that L33t hackers can distribute their configs.
There may even be non-L33t hackers using some LUA files
right now.
LordMatt:
You're also agreeing with Caydr. I made the same mistake in
my first post. His problem is with there being config files installed
by default (that block mod files), and not that the user gets the final
override.
The current setup is basically what Caydr asks for, with the caveat
that the initial user choice defaults to exercising the right to override
You're also agreeing with Caydr. I made the same mistake in
my first post. His problem is with there being config files installed
by default (that block mod files), and not that the user gets the final
override.
The current setup is basically what Caydr asks for, with the caveat
that the initial user choice defaults to exercising the right to override