Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

[Solved] [1.16.5] How to make Curios support optional?


Recommended Posts

Posted (edited)

I haven't made a working mod since 1.12, but I'm starting a new one for 1.16.5 and I'd like it to support the Curios API. I've gotten that working, but I realized that in order to register a Curios slot, I need to reference the Curios API SlotTypeMessage class. I was hoping I could make Curios support optional, i.e. register the slot if the Curios mod is installed, or just gracefully ignore it if not, but if I'm referencing SlotTypeMessage and someone installs my mod without including Curios, won't that just crash? Is there something special I need to do to make the support optional? Or am I totally misunderstanding how dependencies are handled and worrying about crashes that won't happen after all?

Edited by IceMetalPunk
Solved

Whatever Minecraft needs, it is most likely not yet another tool tier.

Link to post
Share on other sites
  • IceMetalPunk changed the title to [1.16.5] How to make Curios support optional?

You have to confine classes that interact with the dependency to one part of your mod which must not directly be accessed from anywhere else in your mod. The way you then interact with it is that you have an interface (say CuriosCompat) which is implemented twice. Once for when Curios is not present and once for when it is (this 2nd one can reference Curios classes). Then at startup check if Curios is loaded (the ModList class tells you whether a mod is loaded). If it isn't, instantiate the first implementation. If it is, get the 2nd implementat class using reflection (Class.forName) and create an isntance of it (newInstance()). You cannot reference it directly as otherwise the JVM will try and load this class even though the code is never executed.

  • Like 1
Link to post
Share on other sites
Posted (edited)
15 hours ago, diesieben07 said:

You have to confine classes that interact with the dependency to one part of your mod which must not directly be accessed from anywhere else in your mod. The way you then interact with it is that you have an interface (say CuriosCompat) which is implemented twice. Once for when Curios is not present and once for when it is (this 2nd one can reference Curios classes). Then at startup check if Curios is loaded (the ModList class tells you whether a mod is loaded). If it isn't, instantiate the first implementation. If it is, get the 2nd implementat class using reflection (Class.forName) and create an isntance of it (newInstance()). You cannot reference it directly as otherwise the JVM will try and load this class even though the code is never executed.

Ah! Using reflection to prevent crashing is the trick I needed to know! Thank you, I'll work on implementing it when I get a chance; hopefully it should go smoothly, if not, I'll ask more here with more details.

EDIT Worked perfectly the first try 😁 Thank you for your help!

Edited by IceMetalPunk
Update

Whatever Minecraft needs, it is most likely not yet another tool tier.

Link to post
Share on other sites
  • IceMetalPunk changed the title to [Solved] [1.16.5] How to make Curios support optional?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.