EnderChest interferes with auto-updating systems

[OpenBagTwo]

Summary

Launchers that have built-in functionality to manage mods and fetch updates will not play nicely with EnderChest

Environment and Version

This is not specific to any OS or (current) version of EnderChest and is instead a flaw in the very premise of this design.

Steps to Reproduce

PrismLauncher and other instance managers have the built-in ability to download mods and check for updates. On a system using EnderChest, that will remove any symlinks to outdated mods and download new mods into the instance folders.

The next time a user runs enderchest place the deleted symlinks will be restored, possibly causing launcher conflicts, but 💯 creating a mess.

Workaround

Don't use auto-updaters!

Severity

Major Annoyance

Desired Outcome

Pick a new approach!

Urgency

While not needed for MVP, this will seriously hinder adoption.

[OpenBagTwo]

My reflections dogfooding this for a bit is that it hasn't been horrible to go through and periodically move all non-symlinks into the appropriate chest.

I do think a log that allows EC to notice an EnderChest-placed link was deleted since the last place and offers to propagate that change upstream would be achievable.