Total nitpick, but: Why would you name an option "disable_ai" with a default value of false instead of calling it "enable_ai" with a default value of true? Are there some mechanical semantics I'm missing here that make this beneficial? Negative booleans (ie that remove or suppress something when true) are generally a source of confusion and bugs and should be avoided like the plague in my experience.
It makes sense, historically. They had AI features that were always on. Some people complained so they introduced a flag to, wait for it, disable the ai features. So they didn't think too deeply about it and named the flag "disable_ai" because it mapped into how they were thinking about it. You overstate the problem with negative booleans. It's trivial for them to add a function: fn isAiEnabled() { return !disable_ai…
if(disable_ai) { //disable shit }