Pr-downloader fails to load data because of invalid path

[springjools]

Rapid fails to download anything because it uses some path on my T: drive, which is a network drive and not available. How can I set it to permanently use the current directory instead?

This also prevents integration with lobbies...

[abma]

permanently isn't (easily) possible as pr-downloader has no config file.

use pr-downloader --filesystem-writepath . zk:stable

to download to the current directory. an alternative would be to fix your homepath / the network path (by changing the path of it or connecting the drive)

related to #12

[springjools]

That extended command worked, but I always have to do that manually then. It should be default behaviour to download to current directory. Somewhere within the program there must be information what directory to use, and that's wrong, because the folder it tries to use has never existed and can not be made to work.

[springjools]

But I still don't get it why the path is hardcoded?

[abma]

pr-downloader has no config file

[ScarylePoo]

Perhaps it would be a decent idea to add prdrc and allow it to be set in there? Perhaps the default could stay as a failsafe?

[abma]

what is prdrc?

[ScarylePoo]

I should have written it as .prdrc, but windows complains about .filenames, but I figured you would understand what I meant.

[abma]

i repeat:

pr-downloader has no config file

[ScarylePoo]

Perhaps it would be a decent idea to add prdrc and allow it to be set in there? Perhaps the default could stay as a failsafe?

-_- Just because it doesn't have one now doesn't meant hat it could not have one in the future. In other words, you could add the ability to have a config file.

[springjools]

Or prd.ini, so that it also works on windows...

Sent from my iPhone

On 28 Jul 2015, at 05:21, ForbodingAngel notifications@github.com wrote:

Perhaps it would be a decent idea to add prdrc and allow it to be set in there? Perhaps the default could stay as a failsafe?

-_- Just because it doesn't have one now doesn't meant hat it could not have one in the future. In other words, you could add the ability to have a config file.

—
Reply to this email directly or view it on GitHub.