Chen Liang
Chen Liang
Now 21w39a splits vanilla server and its dependencies. It may be a good time to revisit this concept.
Imo a tag unification system, where two ids, such as `c:tin_ores` and `forge:ores/tin` can be merged to refer to the same tag (instead of one contained in the other), would...
Imo we indeed should move them to a `loader.api.entrypoint` pacakage. If people are really concerned with class renaming, we can just handle that with a custom classloader if things go...
Assuming you only have the loader (no api), does it happen when you connect vanilla client to fabric server or fabric client to vanilla server?
So @gudenau what is the purpose of us implementing modules? To restrict mods? I don't see any benefit here, especially given modules cannot supply different versions to different requesters.
Hmm, an advantage of turning loader and api into java 9 modules (only if java higher than 9 is present) is that in that case mods written in java 9...
Problem is the code you depend on will be in the unnamed module, like all vanilla classes. As a result, you cannot make your mod in a named module, as...
That will require packing all vanilla's dependencies into modules (at least automatic modules with `Automatic-Module-Name` jar attribute) first, and then add an `Automatic-Module-Name` attribute to the vanilla jar
Should be possible.
Hmm, now I looked at java's module api. Seems that anyone can create automatic modules than depending on java's Automatic-Module-Name scan; with java 9+'s multirelease jar, we can possibly add...