QOL Features #304
Machinational
started this conversation in
Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sorry in advance if this is a little long.
Here is a lit of additions / changes that I think would greatly improve the feel of the desktop app.
Library List View
Brief: Add an additional view in the form of a list to the users library screen.
Specifics: The grid view cuts off longer project names. Implementing a list view option would also allow for more data to be displayed. Like longer names, last played, Minecraft version, and or pack version.
Content Hierarchal View
Brief: Allow for a visual representation of dependencies and other relation ships in the project content view.
Specifics: Lots of mods have library mods or require other mods to be installed. It would be incredibly helpful from a content management and understanding perspective to have a visual representation of this. Maybe indent dependents under the main mod creating a easy way to distinguish what library mods go to what mod.
Content Sorting and Information
Brief: Display more information regarding project content and allow for sorting and filtering.
Specifics: Since the content view is in a list there is a lot of unused space. While filling this space would be too much the option to add other information would be incredibly helpful. Information like:
Date Added: Extremely helpful in figuring out which of the 10 things you just added broke things.
File Name: Helpful for when the mod name doesn't match the file name and the crash log only gives you the file name.
Last Updated: Helpful for figure out what thing updated and broke things.
Mod Type: (Main | Dependent | library)
Mod Author: Split the mod name and author name, so we can filter by authors.
Adding the ability to filter by these added values would be amazing and incredibly useful.
Project Versioning
Brief: Implement a system for pack versioning.
Specifics: A system for pack versioning would allow for easier development and distribution. This might be done by leveraging GitHub and just having the user sign-in. This is probably my most complex suggestion. I know you can kind of do versioning using the "Export" feature, but a built-in system would be nice.
Navigation Memory
Brief: Maintain current filters when using the forward and back page feature.
Specifics: When navigating around the app being able to use the forward and back page feature is great, but it often clears any active filters or page settings. For example, if you are on page three in a project and you click on some content to see more info about it, and then go back it will put you back on page one.
Are you looking for new content on page four with a few filters?It looks like this was fixed.If you have taken the time to read all of this, I appreciate you.
Beta Was this translation helpful? Give feedback.
All reactions