The issue is random for some users.I was asked by Fabulously Optimized modpack author to find reason of this.According to Java documentation StackTraceElement.getFileName() can return null.
StackTraceElement.getFileName()
Returns: the name of the file containing the execution point represented by this stack trace element, or null if this information is unavailable.
You are calling getFileName().equals unsafe way without null check, so it’s causing issues.
getFileName().equals
Fix for this: KostromDan/Simple-Snowy-Fix: Fix of https://bugs.mojang.com/browse/MC/issues/MC-119599
KostromDan
KostromDan
The issue is random for some users.
I was asked by Fabulously Optimized modpack author to find reason of this.
According to Java documentation
StackTraceElement.getFileName()can return null.You are calling
getFileName().equalsunsafe way without null check, so it’s causing issues.