More Info

CABAL News Discord checks public official CABAL EU news and update pages, detects posts that are not saved yet, and sends configured notifications to Discord channels through the bot.

The dashboard is used only for login, server selection, channel configuration, test messages, and account management. Notification delivery itself is handled by the bot and worker processes.

Every due scan checks the configured official source pages.

• News list: https://cabaleu.playthisgame.com/en/News/List
• Updates list: https://cabaleu.playthisgame.com/en/update/List

The list page is used to discover post links. The detail page for each checked post is then opened to read stable information such as the real publication date and time, description, and image.

The default scan interval is 300 seconds. On normal recurring scans, the worker checks up to 10 posts per source. For each source this means one list request plus up to 10 detail requests.

With both News and Updates enabled, the normal maximum is about 22 requests every five minutes. The first scan of a source checks only one post to avoid loading old content all at once.

CABAL list pages can show relative labels such as today, yesterday, or hours ago. Those labels change over time and are not reliable for notification formatting or duplicate detection.

Opening the detail page lets the service use the direct publication timestamp shown on the post itself. This is why Discord notifications can include a stable date and time.

Posts are stored in the database with their source, URL, external CABAL content ID, content hash, title, description, image URL, and publication time when available.

A post that is already saved is not sent again. This lets the worker detect new posts inserted between older posts without resending posts that were already handled.

If CABAL publishes several posts at once or inserts posts below the top item, recurring scans can still find them because the worker checks more than the first list item.

If the database is reset or the source URL changes, old visible posts may look new to the system. In that case, a one-time catch-up may send more notifications than usual.

Discord OAuth login is used for the dashboard and server management. If that login expires, the dashboard asks the user to sign in again.

Scheduled notifications use the bot token, not the user's OAuth access token. A user login expiring does not stop already configured notifications.