-
Notifications
You must be signed in to change notification settings - Fork 49
Required features for Curios #84
Comments
I can handle the Screens AWs and the ContainerFactories. I've got patchwork-containers started locally but it needed to be rewritten since Nuclear was using MethodHandles from pre-AW. |
this is on fabric too :tiny_potato: |
:tiny_potato: |
In addition, curios is available on fabric for 1.16, but patchwork is still on 1.14. There are several mod APIs at this point that I think it'd be worth investigating forge mods interacting with the fabric version of the api, but the ones I've seen so far are not present on 1.14, which makes testing that and developing a framework around that a bit more difficult. In the meantime, there are always more forge events and stuff to implement. |
Curios API uses IMC on Forge so using the Fabric counterpart wouldn't work here. |
Hypothetically someone would make a wrapper lib that translates the IMC API to the underlying fabric one, but that's out of scope for here. |
CurseForge
This mod is interesting largely because it's required for Botania (though needless to say that's some ways off), however numerous other mods also use it.
These are all the things I could find that it needs to (after stubbing them out) reach the main menu. It then crashes while loading in from
@CapabilityInject
not being implemented. As such it likely uses other features, and I'll update this once it's implemented.patchwork-gui
(famous/VFMADD said in Discord they'd be working on these)patchwork-events-entity
patchwork-events-lifecycle
(probably the best place for this):Unknown module/other:
Bugs:
FMLLoadCompleteEvent
must be sent afterMinecraftClient.init
has returned, since Curios uses fields fromMinecraftClient
(See FMLLoadCompleteEvent sent before Minecraft.init has returned #85, PR Make FMLLoadCompleteEvent call at the correct time on the client. #91).Access widening:
The text was updated successfully, but these errors were encountered: