Talk:Con GetINISetting

Does this actually work?

con_GetINISetting Activate

I don't get anything from getIni or setIni unless I use the syntax:

getIni "setting:Subsection"
setIni "fDefaultFOV:Display" 90 ; example

But I can't access the Controls section at all, and other settings seem to be unavailable too. It's not an issue with OBSE, but the console function itself. Is there some alternate syntax I'm unaware of? Or, rather than actually consulting the Ini file itself, does getINI just use a more limited list defined somewhere else? Scruggs 22:00, 12 August 2006 (EDT)

Dragoon Wraith TALK 10:53, 13 August 2006 (EDT): Oh, I don't know how it works. I did this entire section based on commands.txt and this article, so I had very limited information.

I also doubt that you could actually access the commands section in a usable way because it's in hexadecimal and script has no way to handle hex. I just don't know the INI well enough to know what kind of information you'd actually like to find.

Dragoon Wraith TALK 11:01, 15 August 2006 (EDT): Are you sure you literally can't access the controls, or is it just that you can't do anything with them because they're in Hex? I would expect this

if ( con_GetINISetting Controls:Rest == "0014FFFF" )

would work, and could be useful for determining if the player is using the default set-up. You just can't say "set var to con_GetINISetting Controls:Rest" (at least, that's my understanding.

You can't get a value to compare against in the first place. Certain settings just return a "Cannot find setting" error message (paraphrased). According to Ian, only settings that begin with a type indicator (i.e. "b", "f", "i") can be used. I suppose the compiler needs to know how to cast the result before fetching it. Scruggs 17:25, 16 August 2006 (EDT)

Dragoon Wraith TALK 18:23, 16 August 2006 (EDT): Ah, that makes sense, then. Alright, I'll update the article accordingly. What would be a good example, then?