User Tools

Site Tools


modding:missions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
modding:missions [2021/04/27 18:11] – ↷ Links adapted because of a move operation hemacastmodding:missions [2021/05/03 05:33] 24.239.107.14
Line 23: Line 23:
 ===== Objectives ===== ===== Objectives =====
  
-Add objectives to track mission progress. Use the End Mission When Objectives Complete checkbox in the General Menu to choose if the mission ends when all objectives are complete+Add [[modding:objectives|objectives]] to track mission progress. Use the End Mission When Objectives Complete checkbox in the General Menu to choose if the mission ends when all objectives are complete.
- +
-**Name** The name of the objective as displayed in the objectives list on the comms screen. +
- +
-**Group** The grouping of objectives inside the objectives list. This is used for organization. +
- +
-**Rank** Choose between a primary mission objective and an optional objective. +
- +
-**Type** The type of check required to mark the mission as complete. +
- +
-  * **Open** An objective that must be marked complete by an Event. +
-  * **Commodity** An objective +
-  * **Objects Destroyed** An objective +
-  * **Objects Hailed**  +
-  * **Objects Scanned**  +
-  * **Objects Survived**  +
-  * **Timed**  +
- +
- +
-**Tags** The variable used to check the type against.  +
-//example: Type:"Objects Destroyed" Tags:"Darts" where "Darts" refer to the tag assigned in the object screen or spawning action.// +
- +
-**Description** The description displayed when an objective is clicked on the Comms Console. +
- +
-**Visible?** If this is checked the mission will be visible on the Comms Console. If unchecked it will not be visible. Visibility can be changed through an Event or Dialog Action.+
  
 ===== Comm Channels ===== ===== Comm Channels =====
Line 55: Line 31:
 ===== Objects ===== ===== Objects =====
  
-The creation of an object will spawn the object at the launch of the mission. This is not to be confused with the spawn of an object through Event Actions and Dialog Actions, which are currently more limited.+The creation of an [[modding:add_object|object]] will spawn the object at the launch of the mission. This is not to be confused with the spawn of an object through Event Actions and Dialog Actions, which are currently more limited.
  
 **General** **General**
Line 61: Line 37:
   * **Description** Is displayed only for the GM in the GM screen.   * **Description** Is displayed only for the GM in the GM screen.
   * **Designation** The ship's hull number.   * **Designation** The ship's hull number.
-  * **Faction** The ships faction alignment. None will make the ship show as neutral.+  * **Faction** The ship'faction alignment. None will make the ship show as neutral.
   * **Class** The ship class, which affects the 3D model and base component setup.   * **Class** The ship class, which affects the 3D model and base component setup.
   * **Tags** These tags are alternative references to the object. Names must be unique but tags can be shared by multiple objects.   * **Tags** These tags are alternative references to the object. Names must be unique but tags can be shared by multiple objects.
Line 87: Line 63:
   * **Links To** The ID of another Dialog Group that will be triggered after the activation of the current dialog group.   * **Links To** The ID of another Dialog Group that will be triggered after the activation of the current dialog group.
   * **Text** The text sent from the NPC to the Player when this topic is triggered.   * **Text** The text sent from the NPC to the Player when this topic is triggered.
-  * **Topics** The text responses available to the Player which can trigger the NPC.+  * **Topics** The text responses available to the Player that can trigger the NPC.
   * → **Type** Sets the type of message being sent.   * → **Type** Sets the type of message being sent.
   * → **ID** The ID of the topic.   * → **ID** The ID of the topic.
Line 96: Line 72:
  
 **Tasks** **Tasks**
 +Object tasks are orders that are executed in the order that they are assigned. These actions currently include:
 +  * **Type** The type of task that will be added to the task queue.
 +  * → **Idle** Order the object to stand down.
 +  * → **Go To** Order the object to set course for a waypoint.
 +  * → **Patrol** Order the object to patrol the current planetary system and attack enemies.
 +  * → **Evade** Order the object to evade enemies in the current planetary system.
 +  * → **Attack** Order the object to attack a specific target or tag.
 +  * → **Defend** Order the object to defend a specific target or tag.
 +  * → **Investigate** Order the object to move to and assess a specific target or tag.
 +  * → **Trade** Order the object to attempt trade with a specific target or tag. //(This Task is a work in progress.)//
 +  * **Tags** The target parameter of the Type command.
 +  * **Clear On Complete?** Check this box to clear this task from the task queue once it is completed. If unchecked, the task will remain in the queue unless canceled by an action.
  
 **Properties** **Properties**
 +These object properties set or override specific parameters normally set by the ship class.
 +  * **Type** The type of property to set or override.
 +  * → **Alert** 
 +  * → **Behavior** The current active behavior for the object.
 +  * → **CoreBehavior** The default behavior for the object.
 +  * → **Dialog** 
 +  * → **Dialog [Group]** 
 +  * → **Integrity** 
 +  * → **Integrity [Relative]**
 +  * → **Manuver**
 +  * → **Planet** The planetary system where the object is currently located.
 +  * → **Position** The x,y,z position within the system where the object is currently located. 
 +  * → **Star Position** 
 +  * → **Galatic Position**
 +  * → **Speed**
 +  * → **Speed [Target]**
 +  * **Value** The new value for the selected Type.
  
 ===== Encounters ===== ===== Encounters =====
  
 +[[modding:encounters|Encounters]] are events that activate on set intervals. These are akin to random monster spawns. GMs have the ability to adjust the likelihood and other details of the spawn.
  
  
 ===== Events ===== ===== Events =====
  
 +[[modding:events|Events]] are powerful IF-THEN statements that allow mission designers to manipulate the world of the mission when specific conditions are met.
  
 ===== Variables ===== ===== Variables =====
  
 +[[modding:variables|Variables]] are numerical strings that store information that may be checked or edited later. 
  
 +  * **Name** The name of the variable. This is used to check using conditions or edit using actions. This name is also shown inside of Designer and the GM screen.
 +  * **Type** Currently, only numerical string values are supported. 
 +  * **Value** The initial value of the variable when the mission starts.
  
 ===== Waypoints ===== ===== Waypoints =====
  
 +[[modding:waypoints|Waypoints]] are named points in space that the Flight console can target and jump to.
  
 +**Add a waypoint**
 +  * **Name** The name of the waypoint that appears in the Flight Screen's waypoint menu.
 +  * **Description** The description of the waypoint that appears below the waypoint name in the Flight Screen's waypoint menu.
 +  * **Type** The only type available at the moment is Planet.
 +  * **Target** The planet that the waypoint is referencing.
  
 ===== Scripting ===== ===== Scripting =====
  
 +The scripting section allows for custom scripts written in C#.
  
modding/missions.txt · Last modified: 2022/01/25 23:01 by hemacast