[fysiks]

Originally Posted by happy_2012 No, not plugins.ini, mostly cmdacess.ini what breaks the file! AFAIK that file is automatically generated, and same goes for cmd.ini I think, not sure

cmdaccess.ini does get edited by one of the built-in functions but it only adds commands that don't already exist. So, you can modify the access requirements for commands (which you do by editing the file manually) and it won't overwrite those values that you change.

cmds.ini is one that I don't ever use but it looks like it's designed to only be edited manually.

My original point is that some "editors" that people use are not the correct type of editors for these types of files. So, I was curious if maybe the file we being corrupted during editing which then may cause issues when AMX Mod X is trying to open and read them (I'm not entirely sure of all the scenarios that might cause the specific error, I'm just hypothesizing ).

[happy_2012]

Originally Posted by fysiks cmdaccess.ini does get edited by one of the built-in functions but it only adds commands that don't already exist. So, you can modify the access requirements for commands (which you do by editing the file manually) and it won't overwrite those values that you change. cmds.ini is one that I don't ever use but it looks like it's designed to only be edited manually. My original point is that some "editors" that people use are not the correct type of editors for these types of files. So, I was curious if maybe the file we being corrupted during editing which then may cause issues when AMX Mod X is trying to open and read them (I'm not entirely sure of all the scenarios that might cause the specific error, I'm just hypothesizing ).

I am using visual studio code!

[fysiks]

Well, with VS Code, I wouldn't expect any file format issues.