coko7 / tcb-opus Goto Github PK

3 modes:

• Simple: Only post a notification message without a link to the direct chapter
• Direct Link: Takes the existing link from the original Discord message and embed it in the notification message
• Scraping: In case a direct link to the chapter page is missing, uses the manga name to search and scrape the TCB website

Sometimes, TCB change the way their URL look by adding additional parts at the end.
Despite that, here is what the URL should always look like:
https://onepiecechapters.com/chapters/{Id}/{mangaName}-chapter-{chapNum}{suffix}

The {chapNum} is the one thing we care about and it should always be an integer.

The data.json is not present on Git by default and must be created in order for the bot to run because of require("data.json").
Change this call to a readFile call and create the file if it does not exist beforehand.

Add option to use Regex for manga name in opus-config for more complex manga names that might have several aliases

Changes in TCB message format causes the thread name to be invalid:

This occurs in "FROM_MSG" fetch mode.

Add some logging to debug when problems happen.
A few libraries to look at:

• winston
• loglevel
• pino

See others on Openbase

Whenever there is a manga update from TCB, the bot will try to identify which manga it is based on the message.
If there is an entry for the manga One Piece and if it set to a regex like One(.?)Piece then it causes a problem because updates of all manga titles will be detected as One Piece. See below:

The reason this is happening is because the regex match is too permissive for "One Piece" and so it stops at the host name of TCB: "https://onepiecechapters.com/chapters/5593/black-clover-chapter-347"

The way regex match on manga titles should be modified to ignore this case. Maybe instead of looking for a match in the entire match, we should first isolate the URL and use a regex pattern on the right-hand side to only extract the manga title (See #7)