So why am I sharing this, or why am I exited (you probably ask yourself, or not). Well, today I reached the load/save/new milestone.
What is it all about, In short:
load = allow you to open a valid mission file.
save = saves your work to disk.
new = Create a skeleton mission file where you can add your mission steps and definitions.
So yes, I'm exited, it is like closing the mandatory "work cycle" of every mission. You can open your work, save it or start a new one. This is also translates to an editor that can allow you define a basic mission with ~30% of features implemented, which is not bad at this stage.
Lets see what was implemented:
- Full work cycle - Load, Save, New or L.S.N in short (I just made it up).
- Briefer and global settings - date, map, designer flag and custom directory names.
- Steps - Add or remove steps.
- Step Goals - Add/Remove goals, currently implemented: static and area goals (limited to 5 per step).
- Step Triggers - Currently supports only "trigger_zone" type. You can choose between "rad" or "poly" areas and also define events.
- Step Settings - Step description, map, feedback messages and payload.
This might not sound much, but it is the core of every mission.
I hope that in the near future, I'll be able to publish my first public build, but first I'll have to finish implementing last few options and create at least one short mission with it, in order to have better understanding of the workflow and QA it a bit more.