I would like to know whether you have any plans on further supporting the CurseForge API after they implement the changes listed in a newspost of theirs.
Going forward, one will require an API token from CurseForge in order to access it. It would be awesome if you would allow users of your CurseAPI project to set a property containing said key, or otherwise allowing users to set the key so CurseAPI can continue to work with the API.
My project ServerPackCreator is going to heavily depend on your CurseAPI with the next release, and therefore will need to make use of a CurseForge API token. It would be awesome if there would be something you could do, so people like me could continue to not only use the CurseForge API, but your CurseAPI as well.
Hello TheRandomLabs,
I would like to know whether you have any plans on further supporting the CurseForge API after they implement the changes listed in a newspost of theirs.
Going forward, one will require an API token from CurseForge in order to access it. It would be awesome if you would allow users of your CurseAPI project to set a property containing said key, or otherwise allowing users to set the key so CurseAPI can continue to work with the API.
My project ServerPackCreator is going to heavily depend on your CurseAPI with the next release, and therefore will need to make use of a CurseForge API token. It would be awesome if there would be something you could do, so people like me could continue to not only use the CurseForge API, but your CurseAPI as well.
Cheers, Griefed