Skip to content

Add configurable rate-limits for game endpoints - #1130

Merged
Toastbrot236 merged 6 commits into
LittleBigRefresh:mainfrom
Toastbrot236:game-rl
Oct 4, 2026
Merged

Toastbrot236 merged 6 commits into
LittleBigRefresh:mainfrom
Toastbrot236:game-rl

Conversation

@Toastbrot236

@Toastbrot236 Toastbrot236 commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

This uses the newly introduced configurable endpoint rate-limiting system on nearly all game endpoints, making them no longer use Bunkum's rate-limit attribute and adding buckets for them to the enum and the config defaults.

This doesn't remove any of the now unused leftover hardcoded constants in Refresh.Core.RateLimits. That should be done in a PR after this one and a similar PR for API buckets are merged.

@Toastbrot236 Toastbrot236 changed the title Add configurable limits for most game endpoints Add configurable rate-limits for game endpoints Sep 21, 2026
@Toastbrot236

Copy link
Copy Markdown
Contributor Author

I tested most of these defaults in LBP1/2/3 a few days ago, especially the ones for fetch endpoints, and they didn't seem to trigger any rate-limits under normal operation.

@Toastbrot236
Toastbrot236 merged commit 2feae6d into LittleBigRefresh:main Oct 4, 2026
3 checks passed
Toastbrot236 added a commit that referenced this pull request Oct 4, 2026
The same as #1130, but for nearly all APIv3 endpoints. Shared buckets
and a few comments overlap with the other PR.
Toastbrot236 added a commit that referenced this pull request Oct 12, 2026
Removes all the leftover endpoint rate-limit constants outside of
`EndpointBucketDefaults`, since both #1130 and #1131 are now merged.
Also bumps the `EndpointRateLimitConfig` config version (even though
there haven't been any stable releases between #1116 and now), just to
make extra sure that all new buckets get added to the config during
migration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants