Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.esportshub.io/llms.txt

Use this file to discover all available pages before exploring further.

Patch notes track every meaningful change to the Esports Hub platform: new features, fixes, policy tweaks, and the small adjustments that make the site work better day to day. Posts are dated, listed newest first, and tagged so you can filter by area.

Browse the patch notes

Every platform change, dated and searchable.

What gets listed

TagCovers
NewFeatures that didn’t exist before. Whole product surfaces, new bot abilities, new partnership benefits.
ImprovedExisting features that got noticeably better, faster, clearer, more flexible.
FixedBugs we identified and closed. Always linked back to the affected area.
PolicyRule changes, refund-policy adjustments, moderation updates, ticket-flow changes.
RemovedFeatures or surfaces we sunset. Always paired with a “why” sentence.
Each entry includes a short headline, a one-paragraph description, and links to the affected pages or docs.

Release cadence

We post patch notes in batches. There’s no fixed release day; we publish when a meaningful set of changes has shipped, usually weekly. Smaller hot-fixes that don’t deserve a full entry are rolled into the next batch. For huge launches (new product surfaces, new partnership tiers, major policy shifts) we publish a dedicated Wave News story alongside the patch notes entry, so the context lives somewhere richer than a one-paragraph note.

Subscribing

Every new patch-notes entry posts to the #patch-notes Discord channel automatically. Enable channel notifications there if you want the alert. The page also publishes a JSON feed at /patch-notes.json for integrations and partner-dashboard widgets. Read access is open, no auth needed.

Reporting something we missed

If you spot a bug we haven’t fixed yet, or a behaviour that doesn’t match what the patch notes describe, open a Website Bug Report ticket in Discord. Include the page, what you expected, what you saw, and a screenshot if relevant. Bugs that are reproducible enough to act on appear in the next batch with a “Fixed” tag and a credit to the reporter when they want one.