MarkJFox: 3 revisions imported

2025-03-31T19:59:32Z

3 revisions imported

← Older revision	Revision as of 21:59, 31 March 2025
(No difference)

en>Crimsonum at 17:47, 8 June 2023

2023-06-08T17:47:57Z

← Older revision		Revision as of 19:47, 8 June 2023
Line 208:		Line 208:
	\|{{N}}		\|{{N}}
	\|{{Y}}		\|{{Y}}
	\|~~Function unknown~~.		\|Used by units when entering a [[Grinding\|grinder]].
	\|}		\|}

en>Crimsonum: Updated

2023-06-08T15:33:27Z

Updated

Show changes

en>Nighthawk200: Well, since it was absent...

2008-06-14T16:21:39Z

Well, since it was absent...

New page

This section in <tt>[[rulesmd.ini|rules(md).ini]]</tt> specified behavioural characteristics of objects engaged in missions. These 'missions' are not singleplayer campaign missions or anything like that. A mission in this sense is something like 'Attack', or 'Area Guard' or 'Harvest'. Something that the computer performs automatically.

Most mission behaviour is hardcoded into the EXE file, but a few values can be overridden in each mission's section in the <tt>[[rulesmd.ini|rules(md).ini]]</tt> file.

New missions cannot be added, and conversely you should not remove any either. There are quite a few within the section, some are unused. Some new missions have been added in {{ra2}} and {{yr}}. This has been noted in the table. Here are all missions contained within the Mission Control section, in the order they appear in the INI:

{| align="center" cellpadding="4" class="table_descrowdesccol"
!<b>Mission Name</b>
!<b>Function / Objective</b>
|-
|Sleep
|Unit basically plays dead.
|-
|Harmless
|Unit will not return fire, and is not considered a threat by the AI.
|-
|Sticky
|Operates like Guard mode, but the unit will not move from its current location.
|-
|Attack
|Attack mission used by team logic.
|-
|Move
|Move to a destination. Simple as that.
|-
|Patrol
|Patrol a series of waypoints. Used by units in a waypoint loop.
|-
|QMove
|Queued Move. Similar to move, but only used when all other queued moves have been carried out.
|-
|Retreat
|Run away. The INI states that the unit may leave the map too.
|-
|Guard
|Engage any enemy that enters weapons range. The defending unit may follow the aggressor.
|-
|Enter
|Enter a building or transport.
|-
|Eaten [[Image:ra2small.png]]{{yro}}
|Function unknown.
|-
|Capture
|Mission used whenever an Engineer unit enters something.
|-
|Harvest
|Automatic mission used by harvester units. Collect ore, dump it, repeat.
|-
|Area Guard
|Guard the general area around the unit.
|-
|Return
|An unused mission.
|-
|Stop
|Halt! Basically, the unit will cease firing and moving whenever it can.
|-
|Ambush
|An unused mission.
|-
|Hunt
|Seek out and attack enemy units.
|-
|Unload
|Unloading cargo, e.g. an APC unloading passengers.
|-
|Sabotage
|C4 mission.
|-
|Construction
|Mission used by buildings when they are initially placed.
|-
|Selling
|Mission used by buildings during deconstruction, i.e. when they're sold.
|-
|Repair
|Used by the Service Depot to repair the docked unit.
|-
|Rescue
|A special override mission. Perhaps used if a critical unit is in danger.
|-
|Missile
|Used by a Nuke Silo when it is firing.
|-
|Open
|Gate structure operation.
|}
[[Category:Rules(md).ini Sections]]

Mission Control - Revision history

MarkJFox: 3 revisions imported

en>Crimsonum at 17:47, 8 June 2023

en>Crimsonum: Updated

en>Nighthawk200: Well, since it was absent...