Sync unsupported nexus downloads
Is this necessary? Particularly given #209, I feel it makes more sense to allow any game IDs, and unsupported ones will just fail to find a matching package later on.
I've thought about it and, actually, it isn't. Furthermore: we can use them. We can keep them in special directory (i'm thinking about
env.DOWNLOAD_DIR/unsupported) and we can check when syncing if any new manifests (for new atoms or new versions of existing atoms) match them. And if they do, we can move matches to
env.DOWNLOAD_DIR and inform the user about added support. Those downloads will be limited to nexus, so they will be (most probably) mods for some games. And if they unsupported now, they can be supported in the future, so keeping them in cache makes sense for me.
Also, we can implement option
--clean_unsupported, that will just remove all content of
env.DOWNLOAD_DIR/unsupported, if the user will need to free space.
Also, it probably can be integrated with #197 somehow. Have no idea how yet.