Period. Fix Plox.
Perhaps even add a toggle via modoptions.
Mod LUA should ALWAYS supercede user lua
Moderator: Moderators
-
Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Mod LUA should ALWAYS supercede user lua
Hi,
sorry- i dont think so [in the term of "ALWAYS"].....
Often it come a update from an LUA long for an new mod update and with
"always" this new version go to trash for this mod.
So i like to see a user control over the lua that ar active and for
EVERY mod a single config file for his LUA config.
IMHO is the actual config and AI-config handling one more stupid thing in the
spring world.[with the stupid "who need save/load" one top]
Every time a new minor mod change come i have to rename my AAI config/learning
files and so one with other AIs and the same goes to the mod config files, even is
nothing changed by the configs .. horrible and with realy zero sense ..
Put every mod file in a seperate directory [CA-xxxx is going in the CA\ directory
and the lua config and AIs config and mod config too]
Is now a mod update is come you save the new CA-xxxx in the directory and delete the
old.He load the previouse config files (AIs/Mod/LUA) and update is new options
available.
IF the user realy need the old mod version he make a copy of the complete CA\ dir
and name it CA-old1\ or so ....
This will be MUCH more user friendle - but i know - this is not the target here .....
Regards
R-TEAM
sorry- i dont think so [in the term of "ALWAYS"].....
Often it come a update from an LUA long for an new mod update and with
"always" this new version go to trash for this mod.
So i like to see a user control over the lua that ar active and for
EVERY mod a single config file for his LUA config.
IMHO is the actual config and AI-config handling one more stupid thing in the
spring world.[with the stupid "who need save/load" one top]
Every time a new minor mod change come i have to rename my AAI config/learning
files and so one with other AIs and the same goes to the mod config files, even is
nothing changed by the configs .. horrible and with realy zero sense ..
Put every mod file in a seperate directory [CA-xxxx is going in the CA\ directory
and the lua config and AIs config and mod config too]
Is now a mod update is come you save the new CA-xxxx in the directory and delete the
old.He load the previouse config files (AIs/Mod/LUA) and update is new options
available.
IF the user realy need the old mod version he make a copy of the complete CA\ dir
and name it CA-old1\ or so ....
This will be MUCH more user friendle - but i know - this is not the target here .....
Regards
R-TEAM
Re: Mod LUA should ALWAYS supercede user lua
Forb, wtf. Put slightly changed widget handler in mod. Done. And why would you make it a mod option which copy of a widget file loads?
Re: Mod LUA should ALWAYS supercede user lua
Darn you guys! type 'Lua' correctly! 
Re: Mod LUA should ALWAYS supercede user lua
LOOO UH!
What now midknight?
forb I don't agree with the request sorry man but I have to give this a minus 1
What now midknight?
forb I don't agree with the request sorry man but I have to give this a minus 1
Re: Mod LUA should ALWAYS supercede user lua
We need a version field, darnit!
Re: Mod LUA should ALWAYS supercede user lua
in lua or the packages? I am pretty sure the file modinfo has that covered.
Re: Mod LUA should ALWAYS supercede user lua
Widgets; why would I be talking about mod versions?
Re: Mod LUA should ALWAYS supercede user lua
I was pretty coffoosed by that yeah.
Re: Mod LUA should ALWAYS supercede user lua
lurker wrote:We need a version field, darnit!
Both have a version field anyway.smoth wrote:in lua or the packages?
Re: Mod LUA should ALWAYS supercede user lua
I know, but I didn't feel like correcting my post to be more explicit about what I meant. fine
Widgets need to have a version field that does something.
Widgets need to have a version field that does something.