It’s one of the great mysteries that this insanely useful piece of info is locked away behind a setting that defaults to disabled.
Perhaps this should also affect advanced tweakables?
Im not exactly sure what the best way to implement this from a usability standpoint would be, since it would be nice for a user to turn it off if they really want to. Perhaps there could be a piece of state in kspcf’s plugindata that records whether the patch has ever been run, and only runs the first time kspcf is loaded and that state is not present.
JonnyOThan
commented
2 months ago
It’s one of the great mysteries that this insanely useful piece of info is locked away behind a setting that defaults to disabled.
Perhaps this should also affect advanced tweakables?
Im not exactly sure what the best way to implement this from a usability standpoint would be, since it would be nice for a user to turn it off if they really want to. Perhaps there could be a piece of state in kspcf’s plugindata that records whether the patch has ever been run, and only runs the first time kspcf is loaded and that state is not present.