Enderchest

Latest version: v0.1.6

Safety actively analyzes 706267 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 4

0.1.2

It looks like 1.20.1 now goes further and checks not just the direct target of a symlink but the _final target_... all while still not fully resolving relative paths :man_facepalming:.

With this hotfix release, absolute symlinks will now be placed to the _fully resolved target_ of a symlink found inside a shulker box rather than targeting the link inside the box.

What's Changed
* Fully resolve nested symlinks in `absolute` mode in https://github.com/OpenBagTwo/EnderChest/pull/82


**Full Changelog**: https://github.com/OpenBagTwo/EnderChest/compare/v0.1.1...v0.1.2

0.1.1

There's a concept in software development called "dogfooding," where the best way to test your software is to use it yourself ("eat your own dogfood"). Through two weeks of eating my own dogfood, I've learned what worked and what didn't in the first release, and I've applied those learnings to this patch version. Among the highlights are:
- much more useful sync logs
- making it easier to exclude [garbage files](https://buildthis.com/ds_store-files-and-why-you-should-know-about-them/) from linking and syncing
- a badge on the README to let folks know that EnderChest works on the Raspberry Pi :heart:

What's Changed
* Fix relative pathing issues in https://github.com/OpenBagTwo/EnderChest/pull/71
* Added Raspberry Pi badge to the README and docs pages. by MatterAndy in https://github.com/OpenBagTwo/EnderChest/pull/72
* Better sync outputs in https://github.com/OpenBagTwo/EnderChest/pull/73
* Add detailed code quality reports to the docs in https://github.com/OpenBagTwo/EnderChest/pull/74
* Show shulker boxes that get linked to by an instance in https://github.com/OpenBagTwo/EnderChest/pull/75
* Implement cleaning up of stale EnderChest links in https://github.com/OpenBagTwo/EnderChest/pull/76
* Linting in https://github.com/OpenBagTwo/EnderChest/pull/77
* Implement dynamic link/sync exclude lists in https://github.com/OpenBagTwo/EnderChest/pull/78
* Lots of documentation updates, including [a detailed overview of the release process](https://openbagtwo.github.io/EnderChest/dev/contrib/#development-workflow)

New Contributors
* MatterAndy made their first contribution in https://github.com/OpenBagTwo/EnderChest/pull/72

**Full Changelog**: https://github.com/OpenBagTwo/EnderChest/compare/v0.1.0...v0.1.1

0.1.1rc2

Since the "prerelease" got published as "rc1" I guess that makes this "rc2."

The purpose of cutting this release is entirely to make sure that [this commit](https://github.com/OpenBagTwo/EnderChest/pull/79/commits/5067b2a3505f53e2fb8205c43af0a2b679544dd8) is behaving as it should (read: no docs when I hit that "publish" button).

**Full Changelog**: https://github.com/OpenBagTwo/EnderChest/compare/v0.1.1-pre1...v0.1.1-rc2

0.1.1pre1

What's Changed
* Fix relative pathing issues in https://github.com/OpenBagTwo/EnderChest/pull/71
* Added Raspberry Pi badge to the README and docs pages. by MatterAndy in https://github.com/OpenBagTwo/EnderChest/pull/72
* Better sync outputs in https://github.com/OpenBagTwo/EnderChest/pull/73
* Add detailed code quality reports to the docs in https://github.com/OpenBagTwo/EnderChest/pull/74
* Show shulker boxes that get linked to by an instance in https://github.com/OpenBagTwo/EnderChest/pull/75
* Implement cleaning up of stale EnderChest links in https://github.com/OpenBagTwo/EnderChest/pull/76
* Linting in https://github.com/OpenBagTwo/EnderChest/pull/77
* Implement dynamic link/sync exclude lists in https://github.com/OpenBagTwo/EnderChest/pull/78

Still To Do
* 68
* Writing up the descriptive release notes
* Coming up with a clever name 🤣

New Contributors
* MatterAndy made their first contribution in https://github.com/OpenBagTwo/EnderChest/pull/72

**Full Changelog**: https://github.com/OpenBagTwo/EnderChest/compare/v0.1.0...v0.1.1-pre1

0.1.0

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

0.1.0rc6

This is the last version of EnderChest that used relative links by default.

**[Click here](https://github.com/OpenBagTwo/EnderChest/compare/v0.1.0-rc1...v0.1.0-rc6)** to see the full list of changes from the first release candidate until this one

**[Click here](https://github.com/OpenBagTwo/EnderChest/compare/v0.1.0-rc6...v0.1.0)** to see the full list of changes from this release candidate to the final release

Page 3 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.