You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of the user modifying script/wz/config.yaml, having a separate local directory ($HOME/.local/share/cosmic?) that the server will load on top of it's own directory would be rather nice.
As an example in the local directory a user can have a config.yaml with only the changed values:
WORLDS: 2
ENABLE_PIC: false
USE_MTS: true
As well for scripts/wz folder the source likewise loads the local folder on top of it's own original folder, so the user only needs to have the scripts / wz xmls that they want to change or add.
The text was updated successfully, but these errors were encountered:
Sounds like a useful feature, I just don't know how it would work in practice.
In the case of config.yaml, I've been eyeing an alternative to YamlBeans called Typesafe config. It is based on HOCON files (JSON with extra features) and includes support for overriding properties.
Will get back to this at a later point, when issues with higher priority have been taken care of.
Instead of the user modifying script/wz/config.yaml, having a separate local directory ($HOME/.local/share/cosmic?) that the server will load on top of it's own directory would be rather nice.
As an example in the local directory a user can have a config.yaml with only the changed values:
As well for scripts/wz folder the source likewise loads the local folder on top of it's own original folder, so the user only needs to have the scripts / wz xmls that they want to change or add.
The text was updated successfully, but these errors were encountered: