[Bug] Debugify asks for YACL 3.x even if 3.1.0 is present on mods folder
vico93 opened this issue ยท 3 comments
Bug Description
Basically, i got this line on my latest.log when loading a singleplayer world:
[13:32:45] [main/WARN]: Warnings were found!
- Mod 'Debugify' (debugify) 1.20.1+2.0 recommends any 3.x version of yet-another-config-lib, which is missing!
- You should install any 3.x version of yet-another-config-lib for the optimal experience.
But i have yet-another-config-lib-fabric-3.1.0+1.20.jar
on my mods folder.
Pretty minor (mods seems to work normally regardless of this line) but solving it could prevent further confusion in future unrelated issues.
How to Reproduce?
No response
Expected Behavior
No response
Version
2.0
Fabric/Quilt Loader Version
Fabric 0.14.21 for 1.20.1
Logs or additional context
No response
Has not been reported.
- I made sure this bug hasn't already been reported.
Is on most update to date version.
- I made sure I am using the most up to date fabric/quilt loader and mod version.
this is an issue with the fabric.mod.json, it askes for the wrong yacl ID i manually whipped up a hotfix if it bugs you, but weirdly its fixed in the source but not the jar...https://www.dropbox.com/scl/fi/268ol8t7f3rxrr5lgcxl1/Debugify-1.20.1-2.0-HOTFIX.jar?rlkey=o7zbgim5j6vva73fk526nu5wt&dl=0
edit i am not affiliated with the dev in any way, just sharing my hasty personal hotfix