As it currently stands, the Curseforge app will not download a mod if the version does not match, especially if the version change is as little as a minor version bump.

For example, the difference between 1.12.1 and 1.12.2 as well as 1.18 and 1.18.1 are quite insignificant and require no code changes. Even though this is true, the Curseforge app considers these too different and files have to be updated accordingly.

This is a problem, especially for those on slow internet connections having to navigate the pages, because the process requires going to the project (1 page), going to the file (2 pages, editing the file (3 pages), then saving the project (4 pages, and a bar that obstructs the user profile button for several seconds). A total of 4 pages to navigate with an additional time buffer because of a website element that obstructs the navigation bar.

What would be preferred is either:

1. Lump Minecraft versions into major versions. 1.12 includes 1.12.1 and 1.12.2, or 1.16 includes versions 1.16.1, 1.16.2, 1.16.3, and 1.16.4. This way, if a file's supported versions is not listed, it can still be downloaded for the specified version. Specific minor iterations can also be specified.

2. Less page navigating to specify what file supports what version. Minor versions are sporadic and cannot be predicted, so it should not be on the author to specify what versions can be supported, especially if they author numerous projects.