custom sieve registry not working about exnihiloomnia HOT 3 CLOSED

Note that moving defaults to a json file is always problematic as changes in later versions of the mod won't be applied to users who ran it before, unless you do some spooky versioning magic.

The best way to solve this issue is probably allowing 1) disabling of individual default entries and then 2) making new entries append to existing entries rather than overriding them.

from exnihiloomnia.

i'd expect it to be more like a config file, in that if you need changes from an update then the user would backup/remove the file for it to be recreated at launch. or use a hash check to determine if there were no changes and then just replace the file at launch maybe?

more important right now, is that the registry doesn't seem to function as is. if the example given doesn't work, i'm not really sure how to add my own entries.

from exnihiloomnia.

Can confirm. Adding blocks to the sieve registry merely gives back two of the blocks you put in.

from exnihiloomnia.