I dont want to lead anyone astray, and since the above back and forth with @Flappie DID lead us astray, I wanted to come back here and document the issue more clearly, now that we know what happened.
Problem Statement: Users were seeing tooltips on our servers, despite the Options file in the MIZ saying tips=false
In the above Track (in the very first post), there was a conflict between the two options available in the Mission Editor. If you open the track, you will see the OPTIONS file in the track lists tips=false. However, in the MISSION file under the 'forcedOptions' section, tips=true. This is the 'conflict' and post 2.8, the MISSION file forcedOptions section is now taking precedence (as it rightfully should). If you open the same track with 2.7, you'll see that the forcedOptions section for tips is not obeyed, and instead the Options file value is obeyed.
So lets better understand the OPTIONS file vs the 'forcedOptions' section in the MISSION file. First, the 'forcedOptions' section in the MISSION file is where a mission designer goes into the mission editor and selects the "ENFORCE" options and then selects a value. This will enter into the MISSION file a forcedOptions value for what you select. Notice that today in 2.8, tooltips is no longer a selectable option. 🙂
To resolve the issue, we simply updated the 'forcedOptions' section to tips=false and this has resolved our issue.
I then tried to play around with the OPTIONS file, but I still havent figured out what the OPTIONS file actually does. In 2.8 there is no way to select a value in the ME without selecting enforce first, which seems to render the Options file obsolete. I believe that the correct way to now enforce Options in your MIZ is to set 'forcedOptions' values in the MISSION file (either via the GUI that ED makes available in the Mission Editor, or by editing the MISSION file with your preferred text editor of choice.)
Hope this helps anyone else who stumbles across issues with their MIZ's in the future.
TJ
