Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Eagleon]

This or something like it might have been suggested before, but I thought it was a decent idea. Right now, mods that have to modify default raw files are a pain if you want more than one, or if you've made your own tweaks (my situation). In addition, many times mods will pick the same name for an object by coincidence, or simply use the same resources from an entirely separate third mod.

Allowing creature/item/material/whatever definitions to gracefully override definitions already loaded would improve this, if not outright eliminate it in some cases. There could be three levels for this - an init tweak that arbitrarily picks one definition to use in case of duplicates (quick and dirty), an 'override' folder inside /raws/objects/ or just /raws/ whose definition names are loaded first, which then act in place of definitions with the same name (bit less quick and dirty), and a tag for object definitions that ensures that it is loaded as the winning definition no matter what (for fine tuning).

The finer level overrides the previous - if a definition inside /raws/objects/ has a [OVERRIDE] tag, and a definition inside /raws/override/ shares its name, the /raws/objects/ definition wins. If there's a definition with [OVERRIDE] in /raws/override/, it will win over any duplicates inside the override folder.

Thoughts?

[NW_Kohaku]

My thoughts?

Something this sophisticated just to be user-friendly sounds like the sort of thing Toady would never do, honestly.

There are some third-party resources out there, however, that are designed to help you manage putting together mods.

[Eagleon]

Except it's not really too sophisticated. It's merely a dictionary instead of a basic array - as objects go into it, duplicates either replace existing definitions (if [OVERRIDE] tag is found) or are ignored. This is something I could implement in VB in a day or two, and I'm hardly a master programmer.