Michael
Michael
Obviously, removing the conflicting package avoids the conflict, but that doesn't solve the undeclared package conflict! :P
Try: - newer version of Forge. - dropping mw/weaponlib from the pack. If that helps, talk to its author(s).
Try starting with `/profile e` output rather than attempting to make sense of the lagspike detection output. This will tell you specifically which chunks and which entities/entity types are eating...
Should I assume you'll be targetting 1.15 now?
FWIW I experience this problem quite reliably whenever sigal emits any error or warning (including `contains sub-albums`) during processing. My local disk is an nfs mount over a relatively slow...
Well I'll be dipped...I can no longer reproduce (for now...). I'll be back if that changes. :sweat_smile:
I'm also seeing this (forge-1.11.2-13.20.1.2429, BetterFoliage-MC1.11.2-2.1.7, industrialcraft-2-2.7.81-ex111). If it helps (which I hope it does!), the position referenced in the error appears to always be that of a resin hole....
As someone who routinely browses with cookies disabled, I can assure you that you are far from being the only one to make that same assumption (sadly). 😅
Does the existence of https://github.com/Ephys/mc-curseforge-updateJSONURL help at all? 🤔
Somewhere like https://pages.github.com/ ? :sweat_smile: