rev7258| Creating new config instanted of replacing old one

[Mushroom]

Assuming we have 2 config files, the main one and the one which is included on the main. When I try to change a value from a config in the included file (using command conf), Openkore creates a new config key with the defined value in the main file instanted of replacing the values on the included files.

Example, before changing anything

fileA.txt
!include fileB.txt
apple 1
banana 2

fileB.txt
grape 3
orange 4

After changing config grape using 'conf grape 0'

fileA.txt
!include fileB.txt
apple 1
banana 2
grape 0

fileB.txt
grape 3
orange 4

It just breaks the whole concept of being organized lol

[kLabMouse]

Nope.
the Included Conf parts are used to be static.
but the main one is dynamic, and could be changed.
that is done specially, because multiple instances could use included files, but the main one is uniq for every running instance.

[EternalHarvest]

I think there should be !include syntax to choose preferred behavior.

[rocknroll]

This is very very helpfully for me
now i just create one config for all, tq sir ^^