Update not pushed live at time of update due to a few bugs. Wanted to get commit in. Fixed typo with mist.utils.NMToMeters causing function not to work. added Logger 'dbLog' to mist DB code inserted do-end blocks to make DB code block shorter in length Purpose of DB updating refactor is to more accurately keep unit tables updated correctly. In the old system only 'byName' DBs were updated if a group/unit name was duplicated. So it was possible for multiple units to share the same name in unitsByNum, byCat, etc. The process of how it checks added groups and units has been altered slightly. Groups spawned with player controlled units will not be updated. The conditions for whether or not the table gets updated are as follows: If groupName is already in DB then check if its groupId, country, or coalition changed. If nothing has changed then it checks if the newly spawned units exist in a DB entry and if so it will verify if the unitId ort ype have changed. Any single update prompts the DB to update accordingly.
Mission Scripting Tools
Mission Scripting Tools for Digital Combat Simulator
Authors: Grimes (mrSkortch), Speed
Forum Thread: http://forums.eagle.ru/showthread.php?t=98616
Documentation
The MIST Wiki page can be fore at this address: http://wiki.hoggit.us/view/Mission_Scripting_Tools_Documentation
The attached pdf "mist gude.pdf" is attached in the download.
Description
MIssion Scripting Tools (Mist) is a collection of Lua functions and databases that is intended to be a supplement to the standard Lua functions included in the simulator scripting engine. Mist functions and databases provide ready-made solutions to many common scripting tasks and challenges, enabling easier scripting and saving mission scripters time. The table mist.flagFuncs contains a set of Lua functions (that are similar to Slmod functions) that do not require detailed Lua knowledge to use. However, the majority of Mist does require knowledge of the Lua language, and, if you are going to utilize these components of Mist, it is necessary that you read the Simulator Scripting Engine guide on the official ED wiki
Contribution Guide
Contributions can be made with a standard github pull request model. Code developed for the next release should be requested to be pulled into the "develop" branch. Pull requests not targetted for "develop" will be denied. For hotfixes please open a ticket describing the problem and ideally a fix and your changes will be attributed in the relevant commit message. It's done like this because unfortunately github provides no tools to target to a new hotfix branch, and github tools are exclusively used in the administration of this repository and we wish to minimize the amount of unvetted code into master.