Joseph Burton

IntelliJ is too smart for its own good.

Unfortunately this is not easy to fix. IntelliJ's dataflow inspections are hardcoded with no extension points for plugins. There is no way to tell it that actually no, this expression...

Note that JetBrains will be disabling this inspection by default as it is causing problems with other frameworks too: https://youtrack.jetbrains.com/issue/IDEA-352283

We have already dropped support for new features for MC 1.12, so I don't mind support for lang files being unimplemented.

The license file has no file extension so mcdev then checks to see if the first 10kb of the file can be interpreted as NBT. The first byte of the...

I think once write actions are allowed outside of the EDT we'll have to make a general sweep of the codebase to look for cases like these where we use...

I made a list of differences, along with the changed config files: https://gist.github.com/Earthcomputer/2296da33b8cc91dba81b48103c0e1fe3

> On a last note, the parantheses around lambda declarations are actually technically unnecessary. It should always unambiguously parse to either a lambda or an identifier folowed by the next...

The problem is, badly written transformers might *not* conflict when you might think they should, with the current design. The ASMR backend has a fair amount of manual conflict detection,...

The issue seems to be that Iris is ignoring the depth test value in the `RenderLayer`. This is causing the lines to not be render behind other blocks and to...