nemostultae wrote:Make autoexec.cfg in ~/Library/Application Support/Armagetron Advanced/config, so when you upgrade you don't need to migrate your settings.
So not the var folder, but rather make a new folder called "config" in the above location? If so, perhaps you should make that edit to settings.cfg, because right now it says to make an autoexec.cfg and place it in the var folder. (I ran into the same problem as rogue.)
Oscilloscope wrote:So not the var folder, but rather make a new folder called "config" in the above location? If so, perhaps you should make that edit to settings.cfg, because right now it says to make an autoexec.cfg and place it in the var folder. (I ran into the same problem as rogue.)
hmm.. it works both in config/ and var/. Is there a specific reason settings.cfg recommends keeping it in var/? I like to keep my hand edited config files in config/ (my user config dir, that is).
Two reasons: I guess previous Windows installers may have wiped out the config directory, and var is the place I always put things when I run my stuff from the build directory So no, no particular reason.
And it should work in var...
Alright, I realised what the oversight was. When making autoexec.cfg in TextEdit (the app most Mac users would likely use), one has to be sure to set it to "plain text" in preferences. The game evidently won't read rich text. Doing that, I was able to just stick autoexec.cfg into the var folder and have it work. Der. Still, it might be helpful if you added a line about it needing to be plain text to settings.cfg (and settings_dedicated.cfg) somewhere in this paragraph:
# IMPORTANT: Users should NOT edit this file. Instead, copy the
# lines you want to change into a new file named autoexec.cfg
# ( either here or in your var directory ).
# This file will be overwritten when you upgrade, autoexec.cfg won't.
This is another example of one of those little things where programmers may assume to much on the part of the average user.
Will do, but I'd like to note that this is really a case of "programmer doesn't know there is a TEXT editor with the default of writing rich text as the default text editor anywhere" and "furthermore, programmer thinks this behavior is braindead.".
What I meant by the assumption thing was that some users may have no clue that a config file would have to be in plain text format. Put a little note in there about how it does, and there won't be dopes (say, like myself) coming here and asking why something simple won't work.
I'd say the only the text format is just pure text, so unless mentioned otherwise, always use that.
TextEdit: Use Format -> Make Plain/Rich Text (shift-cmd-T) to change only the file you're working on, not all new files you create. At least the 10.4 version even mentions that in the preferences window, a few pixels above the radio buttons.
i'm on osx aswell and my camera is all fuxx0red