rednoah wrote: ↑06 Aug 2021, 02:28

Please copy & paste the complete command-line and console output. If you're using FileBot Node, please copy & paste the complete text content in the black box.

Please read
How to Request Help.
1.
Your .exclude list file is in the input folder, and so FileBot will ignore this file
(just like any other hidden file) from processing:

This is the correct behaviour. You don't want to process your exclude list file. You only want to process your media files.
2.
You're not passing in any input files or folder for processing:

The input folder you're passing in either doesn't contain any media files, or appears to not contain any media files due to permissions.

If you're using
Synology DSM then you may need to explicitly grant file access permissions:
rednoah wrote: ↑10 Jul 2014, 06:56
Package Permissions:
DSM 6.2.4 and DSM 7 restrict file system access by default. FileBot Node may not be able to access your files unless you explicitly grant permission first.
1. I know why this is happening.
If I set it to exclude files and the .excludes file does not exist then Filebot detects everything as exclusive, and excludes everything.
So if I create the .excludes file then Filebot works! =)
The only question, let's imagine that I create an .excludes file, that text file, how do I have to separate the file extensions that I want to exclude?
rar, png
or
rar png
(within the text file .excludes I mean)
2. If I remove from the configuration that excludes .excludes and leave that field empty, I understand that it does not exclude anything, therefore it would process everything, nothing happens if I do this, right? I have read that I can be penalized or something like that.
Thanks!