autopilot.js: losing --enable-bladeburner flag after installing augs

I see the reasoning behind disabling bladeburner by default, but in BN6 and BN7 that should not be the case I think, so I run autopilot.js --enable-bladeburner there. After autopilot decides to install augs, the flag is lost and bladeburner gets disabled again - even when I already installed The Blade's Simulacrum.

I think its more sensibe to default to run bladeburner regardless of the flag, at least when The Blade's Simulacrum is present. Even more better would be if this (and potentially all) autopilot flags would survive installing augs. (In this case, because the concurrent Bladeburner aug is pretty expensive and probably not obtained in the first resets).

What do you think about this?

[alainbryden]

@Evanito no need! It was always part of my plan to then leverage this feature to have autopilot automatically write out its config overrides to preserve them, so it should “just work” now.

[Evanito]

Autopilot.js not maintaining arguments is a known missing feature at the moment, to my understanding 😅