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
With some simple regular expressions you might be able to pull the supported Minecraft Version from the filename. I usually name my mods like FloodLights-MC1.7.10-0.3.5-40.jar. MC1.7.10 is the mc version, 0.3.5 the mod version and 40 is the build number on my jenkins. It should be rather easy to grab the MC version from that. MC[0-9].[0-9].[0-9]{2} or something like that should match the version then just add in groups and you got the versions in 3 variables.
The text was updated successfully, but these errors were encountered:
Every mod author seems to have a different naming convention, though. I, for example, put the MC version first: "1.7.10-zeldaswordskills-1.0.jar", and many don't put the MC version at all (though they should).
Would you handle multiple scenarios, or require all authors to conform to one standard?
Also, MC version is already handled in the JSON, so what extra benefit would this feature provide?
With some simple regular expressions you might be able to pull the supported Minecraft Version from the filename. I usually name my mods like FloodLights-MC1.7.10-0.3.5-40.jar. MC1.7.10 is the mc version, 0.3.5 the mod version and 40 is the build number on my jenkins. It should be rather easy to grab the MC version from that. MC[0-9].[0-9].[0-9]{2} or something like that should match the version then just add in groups and you got the versions in 3 variables.
The text was updated successfully, but these errors were encountered: