When downloading anything but the release version of a mod that has multiple versions, the app shows that the mod needs to be updated to the release version, even if it was updated at the same time. It's more a quality of life issue, making me think it needs to be updated, when I have it set for automatic updates. Even when I choose that I want to keep the beta version updated, because it's not the release version, it doesn't change the orange update button from being available to be pressed, so it can go back to the release version.
This board is being moderated, if you wish for your idea(s) to go public, please consider the following:
If your idea already exists, vote for it, this will increase the chances for the idea to become reality. Duplicate ideas only split and lower votes
This board is for new ideas and feature suggestions, for technical issues or bug reports, visit/contact CurseForge Support
This ensures that the idea is accessible to a wider audience and makes it easier for others to understand and vote for the idea
Any ideas posted with foul language will not be published and get deleted
Avoid posting 'lists' of different ideas, we won't be able to address them with a proper status and they will get less votes from others, each idea should have its own post
Hello,
Your request describes a specific user experience issue within an application that manages mod downloads, particularly concerning beta versions and their perceived "update" status. It highlights that:Beta versions are incorrectly flagged for update: Even when a user intentionally downloads a beta version, the application prompts them to "update" to the release version.Confusion with automatic updates: This behavior creates confusion, making users think an update is necessary when they already have automatic updates enabled and are specifically choosing to stay on a beta track.Persistent "update" button: Even after indicating a preference to stay on the beta, the "update" button remains, suggesting a downgrade to the release version is available, rather than reflecting the current desired state.Essentially, you're looking for the application to:Distinguish between different mod versions (beta, release, etc.) more clearly.Avoid prompting "updates" when a user has explicitly chosen a non-release version and intends to stay on that track.Reflect the user's chosen version status accurately, perhaps by changing the "update" button's state or text when a beta is intentionally selected and up-to-date within its own track.
marykayintouch com
Best Regards