Blight &/or Difficulty mob blacklist reset at startup
vicitafirea opened this issue · 2 comments
A quick search didn't give me any results about this bug, so I'm posting it, sorry if this has already been noticed. I only saw issue #236 and it isn't the same.
Versions
ScalingHealth-1.15.2-3.0.6+53
- Scaling Health: 3.0.6+53
- Silent Lib: 4.6.1+49
- Forge: 31.1.98
- Optifine Installed: NO
Expected Behavior
Everytime I put a non vanilla mob in the blight blacklist &/or difficulty blacklist on the config, it gets deletes the next time I start Minecraft. The blight blacklist tag also doesn't seem to work through a datapack, I tried even tho I don't know if it should work.
Actual Behavior
I'm trying to blacklist flies from the Project: Vibrant Journeys mod (& other passive/environmental mobs, but let's focus on the fly) and the blacklists get resetted to default during the Forge startup.
Using a datapack, putting a lot of mobs I don't want a blight of, yet I still see the blight dies alert of it.
I can put other passive vanilla mobs on the blacklists, like squids or skeleton horses, these are never deleted.
Yet the second I put something from any mod, the blacklist resets to default and it deletes the mobs that aren't there by default.
ah i think i know why. I confirm that the name is in the registry but by that time only vanilla's are populated huh... the tag was never really implemented I think. but that is actually a much better way ...
i will try to implement the system via tags. Sorry for any confusion/annoyance !