This problem is a backend issue and client issue. The problem is when something happens in the Drop Client and you set a folder that is already full it will complain it needs to be empty. So you don't want to reinstall all your games again on something random happening. What I was thinking was maybe when a game folder is set it creates a file like ".library" so the client can read it. Once the client reads this file it knows it's a already created folder and just imports it by default without question.
Then once a game is installed from that said client that same ".library" file can be used to match the game folders to the games in the users Drop Instance. While also comparing it to what is added to the users library. So if the user instantly has all their games as installed and if the user adds one of the installed games back in there library and it's found inside the folder it instantly skips the install process and just re-list the game as installed. Using the ".library" hidden file as it's sort of database of information.
If you had a network drive this could also be useful for multiple PC's. As you could assign a Samba, NFS, or manually connect and disconnect an ISCSI. Better yet you could put your installed games on a portable HDD and move them between computers easily. As it would just pick them up as the ".library" database file would be hidden in the base directory of the Drop games folder for that library on the drive.
This problem is a backend issue and client issue. The problem is when something happens in the Drop Client and you set a folder that is already full it will complain it needs to be empty. So you don't want to reinstall all your games again on something random happening. What I was thinking was maybe when a game folder is set it creates a file like ".library" so the client can read it. Once the client reads this file it knows it's a already created folder and just imports it by default without question.
Then once a game is installed from that said client that same ".library" file can be used to match the game folders to the games in the users Drop Instance. While also comparing it to what is added to the users library. So if the user instantly has all their games as installed and if the user adds one of the installed games back in there library and it's found inside the folder it instantly skips the install process and just re-list the game as installed. Using the ".library" hidden file as it's sort of database of information.
If you had a network drive this could also be useful for multiple PC's. As you could assign a Samba, NFS, or manually connect and disconnect an ISCSI. Better yet you could put your installed games on a portable HDD and move them between computers easily. As it would just pick them up as the ".library" database file would be hidden in the base directory of the Drop games folder for that library on the drive.