Solved Are the BMS Config options secret defense?
-
Hello,
Already a huge thank you for this majestic update, you have done a great job and I thank you very much.
I often notice that some option tips are added on posts according to the need with link to problems or others, I find it a pity because it imposes to pass on many post to have knowledge of it.
ex:
set g_nScaleUIMode / set g_nCloudRotatingMethod / etc …So a small question and a small request comes out of this.
Question :
Why don’t you integrate in the BMS Config all the options that exist?Request :
Can you create a dedicated post where you indicate all the options that exist and that are not integrated in the BMS Config.Thanks in advance.
-
Are you sure those are not in the manual?
On top, some options are for dev only but we still leak them once in a while…
-
@Maveric most are in the docs. but not all, as you’ve seen
-
@Maveric many of the public ones are that should be safe to use are in the BMS Technical Manual. Although there are a few even non-development side ones that are not listed like noplayerplay.
-
-
@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.