So, keeping it short as i can, i copied files over to the openxcom data directory for several mods and then ticked a bunch of them to try them out. pretty straight forward, they should work fine, however, when i restarted, the following errors appeared /data/resources/folder/image.png:could not open " ".
and i think i know the cause of the issue. because the repository version of openxcom installs the game into the usr/share directory instead of the home directory, it automatically is locked into root permissions, which doesnt interfere with the unmodded version of the game, but wreaks havoc when trying to mod it.
i tried setting permissions in the data folder to the user, which actually fixed some of the permission problems, but still get this error for one mod in particular even with permissions fixed. it only has trouble reading the sprites for this one mod. every thing else so far is fine. the mod in question is the gauss gun mod. i have since tried setting permissions multiple ways using both command line and gui to try and get it to read finally, but to no avail. it still says the file is missing even though it is right there in the folder with thumbnail too. the only thing i can think of is it is nested in a root permission set of folders under usr/share/openxcom, which would probably cause problems since the main folders need root permission but the data folder has been taken over by me.
so my question is this, is there a way to move the whole openxcom directory to the home directory and still function, or is there a way to fix this without losing the whole install? and perhaps could it be possible to fix this in a later release so the openxcom install itself is not nested in root permission folders? there is no good reson for it to be nested in folders that need root permission at all, it is simply a game. several other games are installed in the home directory where they can easily be modified by the regular user without logging in as root, and i see no reason why openxcom has to be the exception to this rule. i have a feeling this would solve a lot of problems for linux users in the future.
if there is a way to change the mods config file to untick this particular mod or any others and get the game working that is fine too, but methinks later versions should abstain from installing it into root permission folders.
EDIT: i also think something else may be an issue, if in fact it is the same as other games ported to linux or installed in wine. windows is case agnostic, but linux is not, so if the config files or scripts or rules are looking for a case specific file name, and the case is different, it will not find the file in linux, it plays stupid... so usually this is alleviated by changing the case on all files and folders in linux game directories to match the names in the configs or scripts. or just to make them uniform so linux has an easier time. if this is an issue, then i have a problem still, because my batch file renamer must access a non root folder and files or it wont be able to write the case changes. however if the script is written or config is written with mixed case this also poses problems even if i were to change everything to upper case to mimic the original xcom file format.