Missions, Assignments, & Events - Revision history

Dan: Dan moved page Missions, Assignments & Events to Missions, Assignments, & Events

2025-08-26T09:49:11Z

Dan moved page Missions, Assignments & Events to Missions, Assignments, & Events

← Older revision	Revision as of 02:49, 26 August 2025
(No difference)

Dan: /* Complexity */

2018-02-02T14:47:57Z

Complexity

← Older revision		Revision as of 07:47, 2 February 2018
Line 12:		Line 12:

	==Complexity==		==Complexity==
	Missions and Events tend to be described by the level of complexity of the associated task or incident, of ~~whih~~ there are five levels:		Missions and Events tend to be described by the level of complexity of the associated task or incident, of which there are five levels:

	* Simple		* Simple

Dan: /* Monthly Orders */

2018-01-24T01:52:39Z

Monthly Orders

← Older revision		Revision as of 18:52, 23 January 2018
Line 23:		Line 23:

	==Monthly Orders==		==Monthly Orders==
	How ships receive ~~missions~~ and ~~assignments~~ and how they encounter Events are handled both by the campaign master and in-character. Missions are received or generated by the sector authority, with any otherwise untasked ships receiving assignments, if they are available to receive them. Events, however, occur randomly. The campaign procedure for determining the number of available Missions, Assignments, and Events, however are provided here.		How ships receive Missions and Assignments and how they encounter Events are handled both by the campaign master and in-character. Missions are received or generated by the sector authority, with any otherwise untasked ships receiving assignments, if they are available to receive them. Events, however, occur randomly. The campaign procedure for determining the number of available Missions, Assignments, and Events, however are provided here.

	Each month, the number of commissioned ships (line and auxiliary) within the authority of the sector (or other) command is divided by 12 and then multiplied by the results of a percentage (i.e., 1d100) roll to determine the number of missions that sector command received from higher authority or generated for the management of the given sector itself. The details of each mission are determined by following the [[Random Missions]] rules. From there, the authority determines which ships are both appropriate and available to be assigned the mission and provides the details to them. The ship then warps off to complete the task.		Each month, the number of commissioned ships (line and auxiliary) within the authority of the sector (or other) command is divided by 12 and then multiplied by the results of a percentage (i.e., 1d100) roll to determine the number of missions that sector command received from higher authority or generated for the management of the given sector itself. The details of each mission are determined by following the [[Random Missions]] rules. From there, the authority determines which ships are both appropriate and available to be assigned the mission and provides the details to them. The ship then warps off to complete the task.

Dan: /* Complexity */

2018-01-23T17:04:43Z

Complexity

← Older revision		Revision as of 10:04, 23 January 2018
Line 20:		Line 20:
	* Extreme		* Extreme

	~~Events have two potential Ship Mission skill rolls to~~ be ~~made~~, in ~~order~~ to ~~be resolved~~. The ~~first~~ is the ~~'''Mission Task''' roll and~~ a ~~successful~~ roll ~~here ends~~ the mission ~~on a completely positive note (though~~ [[~~Starfleet Command:Skills\|Skill points~~]] ~~can~~ be ~~awarded~~ for missions ~~that are rated~~ as ~~Challenging~~ or ~~higher~~). ~~If a Mission Task roll fails~~, ~~then a~~ '''~~Mission Failure~~'~~'' has occurred~~ and ~~damage has been potentially received~~. ~~After~~ the ~~initial damage rolls~~ are ~~made, a second Ship Mission skill roll is made, to see how~~ the ~~commanding officer~~ and ~~crew handled~~ the ~~sudden~~ and ~~unexpected damage~~. ~~If they pass~~, they ~~handled~~ the ~~emergency well~~, ~~and no further damage~~ is ~~taken; however~~, ~~if they fail this second roll, their lack of preparedness has resulted in additional damage to~~ the ~~ship~~.		Assignments are generally assigned with the presumption that the tasking will either be Simple or Routine in nature, with little chance of increasing complexity. However, ships both on missions and assignments may encounter an unplanned Event that provides an incident with a complexity completely unrelated to the tasking.

			==Monthly Orders==
			How ships receive missions and assignments and how they encounter Events are handled both by the campaign master and in-character. Missions are received or generated by the sector authority, with any otherwise untasked ships receiving assignments, if they are available to receive them. Events, however, occur randomly. The campaign procedure for determining the number of available Missions, Assignments, and Events, however are provided here.

			Each month, the number of commissioned ships (line and auxiliary) within the authority of the sector (or other) command is divided by 12 and then multiplied by the results of a percentage (i.e., 1d100) roll to determine the number of missions that sector command received from higher authority or generated for the management of the given sector itself. The details of each mission are determined by following the [[Random Missions]] rules. From there, the authority determines which ships are both appropriate and available to be assigned the mission and provides the details to them. The ship then warps off to complete the task.

			All other ships that are both available for operations but otherwise untasked are generally provided low-priority assignments, items that were on the sector authority's issues to complete, but were low key, open-ended, or "nice to haves." Therefore, ships presently on missions or engaged in some other requirement (such as a maintenance period or port call) would not receive assignment orders. The sector authority considers each assignment-available ship when looking at the low-priority assignments list (as seen with the [[Random Assignments]] rules), as tasks the ships with the most appropriate ones. Note: assignments ''can'' be interrupted by missions, if the need is great enough.

			All ships, however, are susceptible to having to deal with an Event, as these are unplanned (and often undefined, campaign-wise). Like Missions, the number of Events are determined by the number of commissioned ships (line and auxiliary) within the authority of the sector command divided by 12 and multiplied by the results of a percentage roll. However, before they are hoisted into the subjected ships, the level of the complexity of each Event is first determined, per the [[Random Events]] rules.


	[[Category: Rules]]		[[Category: Rules]]

Dan at 16:29, 23 January 2018

2018-01-23T16:29:37Z

← Older revision		Revision as of 09:29, 23 January 2018
Line 7:		Line 7:
	; [[Random Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority		; [[Random Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority

	; [[Random Events\|Events]]: An ~~occurrence or encounter~~ that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.		; [[Random Events\|Events]]: An incident that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.

	Missions represent taskings from higher authority that have associated prioritization and immediacy, ~~while assignments~~ are generally given to starships when there is no pressing mission objective for that ship. Assignments often incorporate low-priority and/or no specific deadline goals for the immediate authority within the sector, and are generally considered to be Simple or Routine in complexity ~~(see [[Missions,_Assignments_%26_Events#Complexity\|below]])~~. Events, however, tend to be unplanned and represent occurrences or encounters with which an individual ship (or maybe formation) must deal before completing the overall mission/assignment. (''Most episodes in the ''Star Trek'' canon represent Events that occur to the heroes.'')		Missions represent taskings from higher authority that have associated prioritization and immediacy, and run the gamut of complexity from Simple to Challenging, with some considered Difficult (see [[Missions,_Assignments_%26_Events#Complexity\|below]]). Assignments are generally given to starships when there is no pressing mission objective for that ship. Assignments often incorporate low-priority and/or no specific deadline goals for the immediate authority within the sector, and are generally considered to be Simple or Routine in complexity. Events, however, tend to be unplanned and represent occurrences or encounters with which an individual ship (or maybe formation) must deal before completing the overall mission/assignment. They also have a much higher chance of having demands and results associated with the Difficult and Extreme complexities. (''Most episodes in the ''Star Trek'' canon represent Events that occur to the heroes.'')

	==Complexity==		==Complexity==
	~~An '''Event''' is defined as an incident that could conceivably result in the ship's destruction, if not successfully completed. Generally, these~~ Events ~~are not defined any further than this, though they can~~ be~~. Events are~~ described ~~as one~~ of five levels ~~of complexity~~:		Missions and Events tend to be described by the level of complexity of the associated task or incident, of whih there are five levels:

	* Simple		* Simple
	* Routine		* Routine

Dan at 16:18, 23 January 2018

2018-01-23T16:18:25Z

← Older revision		Revision as of 09:18, 23 January 2018
Line 9:		Line 9:
	; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.		; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.

	Missions represent taskings from higher authority that have associated prioritization and immediacy, while assignments are generally given to starships when there is no pressing mission objective for that ship. Assignments often incorporate low-priority and/or no specific deadline goals for the immediate authority within the sector, and are generally considered to be Simple or Routine in complexity (see below). Events, however, tend to be unplanned and represent occurrences or encounters with which an individual ship (or maybe formation) must deal before completing the overall mission/assignment. (''Most episodes in the ''Star Trek'' canon represent Events that occur to the heroes.'')		Missions represent taskings from higher authority that have associated prioritization and immediacy, while assignments are generally given to starships when there is no pressing mission objective for that ship. Assignments often incorporate low-priority and/or no specific deadline goals for the immediate authority within the sector, and are generally considered to be Simple or Routine in complexity (see [[Missions,_Assignments_%26_Events#Complexity\|below]]). Events, however, tend to be unplanned and represent occurrences or encounters with which an individual ship (or maybe formation) must deal before completing the overall mission/assignment. (''Most episodes in the ''Star Trek'' canon represent Events that occur to the heroes.'')

	==Complexity==		==Complexity==

Dan at 16:16, 23 January 2018

2018-01-23T16:16:54Z

← Older revision		Revision as of 09:16, 23 January 2018
Line 1:		Line 1:
	__toc__		__toc__
	Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority
			Each month, the ships within a particular sector (or other area of operations) receive and carry out missions and assignments from higher authority, and deal with events that they may be drawn into. For the purposes of these rules, the following distinctions are explained:

			; [[Random Missions\|Mission]]: A prioritized objective to which one or more ships (or other units) are given to accomplish.

			; [[Random Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority

	; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.		; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.

Dan at 16:15, 23 January 2018

2018-01-23T16:15:56Z

← Older revision		Revision as of 09:15, 23 January 2018
Line 1:		Line 1:
	Each month, the ships within a particular sector (or other area of operations) receive and carry out missions and assignments from higher authority, and deal with events that they may be drawn into. For the purposes of these rules, the following distinctions are explained:		__toc__
			Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority
	~~; [[Random Missions\|Mission]]: A prioritized objective to which one or more ships (or other units) are given to accomplish.~~

	~~; [[Random~~ Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority

	; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.		; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.

Dan at 16:15, 23 January 2018

2018-01-23T16:15:33Z

← Older revision		Revision as of 09:15, 23 January 2018
Line 1:		Line 1:
			Each month, the ships within a particular sector (or other area of operations) receive and carry out missions and assignments from higher authority, and deal with events that they may be drawn into. For the purposes of these rules, the following distinctions are explained:

			; [[Random Missions\|Mission]]: A prioritized objective to which one or more ships (or other units) are given to accomplish.

			; [[Random Assignments\|Assignment]]: A tasking that tends to be more open-ended than a specific mission (such as patrolling low-threat areas), and generally represents a lower priority to the overall authority

			; [[Random Events\|Events]]: An occurrence or encounter that may or may not have been anticipated in a given mission or assignment, but one in which the ship must resolve.

			Missions represent taskings from higher authority that have associated prioritization and immediacy, while assignments are generally given to starships when there is no pressing mission objective for that ship. Assignments often incorporate low-priority and/or no specific deadline goals for the immediate authority within the sector, and are generally considered to be Simple or Routine in complexity (see below). Events, however, tend to be unplanned and represent occurrences or encounters with which an individual ship (or maybe formation) must deal before completing the overall mission/assignment. (''Most episodes in the ''Star Trek'' canon represent Events that occur to the heroes.'')

			==Complexity==
			An '''Event''' is defined as an incident that could conceivably result in the ship's destruction, if not successfully completed. Generally, these Events are not defined any further than this, though they can be. Events are described as one of five levels of complexity:
			* Simple
			* Routine
			* Challenging
			* Difficult
			* Extreme

			Events have two potential Ship Mission skill rolls to be made, in order to be resolved. The first is the '''Mission Task''' roll and a successful roll here ends the mission on a completely positive note (though [[Starfleet Command:Skills\|Skill points]] can be awarded for missions that are rated as Challenging or higher). If a Mission Task roll fails, then a '''Mission Failure''' has occurred and damage has been potentially received. After the initial damage rolls are made, a second Ship Mission skill roll is made, to see how the commanding officer and crew handled the sudden and unexpected damage. If they pass, they handled the emergency well, and no further damage is taken; however, if they fail this second roll, their lack of preparedness has resulted in additional damage to the ship.


	[[Category: Rules]]		[[Category: Rules]]

Dan: created

2018-01-23T15:56:06Z

created

New page

[[Category: Rules]]