
1.18.X - 1.19.X Forge Client Side Mods Helper Wildcard Support
P3rf3ctXZer0 opened this issue ยท 2 comments
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I would like wildcard support for mods blacklist; example TextruesRubidiumOptions-1.0.4-mc1.19.3 to TextruesRubidiumOptions*.jar
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like wildcard support for mods blacklist; example TextruesRubidiumOptions-1.0.4-mc1.19.3 to TextruesRubidiumOptions*.jar
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
There isn't any
Additional context
Add any other context or screenshots about the feature request here.
I would like wildcard support for mods blacklist; example TextruesRubidiumOptions-1.0.4-mc1.19.3 to TextruesRubidiumOptions*.jar
Thanks a lot for the feedback. Currently the mod already include a kind of wildcard support by automatically stripping out the versions numbers from the given file names.
The file name TextruesRubidiumOptions-1.0.4-mc1.19.3
will basically match with anything like TextruesRubidiumOptions-*-mc1.19.3
.
If this is not working for a specific use-case it would be great if you could provide an example to improve the version stripping.