The future of this project
⚠️Read the most recent reply to this issue. The below plan is no longer in place.
As I'm sure you're aware, this repository and it's packages are currently for the Guilded *user API. I have been given Early Access to the bot API in order to adapt my library to the new bot API. Seeing that selfbots aren't necessarily outlawed on Guilded, support for the user API verison of this library will continue.
With this new API access, I will now be starting work on the
nextbranch of this repo, which will include the following breaking changes:
- current
@guildedjs/guilded.jspackage will be renamed to@guildedjs/guilded.js-selfbot.- new package will be published under
@guildedjs/guilded.jsthat covers the bot API. Will include the same caching, ws, events, and other mechanics that the old package had.@guildedjs/restwill be adapted to work for both the bot API and the user API (atm it's literally just a fancy node-fetch wrapper with retry logic, which I'll have to rework for the bot API to take into account ratelimit headers).- user API typings in
@guildedjs/guilded-api-typingswill be moved to auserdirectory in that package, and the bot API typings will be in abotdir with the API versions being separated by dirs with the appropriate version number (e.x.v1/,v2/).This process will take weeks, maybe even months. There is no planned package release date. I have full permission from Guilded employees to publish my work on the bot API on GitHub.
After months of work on support for the bot API in a separate repo, I've come to the conclusion that we will no longer support the user API once the first release of the bot API comes out. The above plan is now defunct, with all the already published packages planned to be replaced with their bot API counterpart upon release. I will be archiving this repo when the time comes. I am currently working on bot API support available here https://github.com/guildedjs/guilded.js. This is only usable if you are in the early access for the API.