Ampflower
Ampflower
Since this would be useful as reference: https://docs.oracle.com/en/java/javase/17/docs/specs/jar/jar.html#jar-manifest Also, a thing to account for: Hot loading agents should be considered given that application jars *may* provide one and expect it...
Fair. It doesn't necessarily have to be bundled in the main jar, and is that way with the current architecture; one is able to write an arbitrary game provider and...
That's fair. It's very likely that if you're using your own GameProvider that either... A: You're most likely going to be fine with using an older version. B: You can...
> Oh, er, not all game providers actually - quilt-provided ones would be separate (complete) jars containing bare quilt-loader plus the game-specific stuff. Oh, misinterpreted what you said then. Yeah,...
> Would sound much cleaner to me to use service providers instead. > slf4j also used to do that and switched to service providers as well. It's already in use...
A bit of a catch I ran into with developing on `quilt-loader-0.18.1-beta.27-20230105.235638-8` is that `SystemProperties.REMAP_CLASSPATH_FILE` seems to be required, along with the `intermediate_mappings` field in the `quilt.mod.json`, neither of which...
For that we just said it was `SERVER` and called it good enough when using it for ProxyFox a while ago. But yeah a dedicated enum type might be good?
Yes, example mod alone was enough; I could try binary searching which Loom introduced the bug and see.
0.9.54 with 1.18.2 generated the files. 1.0.1 also with 1.18.2 failed to generate the files. I can poke at the registry settings in IntelliJ and see if they're interfering at...
Looks like it was a bug with `gradle.tooling.use.external.process=true` that somehow interfered with how 1.0.1+ added run configurations. Resetting it back to false allows Loom to generate the IDE configuration correctly,...