[x] In A.1, the description of cp_passenger_window_[1|2]_[l|r]_lock incorrectly states that "windows are always locked by default in newly-spawned user-controlled vehicles". Now, that was the intent indeed, but never materialized, due to there not being a convenient mouse event available for users to unlock the windows when so desired.
[x] In A.2., the descriptions of the values assignable to lights_cti_int_lights_level_2_requires_running_engine are erroneously inverted, i.e., the constraints on the function are laxer when the value is set to 0 than when it is set to 1.
[x] On title page and D.10, prolong 1.5.1 development end from February to March.
cp_passenger_window_[1|2]_[l|r]_lockincorrectly states that "windows are always locked by default in newly-spawned user-controlled vehicles". Now, that was the intent indeed, but never materialized, due to there not being a convenient mouse event available for users to unlock the windows when so desired.lights_cti_int_lights_level_2_requires_running_engineare erroneously inverted, i.e., the constraints on the function are laxer when the value is set to 0 than when it is set to 1.