Splitting the rulesets

[kkmic]

How about splitting that huge (and growing) ruleset file into multiple files each containing a specific set of rules?

I cant give any examples of the op of my head now... it's just an idea.

[Volutar]

Having all rulesets in one file is a bad idea.
It definately should be splitted.

[d2uriel]

There's one good thing about it - you open up that file with whichever text editor you prefer and you can find everything there. If you have multiple files... well, you have to look in each and every one of them. Besides, it's easier to mess around with only one file to load than a complete set of files.

How do you think the files should be split up?

[Volutar]

Searching through all text files could help.

Config (yaml) files should be splitted by logical parts. At least - geography / basescape / battlescape
and later, each of it should be splitted by lesser parts.

[SupSuper]

This is planned for later. The problem is it's much faster to think up ideas than implement them, so by the time I finish implementing ideas I already got much better ones in mind, it's an ever-lasting struggle. In my mind we're already at OpenXcom 2.0 and I'm on vacation in Hawaii.

To give you an idea, my future plan is something like this:
- data\
-- Xcom1DataSet\
--- Rules\
---- world.rul
---- crafts.rul
---- facilities.rul
---- ...
--- Resources\
---- surfaces.rul
---- music.rul
---- sound.rul
---- GEODATA
---- GEOGRAPH
---- ...
--- Languages\
---- english.lng
---- german.lng
---- ...
-- Xcom2DataSet\
--- Rules\
---- world.rul
---- crafts.rul
---- facilities.rul
---- ...
--- Resources\
---- surfaces.res
---- music.res
---- sound.res
---- GEODATA
---- GEOGRAPH
---- ...
--- Languages\
---- english.lng
---- german.lng
---- ...
-- HDGraphicsPack\
--- Resources\
---- surfaces.res
---- newgraphics.png
---- ...
-- NewCraftPack\
--- Rules\
---- crafts.rul
--- Resources\
---- surfaces.rul
---- newcraft1.pck
---- ...
--- Languages\
---- english.lng
-- TerrorMapSet\
--- Rules\
---- maps.rul
--- Resources\
---- surfacesets.res
---- terrorBlock1.map
---- ...
-- ...