Ennui Langeweile
Ennui Langeweile
Usually, Quilted Fabric API aims to have the testmods inherited from Fabric API intact due to them helping with maintaining parity with it, with expansions of them rarely being needed...
I have a suspicion that this [commit](https://github.com/QuiltMC/quilted-fabric-api/commit/9895bd97897415e655bc9e0d5c134840f34ce892) might have made development more painful by bringing longer build times and such. While I don't have concrete proof, I have tried reverting...
Self-explanatory; I currently have something preliminary written on my hands, but yeah, there's still a lot of work to do in order for it to be useful.
While both appears to be besties so far? I do believe it's possible for one to be bridged to the another, since the latter appears to be a weird subset...
While it is quite robust so far, issues like issue #55 shows that there's more work to be done on catching all the pesky bad registrations; Any work done here...
Automating the process of renaming stuff, changing icons and generating QMJs from FMJs such would allow for a lot of time-saving in the process of upstream syncing. This might require...
Currently, our workflows have a lot of upstream stuff that has been disabled in order to allow CI to work; While they don't really matter? They can't remain disabled forever,...
Currently, there's 1 failing tests: - [ ] `fabric-item-api-v1-testmod:recipegametest/fabricremaindertest failed! Item stacks dont match. Testing fabric recipe remainder.` This might be result of divergences between Fabric API and QSL's implementation...
While I do suggest the usage of the user's GitHub page as a replacement for one, there is one tiny issue: - Maven groups are never properly explained, confusing people...