Gegy
This seems to be related to the Procyon update. It seems to call `visitInvocationExpression` with comparison expressions like `fcmpl(Math.abs(arg2.c), 22.5f)`. Enigma currently expects a `MemberReference` attached. Not sure if Enigma's...
Interesting. Maybe a different issue before -- but the Procyon update has definitely caused this NPE to come up more than before.
Can be addressed along with #77
As an alternative it's possible to select tokens to find where the class originates. Anyway, as it stands, imports might be challenging to implement. The class is decompiled as obfuscated,...
Does this work for imports of obfuscated classes? I'm not sure how it would get around the issue with displaying imports mentioned in #136.
The option might be a bit misleading and potentially have very limited scope for use.
As of https://github.com/FabricMC/Enigma/commit/574c99db3a665f043886e102eec86e5403dfcc9f, the stackoverflow errors should no longer be swallowed by Enigma and instead displayed.
Probably easiest way to work around would be to process the jar to move all the obfuscated classes out of that package, and then import that jar into Enigma. On...
None that would exist already -- you'd have to make your own
Will do global pre-processing of this similar to water data.