Moving LUPS/Chilli/FeaturePlacer to Mod-Inspecific Libraries
Posted: 16 Dec 2010, 06:07
What do you guys think of developing these projects (and others like them) as dependency files that games can depend on?
Some advantages would be that
- multi-game players would only need one copy of a file (unless a game specifically uses an old version),
- moddevs would have an easier time implementing these technologies,
- "custom made" stuff stays separate from the base Lua, and
- the files won't be entangled and scattered throughout a mod.
Some disadvantages are that
- library updates might break things for some games,
- library devs would have to be more conservative with breaking backwards-compatibility,
- the initial effort would have to be put in to separate the mod-specific code,
- files would be scattered between general stuff in the lib and mod-specific modifiers in the mod, and
- rapid would have to be edited if we want seamless library updates.
So, do the advantages outweigh the risks? How do people feel about this idea? Can it even be done?
EDIT: Now in easier-to-read bulleted list format!
Some advantages would be that
- multi-game players would only need one copy of a file (unless a game specifically uses an old version),
- moddevs would have an easier time implementing these technologies,
- "custom made" stuff stays separate from the base Lua, and
- the files won't be entangled and scattered throughout a mod.
Some disadvantages are that
- library updates might break things for some games,
- library devs would have to be more conservative with breaking backwards-compatibility,
- the initial effort would have to be put in to separate the mod-specific code,
- files would be scattered between general stuff in the lib and mod-specific modifiers in the mod, and
- rapid would have to be edited if we want seamless library updates.
So, do the advantages outweigh the risks? How do people feel about this idea? Can it even be done?
EDIT: Now in easier-to-read bulleted list format!