Script error on previously working script

[WildernessJ]

In the last day or two my script has stopped working and I'm not sure why. It appears related to looking for The Movie Db, as even if I load up a file in the filebot application rather than using command line or my script and select TMDb I get a nullpointerexception error.

Code: Select all

filebot -script fn:amc "C:\Users\Holdy\Downloads\Torrents\Downloaded" --output "C:\Users\Holdy\Downloads\Torrents\Renaming Folder" --action move --conflict skip -non-strict --def "movieFormat=Movies/{n} ({y}) - {vf}" 
Parameter: movieFormat = Movies/{n} ({y}) - {vf}
Argument: C:\Users\Holdy\Downloads\Torrents\Downloaded
Input: C:\Users\Holdy\Downloads\Torrents\Downloaded\Elysium.2013.360p.avi
NullPointerException: java.lang.NullPointerException
java.lang.NullPointerException
        at net.sourceforge.filebot.web.TMDbClient.searchMovie(Unknown Source)
        at net.sourceforge.filebot.media.MediaDetection.queryMovieByFileName(Unk
nown Source)
        at net.sourceforge.filebot.media.MediaDetection.detectMovie(Unknown Sour
ce)
        at net.sourceforge.filebot.media.MediaDetection$detectMovie.call(Unknown
 Source)
        at Script2.detectMovie(Script2.groovy:237)
        at Script2.detectMovie(Script2.groovy)
        at Script3$_run_closure31.doCall(Script3.groovy:136)
        at Script3.run(Script3.groovy:121)
        at net.sourceforge.filebot.cli.ScriptShell.evaluate(Unknown Source)
        at net.sourceforge.filebot.cli.ScriptShell.runScript(Unknown Source)
        at net.sourceforge.filebot.cli.ArgumentProcessor.process(Unknown Source)

        at net.sourceforge.filebot.Main.main(Unknown Source)
Failure (░_░)
Launch4j: Failed to run the given command.

Despite the error seeming related to the movie database, the script hasn't been processing TV shows that I've downloaded either. Manually dropping the tv shows into the filebot gui works fine, as does doing movies and selecting IMDb. I haven't changed or updated my script recently, so I'm not sure where the problem might come from.

[rednoah]

The cause of the issue is that TMDb can't lookup "Elysium 2013" AND that there is a release group called Elysium at the same time.

Fixed with r1708

[WildernessJ]

Thanks again for the quick reply and help