Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New pack version dialog #9

Open
10 of 13 tasks
forresthopkinsa opened this issue Jul 10, 2018 · 4 comments
Open
10 of 13 tasks

New pack version dialog #9

forresthopkinsa opened this issue Jul 10, 2018 · 4 comments
Assignees
Labels
core functionality Primary development goals front-end Requires changes to the frontend module
Milestone

Comments

@forresthopkinsa
Copy link
Owner

forresthopkinsa commented Jul 10, 2018

Should be a form with the following inputs:

  • Version name (e.g. 1.2.3 or F2345): text input
  • Game version: dropdown list populated by Minecraft versions
  • Forge versions: searchable dropdown list filtered by selected game version, defaulting to latest build for that game version
  • Java version: dropdown list populated by major Java versions; optional, set to 0 to unset
  • Required memory: slider input populated by RAM allocations in 512MB increments; optional, set to 0 to unset
  • Recommended: checkbox that will identify this as the new "recommended" version for this pack
  • Mods: searchable dropdown list populated by mods and their versions
  • Save: button that will load until the version is either saved successfully or an error is thrown
  • There should be a table of included mods beneath the Mods dropdown, showing the mods and their versions
  • Each row in the table should have a remove button that will delete it from the table
  • Should show warning when including mods with unfulfilled dependencies
  • Warning should reflect which mods should be included in order to fulfill dependencies
  • Warning should be recalculated every time any mods are added/removed from the list
@forresthopkinsa forresthopkinsa added core functionality Primary development goals front-end Requires changes to the frontend module labels Jul 10, 2018
@forresthopkinsa forresthopkinsa added this to the 18.08.00 milestone Jul 10, 2018
@forresthopkinsa forresthopkinsa self-assigned this Jul 10, 2018
This was referenced Jul 10, 2018
@forresthopkinsa
Copy link
Owner Author

Didn't previously consider the fact that the Forge build sequence does not not follow game version sequence; Forge builds jump around between game versions. For that reason, I'm changing the way we'll select Forge/game versions. See the edit made just now.

@forresthopkinsa
Copy link
Owner Author

The game version/forge version ranges apply to mods versions, not pack versions. Need to change that pretty significantly. About to make an edit to reflect that.

@forresthopkinsa
Copy link
Owner Author

Future version: perform validation on each mod version that gets added to a pack, to ensure that it's compatible with the pack version's Forge.

@forresthopkinsa
Copy link
Owner Author

Future version: make the Game Version field reflect the Forge Version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core functionality Primary development goals front-end Requires changes to the frontend module
Projects
None yet
Development

No branches or pull requests

1 participant