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
Certain options, which apply to both dungeons and to treasue hunts, currently live in the [dungeon] section of the config file. These should probably be moved to a [global] section to more clearly indicate that they affect treasurehunts as well. Examples would be max_dist and min_dist, Spawn*, structures, *_biomes, silverfish
It would probably be necessary to retain backwards compatibility with older cfg files, meaning that if global.X is not set, then use dungeon.X instead, else use the default.
This is fairly easy to code up -- I've already done much of the work in my branch -- but I'd like to hear if this is in line with your design philosophy before submitting a pull req. This would also mean a certain amount of documentation changes.
The text was updated successfully, but these errors were encountered:
It would be nice if the [dungeon] section could become entirely optional - like the treasure hunts section.
Rather than worrying about backwards compatibility, it might be enough just to throw a helpful error message when the [global] section is missing. It's a fairly easy fix to the file.
Certain options, which apply to both dungeons and to treasue hunts, currently live in the [dungeon] section of the config file. These should probably be moved to a [global] section to more clearly indicate that they affect treasurehunts as well. Examples would be max_dist and min_dist, Spawn*, structures, *_biomes, silverfish
It would probably be necessary to retain backwards compatibility with older cfg files, meaning that if global.X is not set, then use dungeon.X instead, else use the default.
This is fairly easy to code up -- I've already done much of the work in my branch -- but I'd like to hear if this is in line with your design philosophy before submitting a pull req. This would also mean a certain amount of documentation changes.
The text was updated successfully, but these errors were encountered: