Closed ColonelGerdauf closed 1 year ago
In situations like 1.16.4, the mod is listed as specifically for 1.16.4, and is not listed for 1.16.5, despite being fully compatible in situations like that.
This can create awkwardness with launchers when they try to update the mods.
This problem is still present, in the context of Forge.
When it comes to Modrinth and non-default launchers, version specificity is very important.
In situations like 1.16.4, the mod is listed as specifically for 1.16.4, and is not listed for 1.16.5, despite being fully compatible in situations like that.
This can create awkwardness with launchers when they try to update the mods.