FileBot

This is a pretty minor bug that as mostly just an annoyance when I was testing my amc script on files that I had already hardlinked/organized previously with filebot. Filebot will still honor the conflict parameter when you run in action test mode and delete the existing files in preparation for new ones that will not be moved since its test mode. Running in test mode should ignore the conflict/delete step.

You mean in the rename(...) call? That should work. But the Groovy code in the script may not respect --action test though. Logs would help with this one since I never had that issue.

I can send logs but they don't really contain much helpful information but basically if you run: you'll get something like: if you then run it again on the same files: you'll get: and the original /to/to.ext from the first filebot run will be deleted even though you ran the new action in test mode

the reason I wouldn't run the second call in skip mode is because then nothing would happen and I wouldn't be able to test my amc changes.

I see. Fixed with r2791.