NebelNidas

Results 68 comments of NebelNidas

Not to forget LiteLoader

Is this still relevant? I've used Enigma a fair bit over the past year or so, and I can't recall seeing this particular error at least once

The Fabric toolchain quite prominently states that it's not intended for recompilation, so I guess this is a non-issue. On a separate note, wouldn't it be best to remove Enigma's...

Should be fixed as of https://github.com/FabricMC/Enigma/pull/448, I think this issue can be closed

Fixed as of 9c736848fb7aa82d295b3aa2946e6cd132ee998f

Upstream has been fixed recently, also this is more of a decompiler issue rather than an Enigma issue, so I suppose this can be closed

Fixed via #401 (although now that Enigma requires Java 17, maybe we can move back to AWT's FileDialog?)

More of a decompiler issue, nothing that Enigma can fix on its own

Modern Enigma by default treats all classes as obfuscated, regardless of package, so this issue can be closed

Not sure if I understand your description correctly, but I don't think this issue happens anymore in the latest Enigma releases