Matrix Games Forums

ORIGINAL: orca

a way to make it easier to add to magazine by:

-a way to directly add weapons to the units magazine when selecting the appropriate weapon in the weapons window for that unit (the same window that allows add/remove weapon mount). Maybe create another option at the bottom of that window to "add to magazine".

-similar feature to be used when readying an aircraft to add the displayed load out details to the magazine of the ship/facility that aircraft is located

ORIGINAL: DeSade


I would love to be able to designate landed aircrafts as strike mission targets. Workaround (launching them, assigning and landing) is very cumbersome when scenario is in advanced stage. Maybe assigning targets for mission from OOB screen?

As an option/alternative, possibility to define targets for strike missions by type/subtype rather then actual units.

ORIGINAL: tjhkkr

How about a LUA command
Like:

EVERY (x) Hours
Then allow it to execute a LUA command.
I am thinking in terms of weather...lest of course weather is about to get a new change... but I have a couple of other ideas as well.

ORIGINAL: stormridersp

I have three requests to my wishlist:

1- One thing that I´d like to be able to do is to edit the AI files. I assume that Command´s AI files are hardcoded and impossible to edit. It would be cool if they were ini files, the sorts of sonalysts´, like for example, Submarines_Defensive.ini, or Submarines_ASuW and so on.

2-To have chained missions assigned to waypoints and/or dependent on conditions, like the picture below:



3- An option to turn on/off COMMs dependency on depth/altitude or other factors, between Sides. For example:

OOB:
Side 1 (Player), Side 2 (AI) and Side 3 (AI); are all Allieds.
Side 1 has 1 SSN
Side 2 has a Land bases (HQ), SAGs, Air Force, Army...
Side 3 has 1 SSBN

COMMS:
Side 1 can only communicate with Side 2 above Shallow. Side 1 can communicate with other Side 1 members freely.
Side 3 can only communicate with Side 2 above Periscope Depth. Side 3 can communicate with other Side 3 members freely.
Side 1 and 3 can trasmit comms when above their respective Comms´ depths, but will only receive when above the their assigned depths, that is, Side 3 is just above the layer, while Side 1 is just above it. At waypoint 3, Side 1 flies to Shallow, so it transmits its actual picture to Side 2 and Side 3. Side 2 receives it immediately while Side 3 will only receive it at its Waypoint 2, when it goes to Periscope.

This way I can set both Side 1 and 3 Doctrines to FREE ASW, instead of TIGHT, to prevent each side from engaging non-friendlies, that is, neutrals. This mechanics, allied to the suggestion #2, would make for a more flexible and complex submarines simulation.

ORIGINAL: DeSade


I would love to be able to designate landed aircrafts as strike mission targets. Workaround (launching them, assigning and landing) is very cumbersome when scenario is in advanced stage. Maybe assigning targets for mission from OOB screen?

As an option/alternative, possibility to define targets for strike missions by type/subtype rather then actual units.

ORIGINAL: emsoy

We've added "Doctrine option: Ignore Bingo fuel." in v1.11 so removed from list [8D]

ORIGINAL: Primarchx

ORIGINAL: emsoy

We've added "Doctrine option: Ignore Bingo fuel." in v1.11 so removed from list [8D]

Wow! With the tanker mission improvements this will do a lot to deconflict long-range air operations (if config'd correctly by the scen editor and/or player). Nothing worse than rolling onto a target at the bleeding edge of Bingo to have your a/c RTB because of fuel state (especially when you have tankers waiting for them on egress). This is awesome!

ORIGINAL: Mgellis

An idea...

Would it be possible to update the Event Editor so that some of the more common lua actions are now automated/menu-based (e.g., the way teleporting a unit is) rather than code-based? Things like changing the weather, adding units, having an explosion go off at a certain location, deleting units, killing units, and anything else where it might make sense to set things up this way. You could still use the lua code if you wanted, but there would also be separate items in the Action menu that would let people do it without coding. It would just make things a little easier for scenario designers who, like myself, are a little on the coding-impaired side. [:)]

Thanks for considering this.