Closed SAOS-IT closed 1 month ago
I think it has to do with gradle always wanting to resolve dynamic versions even if offline.
You can try reobfJar.tool = 'net.minecraftforge:ForgeAutoRenamingTool:1.0.6:all'
and see if that allows gradle to resolve the artifact without needing the internet.
But ya, honestly, --offline isn't something people actually use. the internet is needed for everything these days.
Unfortunately that didn't, so I switched to mdk 36.2.34 for more stability, but thank you for your response.
I mean.. it uses the same FG version, so that doesn't change anything. But sure.
When I execute Reobf Jar task with --offline on a fresh forge 1.16.5 36.2.42 mdk, everything works fine. But it's failed the moment I disconnected my WIFI:
And it still throws that error even I had connected after that, unless I stop all daemon and starting a new one. Seem like it's always download net.minecraftforge:ForgeAutoRenamingTool:1.+ when starting a new daemon. While I already had all dependency downloaded.
Then what's the point of using --offline if it can bypass connection like that?
This problem wasn't happened on mdk 36.2.34 with ForgeGradle 5.1.+