This release sees a ground-up rewrite and with it [a pretty nice set of docs](https://openbagtwo.github.io/EnderChest/).
While the workflow of the "v0.0" releases performed their linking based on a config-less EnderChest, the " all the things" strategy eventually resulted in a giant, unmanageable mess. As described in 25 and broken down in [Milestone 2](https://github.com/OpenBagTwo/EnderChest/milestone/2), the new EnderChest structure is now focused on organizing assets into purpose-oriented "shulker boxes." You can read more about the philosophy behind EnderChest [here](https://openbagtwo.github.io/EnderChest/dev/about/).
This release sees feature parity with [v0.0.3](https://github.com/OpenBagTwo/EnderChest/releases/tag/v0.0.3.1)--explicitly, while [servers _can_ be linked and synced](https://github.com/OpenBagTwo/EnderChest/issues/66), it will require manual work that is not currently documented. Aside from that, Enderchest v0.1.0 implements linking and Minecraft instance auto-discovery for both official and MultiMC-derived launchers. This version also allows you to sync your EnderChests across multiple machines via `rsync` (Windows is theoretically supported through Cygwin, but [this is undocumented and untested](https://github.com/OpenBagTwo/EnderChest/issues/67)). You can also sync your EnderChest to another folder on the same file system (like a Dropbox folder) using `file://` URIs. Future releases will see support for other protocols such as `sftp` (pure-python with Paramiko), `smb` and possibly `git`.
A Note On Linking
Starting with Minecraft 1.20, Mojang by default [no longer allows worlds to load if they are or if they contain symbolic links](https://help.minecraft.net/hc/en-us/articles/16165590199181). While it is true that an improper symlink could cause Minecraft to write data to a place it shouldn't, nothing in EnderChest will ever generate a symlink whose target is outside of your EnderChest folder unless you place a symbolic link in your EnderChest pointing to somewhere else (which you may want to do so that your screenshots, for example, point to your "My Pictures" folder).
That said, when you register a 1.20+ instance with EnderChest, EnderChest will _ask you_ if you'd like the EnderChest's directory added to your `allowed_symlinks.txt` file. **EnderChest will never modify this or any other file without telling you it's doing so.**
If you still have concerns about symlinks or questions about how they work, read through [this guide](https://www.makeuseof.com/tag/what-is-a-symbolic-link-what-are-its-uses-makeuseof-explains/) or [watch this explainer](https://www.youtube.com/watch?v=mA08E59-zo8), and if you still have questions, feel free to [open an issue](https://github.com/OpenBagTwo/EnderChest/issues/new?assignees=OpenBagTwo&labels=question&title=symlink%20question).
**Full Changelog**: https://github.com/OpenBagTwo/EnderChest/compare/v0.0.4...v0.1.0