An optimization modpack is recommending these on because they haven't had issues with these setting but I am weary of doing so. I understand that this is a quick fix to a problem you should be finding the root cause of but all I see is the warning "BE WARNED THIS COULD SCREW UP EVERYTHING USE SPARINGLY WE ARE NOT RESPONSIBLE FOR DAMAGES" but has anyone tested this out over the course of a playthrough or in a test environment? Will Forge start deleting far more than it should? What exactly are the consequences in more detail? If anyone has more insight I would greatly appreciate it.

Well, as the configurations imply regardless of version, it simply removes an entity or block entity when it crashes while ticking. The only time this really occurs is when unexpected behavior occurs or the mod itself is programmed badly, which I've rarely seen in small mods. So, unless you're doing something ridiculous that is outside the bounds of survival gameplay, I don't expect you ever to run into this issue. Additionally, if the issue occurs, you'll be able to see the action within the output log, so you'll know that it happened.

 

As I didn't understand the question originally after posing it to the discord, one of the members mentioned that the 'optimization modpack' might be using this to hide errors caused by the performance mods. Additionally, you shouldn't normally expect errors to occur, so it makes no sense to leave the option on until you need to recover the world after the crash already happens.

I see, thank you for your time.