kyrios For example, I download "fun.sh" from Good Old Games to my downloads folder. I use the command "chmod +x fun.sh" to make it executable. I then have to elevate my user rights "sudo su" or else it won't let me execute it. I run the file with "sudo ./game.sh", as the "bash" command tends to fail due to permissions. Once executed, I use the setup wizard to change the default installation path to "user/home/games/fun". I am now able to execute the game. Everything works perfectly.
The problem I encounter, is when I attempt to apply a patch, or expansion. Let's call it "DLC.sh". I'll do everything as above and indicate the prior path for installation. The setup wizard will warn me that this is probably not the correct directory, even though I have 100% certainty I have specified the correct folder for installation. DLC.sh installs, but when I boot the base game, it does not recognize that DLC.sh as having been installed.
As far as rights go, basically every folder will be protected. Taking ownership with chown or through the folder properties has to happen every time I try to access them. Furthermore, if I install games directly through software like Lutris, everything will install without warning, but Lutris won't have rights to access the files once installed.
All of it is really annoying. It's almost like the default account does not have administrator rights in the same vein that Windows 7 created UAC. The solution on Windows 7 is simply to eliminate UAC and have everything "run as administrator" by default. With Solus, I don't know how to give myself blanket rights in the same manner.