This is from a discussion on the discord channel about the problem where new users don't realize that SAS interferes with LOCK STEERING. The manual mentions it several times, but it would be better if the mod was more active about mentioning it, and trying to stop it.

This is the proposal as it stands now:

1 - If SAS is on, at the moment a LOCK STEERING command first starts, Make LOCK STEERING turn it off for you, with a short quick screen message stating it has done so. Do not bother trying to remember the state the player had SAS in. Don't bother trying to restore SAS to its previous state when the steering unlocks, because the player could have toggled it while steering was locked and that's a PITA to track.

2 - During the time that LOCK STEERING is in effect have SteeringManger keep checking the SAS state. If the SAS gets turned on again (by script or by the player's manual action), allow it to do so, but do issue a screen message about it so the player understands why they're seeing the steering go all haywire. The message could be something like "SAS and kOS STEERING are fighting!". Have it fade on and off while the state is happening (repeat the message every X seconds, with a fade-out of X-1 seconds).
If the SAS is only turned on momentarily for a few ticks, then turned back off again by script, then the message should not show. To accomplish this have some kind of timer that only starts the message after the state of SAS & LOCK STEERING has been happening for a second or so.