Handle maps properties in game's luarules/configs

[p2004a]

I don't have all the requirements yet, but also the properties used in https://github.com/beyond-all-reason/Beyond-All-Reason/tree/master/luarules/configs (crickets, lavaConfig) should be part of this project somehow.

[icexuick]

This is interesting, I have a question however:

A possible problem I can think of is, that to build/test/tweak these, you want to be able to change these values in-game. Currently you change the numbers, restart your map, and you can see your changes. It's not as ideal as live changes, but it should not become even more complicated than this.

Is this still doable if this data does not live there? Do you need to change numbers in Git/maps-meta-data, then somehow push that first, then restart/reboot the game to actually see/test it in-game?

[p2004a]

It will be done in a way to not be more complicated. It will not require modifying maps-metadata repository, changes will be testable locally. That's a requirement.

[icexuick]

@p2004a Any thoughts on how to achieve what you want?
Can you perhaps simply sync data from git / or is that just the same thing that you don't want?

[p2004a]

Any thoughts on how to achieve what you want?

Similar to how mapDetails.lua is synced to chobby repo. This repo generates Lua file and commits to the target repo.

[p2004a]

Alternative is it's being programmed at runtime, by modoption: just like it's done for start pos suggestions.

This is the second way. Need to investigate requirements more to make decision which one is more appropriate.

[icexuick]

Hows the investigation going?

[p2004a]

It's not and I do not have any plans for working on it.