Using .add() with net.filebot.media.ReleaseInfo.releaseGroup doesn't work as the latter is currently private.
Use case is for the rare instances for which a group isn't a proper release group to be added to the official file, and to have changes immediately available.
I only work in black and sometimes very, very dark grey. (Batman)
Thank you for confirming.
As I mentioned it's more for ad-hoc processing rather than a stable solution.
I'll keep adding new groups to the thread in case I find them.
I only work in black and sometimes very, very dark grey. (Batman)
The reason I wanted to use the option vs a format was the way the group binding is generated.
I'm not much of a coder, but it seems much more sophisticated, for example it removes already matched patterns.
I'll try both options, see which ones works best.
I only work in black and sometimes very, very dark grey. (Batman)
From my understanding this should than pickup the file from the filebot portable directory, where the filebot.l4j.ini is also located?
Yet trying to get the new groups via {group} format always fails?
PS: This is on windows and i also tried without the xz compression.
I'm fairly sure that these System Properties no longer work since the rewrite some time 1-2 years ago.
If you want to match groups yourself, then it is recommended that you write the complete code (read text file, check each pattern, just a few lines) yourself so that you have full understanding and thus full control over matching, prioritization, pre-processing steps, etc.