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
{{ message }}
This repository has been archived by the owner on Nov 9, 2018. It is now read-only.
selecting features when downloading / updating a pack
a simple CLI input or selecting checkboxes / radiobuttons with a cursor is sufficient
this will be also useful fo #4
installing features, especially mods and removing them
in short.. keeping track of files and being able to reverse a transaction before applying a different one
identifying incompatible features
and disabling incompatible features or preventing it from being enabled at the same time
can be done by matching the paths of the resource entries
live sync of files back into the feature folders
useful for development, but could generally be always useful
maybe just use symlinks on unix and junction points on windows
although junctions only work for folders.. so that might be a pain
and i am not sure how minecraft reacts to symlinks or junctions
changes
mods in packbuild.json will have to change to files or something similar
packbuild.json needs to include metadata for the features
most important keys and names
as well group info and incompatibilities / exclude data
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
requires: #31
features will live in separate folders
challenges
selecting features when downloading / updating a pack
a simple CLI input or selecting checkboxes / radiobuttons with a cursor is sufficient
this will be also useful fo #4
installing features, especially mods and removing them
in short.. keeping track of files and being able to reverse a transaction before applying a different one
identifying incompatible features
and disabling incompatible features or preventing it from being enabled at the same time
can be done by matching the paths of the resource entries
live sync of files back into the feature folders
useful for development, but could generally be always useful
maybe just use symlinks on unix and junction points on windows
although junctions only work for folders.. so that might be a pain
and i am not sure how minecraft reacts to symlinks or junctions
changes
mods
inpackbuild.json
will have to change tofiles
or something similarpackbuild.json
needs to include metadata for the featuresmost important keys and names
as well group info and incompatibilities / exclude data
The text was updated successfully, but these errors were encountered: