After weeks, well more like months, of work and sweat, the first build of the next version of Mission-X will be uploaded. It is not backward compatible with previous versions, but it try to retain the framework it was built on, but with the ability to execute scripts as part of the flow of the mission.
Unfortunately, many features that are present in Mission-X v2 were not implemented and might not be implemented directly into the plugin. Some can be just scripted with enough experience.
The main goal of this build, is to introduce the plugin and the new concepts in it. It will have only one mission as an example, and it won't have the scripting part demo yet, since there is some work to be done, mainly documentation.
This build demonstrate the:
- New mission packaging and file placement.
- New XML elements and syntax for mission creation.
- New UI based on the Nuklear Library*.
- New documentation (well, I know it is not a feature, but good to know).
* The Nuklear library is being used since it solved me the True Type Font implementation. My personal preference is to always use LR XPSDK even for UI and even if it won't look sexy.
This might not seem much, but since it is a complete re-write of the code, there was much effort invested in it and I hope the result will be acceptable by Mission designers.
What kind of mission can you expect to create
This alpha build aims to introduce XML mission creation. Simple "to and from" locations, with few messages.
In 75% of these missions, this kind of interaction should be enough
What about embedded scripts
I already have a demo for the embedded scripting, but I think it is too early and documentation is not ready yet (you will see what I mean if you would get the chance to read the new designer guide).
In the future build, I will add embedded examples to the demo mission.
My problem is mainly time and the desire to implement more features, I want to implement the 3D Object feature, which is a large component from programming side, which come at the expense of writing documentation and preparing tutorials.
I will have to decide though.
Once the alpha build will be published, if you are designer then please go over the documentation first. Take your time, and go over the mission file and the packaging rules (location of mission files and folders). The demo mission is a simple implementation of one of v2 missions.
Please do remember that this is an early bird build, so changes might take place.
Until next time