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
What problem does the feature request solve? The semi-tedious task of going to every individual mod to click "Website" to then figure out what the change/update was/is - or having to search up the mod manually on Thunderstore's page.
Example mock-up (optional)
to the left of the mod could be the update symbol that can be clicked:
The name of the mod could be clickable - which leads to the mod page itself ( not immediately to the changelog, as some modders don't use the changelog function on the site); Or, the empty space to the right of the mod names could have a button similar to the website button (or exactly):
Or a combination of the 3... maybe clicking the name leads to the mod page - and the button to the right, instead of saying "Website", says "Changelog". That way, people can choose which one to go to immediately. Maybe have some sort of detection method to check if the modder uses the changelog page or not? For example, Gratar in the image has no changelog page:
So maybe if changelog can't be clicked (or when you force it to check the changelog page it detects the text "This package has no changelog available." on the page): Then the changelog button doesn't appear to the right of the mod, but the mod name can still be clickable?
If Idea 2 and 3 (clickable name, and button to the right) was used in this situation, it could be like this:
Additional information (optional) Honestly, just wanting to reduce the time it takes for me to figure out what the update(s) did and whether or not I should nuke configs or fix up other configs due to some moon name change or something. It would solve dealing with packs that have over 50 or so mods in trying to find out what the update(s) changed. c:
The text was updated successfully, but these errors were encountered:
What problem does the feature request solve?
The semi-tedious task of going to every individual mod to click "Website" to then figure out what the change/update was/is - or having to search up the mod manually on Thunderstore's page.
Example mock-up (optional)
to the left of the mod could be the update symbol that can be clicked:
The name of the mod could be clickable - which leads to the mod page itself ( not immediately to the changelog, as some modders don't use the changelog function on the site); Or, the empty space to the right of the mod names could have a button similar to the website button (or exactly):
Or a combination of the 3... maybe clicking the name leads to the mod page - and the button to the right, instead of saying "Website", says "Changelog". That way, people can choose which one to go to immediately. Maybe have some sort of detection method to check if the modder uses the changelog page or not? For example, Gratar in the image has no changelog page:
So maybe if changelog can't be clicked (or when you force it to check the changelog page it detects the text "This package has no changelog available." on the page):
Then the changelog button doesn't appear to the right of the mod, but the mod name can still be clickable?
If Idea 2 and 3 (clickable name, and button to the right) was used in this situation, it could be like this:
Additional information (optional)
Honestly, just wanting to reduce the time it takes for me to figure out what the update(s) did and whether or not I should nuke configs or fix up other configs due to some moon name change or something. It would solve dealing with packs that have over 50 or so mods in trying to find out what the update(s) changed. c:
The text was updated successfully, but these errors were encountered: