A248 🇵🇸🇪🇭

I think this is a duplicate of #1369

I don't think JPMS is complicated. It is the standard module system implemented for the Java platform, and it is very suitable to a plugin environment. If it came to...

If we implement this feature, I am thinking it will follow this two-step process: 1. The configuration value is loaded with DazzleConf into its required type. This is what happens...

This will be easier to add in 2.0.0 since we will have a more standardized means of creating configuration instances with arbitrary behavior.

I agree with deprecating `@ConfSerialisers`. Another limitation of this annotation is that it intends for value serializers to be confined to the specific config interface annotated. This behavior doesn't seem...

It might be worth investigating using `NonZeroU128`, to take the advantage of the null-value optimization, if there are any bits known to be non-zero.

Hello, I'd like to kindly ask for an update on this. It's been a year but this bug is relatively easy to patch. Please let me know if you need...

Actually, it's worse than that, @cowwoc . Over a year ago, JPMS support broke entirely when one of the maintainers split flyway into multiple modules per database. The bug was...

Dear Flyway maintainers, As a free software developer, I am going to be completely honest with you because no one else will. The act of removing Automatic-Module-Name is completely nonsensical...

I'd second this request, as using UUIDs everywhere generally makes for better compatibility with other systems. Player names have never been true identifiers. As another example, importing from AdvancedBan to...