A248 🇵🇸🇪🇭

This doesn't seem like an issue with Glowstone. From the SavageFactions source, it's clear it accesses craftbukkit packages to determine the version. This is the line which generated the error:...

Any and all log messages in Velocity are already configurable via log4j2. I'd suggest you refer to such documentation on logging. It's quite powerful.

@orblazer I suggest creating a jar with nested jars, then extracting them at runtime. I've previous work implementing this in a server fork for someone else. If you want an...

This is quite a lot of boilerplate and a non-negligible maintenance burden for such a feature, but I'm not to be the judge of that considering I'm not a core...

I'm not sure if this is still under heavy consideration, but there's an important point missed here. Consider: > deter mis-using these methods on a full blown component as if...

Would you like an integration test to verify the contents of `META-INF/services/` match up with the `provides` directives in the module descriptor?

> @A248 Can you check the build error? It doesn't seem to build at all on CI. I see it now. However, I tried and failed to reproduce the failure...

@kdubb I came back to this and tackled the build failure. I managed to reproduce the compilation failure and solve the issue. Let me know if there are any other...

The minimum Java version for API 9 is 17, but the README on the api-9 branch states otherwise: https://github.com/SpongePowered/SpongeAPI/blob/api-9/README.md#prerequisites

Gradle 7 has improved support for JPMS. Are there plans to work on this issue in buildship? This is a blocker for projects whose maintainers are (rightfully) reluctant to add...