Spring RTS Engine

spads remembers map options globally, instead of per-map, this results to very inconvenient behaviour, take this case for example ( which actually happened and caused quite few troubles to get pinpointed ):

map A has option with name "waterdamage", it gets set to default when loaded/launched
map B has option with the same name, but it's not listed in the option list ( folsom )
now option from map A will be remembered, and players will be puzzled why map B in this host has map damage, and there's no option to turn it off

!waterdamage 0 ?

But yeah, it should save configurations for each map, I agree.

BrainDamage wrote:spads remembers map options globally, instead of per-map

It's not supposed to do so
On which host did you encounter this bug? Which "map A" can I use to reproduce it?
Thx for reporting.

Jazcash wrote:!waterdamage 0 ?

But yeah, it should save configurations for each map, I agree.

that'd be !bset waterdamage 0, but it doesn't work when the map doesn't list it as option, you have to switch to map A which has the option, set it, then switch back to map B

bibim wrote:

BrainDamage wrote:spads remembers map options globally, instead of per-map

It's not supposed to do so
On which host did you encounter this bug? Which "map A" can I use to reproduce it?
Thx for reporting.

TERA hosts were affected
map A: dark water wasteland
map B: folsom dam deluxe v4

true
had many problems - startscript shows waterdamage = 2
and in list options there are no waterdamage options to overwrite or set

so please fix :)

can you switch to unstable release and check if bug is corrected?

it can be easy fixed. Just make a default !bset waterdamage 0 as a default setting, so maps with water and without map options will not have this problem.

Same with maphardness map inverted etc all map option bsettings that affect specially water, terrain also elevation, i dunno if wind or metal its also affected, never tryed it out

bibim wrote:can you switch to unstable release and check if bug is corrected?

how i switch?

actually I have included it in "testing" now, so you don't have to switch to test it