Closed ClaudiusMinimus closed 4 years ago
That wasn't randomloot causing that
Thank you. If you saw what the issue was, it would be nice to share it. Java log files are very confusing. I talked to my adult son who is an enterprise software architect, who used to program in java if he could help me understand the logs. He said, "it can be hard without knowing the code base".
It wasn't anything to worry about, just someone's invalid update url. It won't hurt your pack in anyway just make sure you keep your mods up to date.
On Wed., Jul. 8, 2020, 12:52 p.m. ClaudiusMinimus, notifications@github.com wrote:
Thank you. If you saw what the issue was, it would be nice to share it. Java log files are very confusing. I talked to my adult son who is an enterprise software architect, who used to program in java if he could help me understand the logs. He said, "it can be hard without knowing the code base".
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/TheMarstonConnell/randomlootmod/issues/41#issuecomment-655636124, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIDXOS33LMRDEBOUZJXFIODR2SP4LANCNFSM4OTZ3UXA .
I'm going through the log files for a pack I hope to soon release on CurseForge and noticed the following, starting on line 391:
latest.log
Minecraft: 1.16.1 Forge: net.minecraftforge:32.0.44 Random Loot 2.0
Mods: