MIssion Scripting Tools (Mist) - feature request list

[chromium]

Hi all,

 

this thread is created in the purpose of feed Speed & Grimes of "script logic ideas" to be integrated in the MIST.

 

For MIST information, download and updates please refer to the official Speed's topic here:

http://forums.eagle.ru/showpost.php?p=1622303&postcount=1

 

This thread will likely be monitored by Grimes and Speed to see which wanted feature could be converted in editable script and used in the sim.

 

For clarification about how it works, "not work" communications or anything else it could be better to answer on the original thread: as much as we keep on topic here, as much it will be easily readable by them.

[chromium]

[iD 1] - Indirect fire support by signal rockets

 

Here I am with my first idea (I have to say that I do not check if it's already possible by first release, but I'm in the hurry to insert the first one as an example. Maybe simply tell me "it's already possible :p ):

 

The wanted behaviour is to direct arty fire in the middle spot of a signal rocket salvo.

 

I thought it in 2 phases:

 

A- one script that activate a flag on a text command (slmod.chat_cmd like)

B- one script that "add" a fire-at-point task at the arty ("a" table units) to vec3 coordinates of the average hitting point of the signalling rockets last fired salvo by someone ("b" table units). Arty firing should be customizable in firing minutes & range. The firing action should be on hold since a flag is activated.

 

The operation layout could be:

 

- At mission star script "A" and "B" are loaded;

- I spot the enemy, lock and fire a signal salvo;

- the script "B", create the task to fire at point for the signal rockets hits coordinates but hold the fire;

- I decide to start fire, so I type "fire" in the chat and by script "A" will turn on the flag "n"

- The flag "n", present in the "B" script, release the fire action.

 

Obviuosly workarounds for the probably impossible "hold fire" command are welcome.

Edited December 5, 2012 by chromium

[Speed]

Mission Lua scripts can't detect chat, but it should be possible to direct artillery fire (or AI aircraft) with smoke rockets- the only obstacle is whether Unit.getTypeName will work on smoke rockets... I THINK it does. If not, a fix might come in a patch.

 

Because mission Lua scripts can't detect chat, what about this:

Every time you put down a smoke rocket, its impact position is stored in memory and a timer begins. Every subsequent smoke rocket impact overwrites that position, and resets that timer. If the timer reaches like, 90 seconds, only THEN does the attack command (with the position of the last impacting smoke rocket) get sent to the AI. This would allow you some time to get the smoke mark correct before the AI tried to attack it.

 

Who knows, it might also be that one day, mission scripts can detect chat and then the above logic is no longer necessary.

 

Anyway, other weapons tracking functions would be a higher priority than this smoke marking script- I would probably need to include mist.weaponsShotBy, mist.flagFunc.weapons_shot_by, etc. And I would want to port all the Slmod weapons_impacting_in_zone functions in to Mist too. After all that, then we might get to smoke rockets for marking targets...

Edited December 5, 2012 by Speed

[chromium]

I know that every time I suggest something it will be challenging :p

[chromium]

Proposed workaround:

 

Is there another way to direct filre to "x" location not using CA? All other things are possibly done by SLmod and trigger system.