Any way to bypass the "setting" command's hardcoded list?
Posted: 18 Sep 2008 18:09
Is there any way to get the "setting" script command to support all options in XY's ini file? So that anything given as "setting name", if it exists, will be changed - as opposed to having a hardcoded list of supported settings?
The first time I hit this limitation was when I was trying to turn off the Recursion Checker for just one script. I wanted that particular script to run without any recursion errors, but I didn't want to turn it off globally. But I'm sure there are many other reasons to have the settings command not be hardcoded.
The first time I hit this limitation was when I was trying to turn off the Recursion Checker for just one script. I wanted that particular script to run without any recursion errors, but I didn't want to turn it off globally. But I'm sure there are many other reasons to have the settings command not be hardcoded.
