You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFTER he creates the initial EnderChest and onboard all his instances using a combination of enderchest craft and enderchest gather minecraft WHEN he runs the command
enderchest craft shulker_boxes
(plural)
THEN, based on the registered instances, Steve should have a collection of shulker boxes (interactively?) created that will help him efficiently organize his Minecraft assets
SO that he doesn't have to just figure an efficient way of organizing the assets himself
Notes
I'm narrowing down on what that correct layout should be. I'm thinking that what makes the most sense is:
Start with one box per instance
Create a box for every distinct modloader x version of Minecraft that has two more instances, then move all mods common to those instances into the modloader-version folder
Create a common box for assets that are widely cross-compatible between different modloaders and versions (namely: resourcepacks and shaderpacks) that also contains the "standard" link folders (because those are all things that should be shared among all instances)
Create one final "local only" shulker that contains shader settings (incl. iris.properties)
Alex (more advanced user) may want to craft addtional shulker boxes to organize things like modpacks and testing instances, but this should be enough for even her to get started.
Not sure what should happen if there are already shulker boxes. Presumably he should be prompted to break them?
The text was updated successfully, but these errors were encountered:
GIVEN Steve is setting up a new EnderChest
AFTER he creates the initial EnderChest and onboard all his instances using a combination of
enderchest craft
andenderchest gather minecraft
WHEN he runs the command
(plural)
THEN, based on the registered instances, Steve should have a collection of shulker boxes (interactively?) created that will help him efficiently organize his Minecraft assets
SO that he doesn't have to just figure an efficient way of organizing the assets himself
Notes
I'm narrowing down on what that correct layout should be. I'm thinking that what makes the most sense is:
iris.properties
)Alex (more advanced user) may want to craft addtional shulker boxes to organize things like modpacks and testing instances, but this should be enough for even her to get started.
Not sure what should happen if there are already shulker boxes. Presumably he should be prompted to break them?
The text was updated successfully, but these errors were encountered: