im not sure if the system handles files appropriate with reguards to writing files in user writable locations. cfile is kinda smart and will find the file you're trying to open anywhere in the mod hierarchy. however when a script needs to write out a config file or some other kinda file output operation, im really not sure where the file goes, i would assume either fs root or the mod's data folder. such files would ultimately need to be placed in mod specific writable locations. cfile would need to be able to read and write to those locations, and would need to maintain some kind of directory stucture to ensure that different mod's files wouldnt interfere with eachother. like if somone wrote a generic script to save a bunch of data to a file, and this script was used in 2 different mods. the files would need to be in similar mod directories under the game's folder in %appdata%.
most of my testing with file output was done with an admin account so that i could circumvent any write restrictions. this is ok for development but not really something that should be done in a script/mod release. and that was before there was much discussion about really moving to change file handling to the correct way of doing things. this has been a concern to me for some time. the general rule of thumb is to completely overlook scripting when implementing a new feature that changes something in a way that affects scripting.
this is something which should be avoided in this case in order to ensure scripting doesnt break the rules of the os that the game should be obeying.
