William Gray
William Gray
When throwing a java exception, the stacktrace and exception appear to be missing some data. For example, running the following code: ```java public static void main(String[] args) { try {...
so, umm... I'm trying to get a mod to remap to official on loom 12, it remaps the classes, but I'm using the new `loom.mixin.refmapTargetNamespace = 'official'` key, and it's...
[latest.log](https://github.com/wagyourtail/JsMacros/files/8065731/latest.log)
apply input does not move the dummy. is it missing a bit of the movement code or something?
remove schematica command because it doesn't work anyway on 1.13+ since sechematica doesn't exist past 1.12.2
hi, was using quiltflower idea plugin while working on some legacy stuff and encountered this so I guess I should report it xd in forge version [`1.3.2 - 4.3.5.318`](https://adfoc.us/serve/sitelinks/?id=271228&url=https://maven.minecraftforge.net/net/minecraftforge/forge/1.3.2-4.3.5.318/forge-1.3.2-4.3.5.318-universal.zip) class...
uses a modified diffie-hellman key exchange to prevent cheating
it seems like when the label order is a bit messed up, it causes the local variables at a point to be wrong in mixin. here's an example of this...
use proguard-gradle, only run proguard once for api/standalone and remap+shade the other targets in, also bump unimined version