@Maveric didn’t mean to sound “rtfm” … your general question is valid – but I think it’s perfectly fine that some internal cfg is not documented.
obviously BMS devs have invested a lot in the ability to turn off or change things, in cfg, after launch. that is very cool, very powerful and valuable
but once you document something, it creates a sort of contract … or at least, a loose expectation that something is a supported “feature”, that won’t change without warning
So, when you learn about something like g_nScaleUIMode, think of it as something with no contract or expectation of support. Maybe it will go away in a future release. Maybe it will cause some other bugs… etc.
Think of it like the Windows registry. There millions of registry keys… maybe more, whoknows. But only a tiny percentage are ever documented and supported.