Added DiscordPHP and DiscordPHP-Slash to community resources #2441
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DiscordPHP has returned from the dead and most (all?) of the latest features have been implemented.
The rate-limit system was approved back in 2016 but has been revamped to handle rate-limit buckets which were not present back then. This includes halting all requests on a 429 and attempting to bundle requests together to predict rate-limits.
The current rate-limit handling can be found here:
All notable features are implemented including the REST and WebSocket APIs as well as sending/receiving voice.
--
Also added the DiscordPHP-Slash library to community resources. Allows users to register commands with the Discord servers as well as a script that can be served to listen for interactions sent to the endpoint.
Rate-limiting logic for DiscordPHP-Slash is limited to halting all requests on a 429 response:
Since all HTTP requests are related to registering commands I don't forsee any rate-limit issues because the library is synchronous.