-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Use mission default" should be the default mission conditon #170
Comments
As noted in comment on #172, while Weather and Time parameters use the "Use mission setting/s" phrasing, Fog and Wind parameters call it "Use default" instead. The actual issue (using the mission setting by default) was correctly fixed by PR 172, this is just a string issue. |
@shadow-fa Could you fix the inconsistent strings? Probably changing all to using "Use mission setting" |
Done in #180 |
Looks like f_param_fog and f_param_wind in description.ext use a hard coded "Use default" rather than the stringtable "Use mission setting". These should be changed to reference the stringtable. |
Done in #180 |
Confirmed correct in 3.5.2 test mission. |
For a number of the mission condition parameters in description.ext, the default value is something other than "Use mission default". This should be changed so that the mission conditions module does not override the editor settings unless a missionmaker or host changes the parameter
The text was updated successfully, but these errors were encountered: