๐ If you want to review this again, unarelith:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
#MAL collection builder based on "season" is incomplete
1 messages ยท Page 1 of 1 (latest)
Welcome @runic lance!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
๐ If you want to review this again, unarelith:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
Do I need to put the full log or is the part I sent enough?
Cause there is sensitive data that is not "(redacted)" in the logs:
- GitHub: token
- MAL: access_token, refresh_token, client_secret, localhost_url
Yes full log. What is not redacted in the logs?
Those should 100% be redacted
It's in my message, GitHub token and MAL tokens/secret/localhost_url aren't redacted
But anyways, I redacted them myself. Here are the full logs.
๐ If you want to review this again, unarelith:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
They're redacted for me:
| github: |
| token: (redacted) |
...
| ########## GENERATED BY MALAUTH ##########
| mal:
| client_id: (redacted)
| client_secret: (redacted)
| authorization:
| access_token: (redacted)
| token_type: Bearer
| expires_in: 2678400
| refresh_token: (redacted)
| localhost_url: (redacted)
| cache_expiration: 60
| ############################################
...
|=============================================
| Connecting to My Anime List...
| My Anime List Connection Successful
|=============================================
Then I don't know why it isn't the case for me ๐คท
Looks like perhaps in your config you have the attribute name and value on separate lines? That might be the issue.
This part was generated using Quickstart so I'm probably not the only person with this issue
But thanks, I'll change that
I suppose either Quickstart should stop doing that or the redaction logic here should account for it.
Quickstart is good for a beginner but not that great tbh:
- It adds a lot of default options to the config, which are not even needed for some of them (and some even generate warnings)
- It lacks some options, so going in the docs is still needed in some cases
- It's not clear how it works (for example having to go to "Final Validation" seems to automatically save the config)
- It overwrites/removes some options manually changed in the config without asking
- It is able to install/update/run Kometa, but:
- It would make more sense to be able to use Kometa docker container instead
- The update is automatic, would be nice to have an option for it to be manual instead
- It is able to run Kometa, but if I refresh the page I have to manually stop the process if I need to, because it loses track of it
- The log viewer is limited and when running Kometa it will keep scrolling down automatically so I can't read the logs (especially annoying with "Run at scheduled time")
- The first time I tried, it was ignoring the run parameters, so I had to manually create an .env file with the options I wanted
But aside that it was nice to start using Kometa, I'll probably make a ticket on GitHub for that.
Anyways back to my original issue, [here are the full logs](#1455308782040121394 message) which were a bit lost in the conversation.
QS is known incomplete.
Quickstart overwriting a manually-edited config is correct and expected. There is no provision for importing or editing an existing config [or one of it's own configs you've edited]. Your selections are stored in a database, and at the end the config is exported. That final config is an output-only artifact, and Quickstart pays no attention to any changes you make to it.
I changed the collection name for Summer 2025 and realized this:
- The old and new collections had 7 elements and it stayed like that for a few days
- The new collection now have 9 elements:
- It added Kaiju, Clevatess and Sakamoto Days
- But it removed Secrets of the Silent Witch for some reason
What is this based on? I don't understand how it could add/remove elements on a past season.
For information: Those 4 animes (3 added, 1 removed) were all part of the Summer 2025 season, and some are still missing in the collection.
If you really want animes seasons to work you should consider trying my script with kometa
https://github.com/Arial-Z/Romaji-Renamer