Supports modifying only a single value of a configuration entry

[hzzdev]

Currently, configuration overloading (including mods) only allows for complete replacement of a configuration entry/line.

I think it would be useful to allow adding or deleting a value for configuration entry/line that can have multiple values.

The advantage is that it doesn't affect the default value.

For example, it could force ghost enable PASS_LOCKED_DOORS and disable SEE_INVISIBLE without modifying other default configurations.

ghost.cfg

[attributes]
Properties += PASS_LOCKED_DOORS
Properties -= SEE_INVISIBLE

[Loobinex]

This is done by level script.

SET_CREATURE_PROPERTY(VAMPIRE,PASS_LOCKED_DOORS,1)
SET_CREATURE_PROPERTY(VAMPIRE,SEE_INVISIBLE,0)

[hzzdev]

I think level script is used by map designers.
And the configuration file method(.cfg) is more flexible, more powerful, and more suitable for customized needs.
The biggest advantage is that it is independent of any map or campaign.

For me, what I want to configure is

rules.cfg

[game]
PreserveClassicBugs += STUN_FRIENDLY_UNITS RESURRECT_REMOVED RESURRECT_FOREVER

Although I also noticed the SET_GAME_RULE level script, it's clearly not suitable for me.

[Loobinex]

One feature that is already on the wishlist is to be able to mod in Lua functions. That is all round powerful functionality, and it would in fact allow you to push a line of script to add or remove a single property.

[PieterVdc]

the ones that pass trough the cfg logic already do this, creatures still need to be refactored to use said logic though
specifically value_flagsfield
as it's the logic scripts also use, but nothing stops cfgs from using it

though never really tested it, but the ones that do use it I think
properties = propertyname 1
should enable that specific one

[hzzdev]

As PieterVdc said.

for the PreserveClassicBugs, the following are what I want and they are currently in effect

rules.cfg

[game]
PreserveClassicBugs = STUN_FRIENDLY_UNITS 1
PreserveClassicBugs = RESURRECT_REMOVED 1
PreserveClassicBugs = RESURRECT_FOREVER 1

Others are still waiting for optimization.

[PieterVdc]

ideally done by moving over the creature model cfgs over to the refactored format, so it can simply also use value_flagsfield

I'm personally working on other things atm, but if you'd want to pick that up great
#4631 does also touch that logic so maybe wait till that one is merged before starting

[hzzdev]

Sorry, I probably don't want to do it.
I'm not familiar with the usage of value_flagsfield, especially since I've noticed that the creature properties aren't stored in a separate variable.