Oh the evil of hiding user preferences in invisible folders ...

If one maps for Quake3 the compile settings in Radiant are stored in:

~/.q3a/baseq3/scripts/user0.proj

Note that . infront of q3a - it makes the folder invisible. There is also a user0.proj in ~/Applications/Quake3/baseq3/scripts but that one seems to act as a template. Guess which one I made a backup of before installning the new build ...

Anyway thought I should a fair warning that this can happen - for me it did when I moved MacRadiant14 to my Applications/GTKRadiant folder and launched it again after testing it straight in the Applications folder where everything was the same as with the old build. I did this as I need to keep my Applications folder organised in groups and I assumed from the descriptions that this new build stores the prefs files internally so didn't think that my old ones would be overwritten by moving it. TBH a 'abort' option in the "Warning. I need to reset some files" would be good.

cheers

The problem with GtkRadiant is that LOTS of prefs files are scattered in hidden places : the game description files in the game folder inside the bundle, the prefs files for each games (for radiant14: .radiant/1.4.0, .q3a for q3, .wolf for wolfenstein etc and for radiant15: .radiant/1.5.0) and I didn't want to mess with those locations which I didn't chose.
When the applications are moved and/or renamed, I decided (maybe a little too boldly) to have all the prefs files automatically recreated from scratch (the templates used are inside the bundle by the way).
Maybe I'll try and improve that method (first try to update the already existing prefs before creating new ones)...
Sorry for the inconvenience... my mistake....