Repository navigation
[Page Request] Designing a mod API #174
Description
Basically some "recommended guidelines" for what mod APIs should look like.
Ama said in stream chat he's had it planned, I'm just adding it here so people can add their input and for it to be officially on the todo-list ^-^
Reacted by Cadiboo and Zhukov Georgiy
Activity
JTK222 commentedon Jun 18, 2018
What do you expect from this? Everyone images a perfect API differently.
I would like to do something into that direction though if you can explain it better.
Bluexin commentedon Jun 22, 2018
Was about what kind of stuff to expose trough capabilities, interfaces, or other means (and how to properly go about exposing the things), and the proper way to consume them (like how to not use
@Optionalwhich is getting removed and apparently was bad practice in the first place, not including the API classes etc).Even though different people see APIs in different ways, as a result some are very bad to work with. Maybe some guidelines could help having a more uniform API style, where using different mod APIs could be done in a similar way.
TheCurle commentedon Mar 25, 2021
Kevin, ask on the Forge Forums. This isn't the place to get mod support.