This hopefully streamlines the installation process, because it's one less step that the user could forget.
I imagine that there's at least a small percentage of people who just download Terrestria, forget fabric API, don't understand the resulting unintuitive crash ("but I already installed fabric, why is it asking me to install it again?"), then ditch Terrestria because they can't get it working.
This PR also drops the dependency on LibStructure, because it effectively got ported into Fabric API in the form of fabric-structure-api-v1. This means that we have one less maven server to depend on, and don't need to worry about whether the library will be updated for future Minecraft versions.
This hopefully streamlines the installation process, because it's one less step that the user could forget.
I imagine that there's at least a small percentage of people who just download Terrestria, forget fabric API, don't understand the resulting unintuitive crash ("but I already installed fabric, why is it asking me to install it again?"), then ditch Terrestria because they can't get it working.
From what I've seen, this appears to be the preferred approach (compared to just making the user download fabric api) based on things like https://github.com/FabricMC/fabric-loom/pull/183 and https://github.com/FabricMC/fabric-installer/pull/38#pullrequestreview-417087209 (specifically, the "Those that do should not need to worry about installing it" part).
This PR also drops the dependency on LibStructure, because it effectively got ported into Fabric API in the form of fabric-structure-api-v1. This means that we have one less maven server to depend on, and don't need to worry about whether the library will be updated for future Minecraft versions.