Random Events - Revision history

Dan: /* Event Test */

2026-08-31T13:17:37Z

Event Test

← Older revision		Revision as of 06:17, 31 August 2026
Line 36:		Line 36:
	:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''		:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''

	''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the "tens" digit and the second as the "ones" digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original "twin" rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)		'''Note:''' instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the "tens" digit and the second as the "ones" digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original "twin" rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)

	''Ex: A Routine Event target number (''i.e.'', the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because 6 and 6 were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a 7, making the Test roll 59 (66 - 7 = 59). If the third roll had been another 6, then a fourth roll would be conducted, for maybe a 3. The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''		:''Ex: A Routine Event target number (''i.e.'', the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because 6 and 6 were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a 7, making the Test roll 59 (66 - 7 = 59). If the third roll had been another 6, then a fourth roll would be conducted, for maybe a 3. The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''

	==Event Failures==		==Event Failures==

Dan: /* Event Test */

2026-08-31T13:17:02Z

Event Test

← Older revision		Revision as of 06:17, 31 August 2026
Line 36:		Line 36:
	:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''		:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''

	''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the 'tens' digit and the second as the 'ones' digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original 'twin' rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)~~<br>~~''Ex: A Routine Event target number (i.e., the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because '6' and '6' were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a '7,' making the Test roll 59 (66 - 7 = 59). If the third roll had been another '6,' then a fourth roll would be conducted, for maybe a '3.' The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''		''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the "tens" digit and the second as the "ones" digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original "twin" rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)

			''Ex: A Routine Event target number (''i.e.'', the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because 6 and 6 were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a 7, making the Test roll 59 (66 - 7 = 59). If the third roll had been another 6, then a fourth roll would be conducted, for maybe a 3. The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''

	==Event Failures==		==Event Failures==

Dan: /* Event Failures */

2024-12-17T19:23:45Z

Event Failures

← Older revision		Revision as of 12:23, 17 December 2024
Line 150:		Line 150:

	* Note: For Catastrophic, any roll of 100% or greater results in automatic destruction, with the loss of all hands, as does any damage that equals or exceeds the ship's Total SU value.		* Note: For Catastrophic, any roll of 100% or greater results in automatic destruction, with the loss of all hands, as does any damage that equals or exceeds the ship's Total SU value.
	* To apply damage to a ship, see the [[~~Starfleet Command:Damage\|~~Damage]] rules.		* To apply damage to a ship, see the [[Damage]] rules.


	[[Category:Missions, Assignments & Events\|{{PAGENAME}}]]		[[Category:Missions, Assignments & Events\|{{PAGENAME}}]]

Dan: /* Event Test */

2018-01-23T18:20:36Z

Event Test

← Older revision		Revision as of 11:20, 23 January 2018
Line 19:		Line 19:

	==Event Test==		==Event Test==
	To see if the ship and its crew passes an Event, a Test roll is made. A successful roll results in the success of both the Event and the survival of the ship (and its crew), with no further rolls necessary. If the first roll fails, another is made. A success in this roll indicates that although the Event was not perfectly resolved, the ship survived, albeit with a chance of damage to the ship and casualties to the crew (see below). A failure of the second roll results in the complete destruction of the ship (unless the scenario allows for an alternate result).		To see if the ship and its crew passes an Event, a Test roll is made. A successful roll results in the success of both the Event and the survival of the ship (and its crew), with no further rolls necessary. If the first roll fails, another is made. A success in this roll indicates that although the Event was not perfectly resolved, the ship survived, albeit with a chance of damage to the ship and casualties to the crew (see Event Failures below). A failure of the second roll results in the complete destruction of the ship (unless the scenario allows for an alternate result).

	* A '''Simple''' Event virtually guarantees a successful outcome. Only a Ship skill below 50 has a chance of failing this Event, as the Test roll requires the ship to pass a roll against a doubled Ship skill.		* A '''Simple''' Event virtually guarantees a successful outcome. Only a Ship skill below 50 has a chance of failing this Event, as the Test roll requires the ship to pass a roll against a doubled Ship skill.

Dan: /* Event Failures */

2018-01-23T18:20:18Z

Event Failures

← Older revision		Revision as of 11:20, 23 January 2018
Line 39:		Line 39:

	==Event Failures==		==Event Failures==
	When an initial Test roll is not passed, the ~~mission~~ is deemed a failure. Whether ~~the actual scenario~~ goals were met or not, the Event resulted in an incident that may be regarded as catastrophic (''ex: ''USS da Vinci'''s tragic loss of half the crew at [[Galvan VI]] still allowed for a successful recovery of ~~the~~ ''USS Orion'' and the Wildfire device, but ~~in the spirit of these Events,~~ it would ~~have been seen~~ as ~~a mission~~ failure''). When ~~a mission~~ failure occurs, a percentile roll is made to determine the degree of ~~mission failure~~ (minimal, marginal, major, massive, disaster or catastrophic) on the table appropriate to the level of the Event, down the '''1 Fail''' column. The captain and crew must now deal with the results of this damage. A Test roll of the unmodified Ship skill (i.e., full skill amount) is made again: if the ship passes, no further failures have occurred. If the ship fails ~~again~~, another percentile roll is made and compared against the '''~~2 Fails~~''' column, with additional damage recorded. The Damage Table is consulted twice to determine the amount of damage for both failed Test rolls (if necessary).		When an initial Test roll is not passed, the Event is deemed a failure. Whether an associated mission's or assignment's goals were met or not, the Event resulted in an incident that may be regarded as catastrophic (''ex: ''USS da Vinci'''s tragic loss of half the crew at [[Galvan VI]] still allowed for a mission success with the successful recovery of ''USS Orion'' and the Wildfire device, but it would be graded as an Event failure''). When an Event failure occurs, a percentile roll is made to determine the degree of damage (minimal, marginal, major, massive, disaster or catastrophic) to the ship (and crew) on the table appropriate to the level of the Event, down the '''1st Fail''' column. The captain and crew must now deal with the results of this damage. A Test roll of the ''unmodified'' Ship skill (i.e., full skill amount) is made again: if the ship passes, no further failures have occurred and no additional damage is incurred. If the ship fails this last Test roll, another percentile roll is made and compared against the '''2nd Fail''' column, with additional damage recorded. The Damage Table is consulted twice to determine the amount of damage for both failed Test rolls (if necessary).


Line 149:		Line 149:
	\|}		\|}

	* Note: For Catastrophic, any roll 100% or greater results in automatic destruction, with the loss of all hands, as does any damage that equals or exceeds the ship's Total SU value.		* Note: For Catastrophic, any roll of 100% or greater results in automatic destruction, with the loss of all hands, as does any damage that equals or exceeds the ship's Total SU value.
	* To apply damage to a ship, see [[Starfleet Command:Damage\|Damage]].		* To apply damage to a ship, see the [[Starfleet Command:Damage\|Damage]] rules.



	[[Category:Missions, Assignments & Events\|{{PAGENAME}}]]		[[Category:Missions, Assignments & Events\|{{PAGENAME}}]]

Dan: /* Mission Failures */

2018-01-23T17:53:44Z

Mission Failures

← Older revision		Revision as of 10:53, 23 January 2018
Line 38:		Line 38:
	''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the 'tens' digit and the second as the 'ones' digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original 'twin' rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)<br>''Ex: A Routine Event target number (i.e., the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because '6' and '6' were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a '7,' making the Test roll 59 (66 - 7 = 59). If the third roll had been another '6,' then a fourth roll would be conducted, for maybe a '3.' The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''		''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the 'tens' digit and the second as the 'ones' digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original 'twin' rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)<br>''Ex: A Routine Event target number (i.e., the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because '6' and '6' were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a '7,' making the Test roll 59 (66 - 7 = 59). If the third roll had been another '6,' then a fourth roll would be conducted, for maybe a '3.' The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''

	==~~Mission~~ Failures==		==Event Failures==
	When an initial Test roll is not passed, the mission is deemed a failure. Whether the actual scenario goals were met or not, the Event resulted in an incident that may be regarded as catastrophic (''ex: ''USS da Vinci'''s tragic loss of half the crew at [[Galvan VI]] still allowed for a successful recovery of the ''USS Orion'' and the Wildfire device, but in the spirit of these Events, it would have been seen as a mission failure''). When a mission failure occurs, a percentile roll is made to determine the degree of mission failure (minimal, marginal, major, massive, disaster or catastrophic) on the table appropriate to the level of the Event, down the '''1 Fail''' column. The captain and crew must now deal with the results of this damage. A Test roll of the unmodified Ship skill (i.e., full skill amount) is made again: if the ship passes, no further failures have occurred. If the ship fails again, another percentile roll is made and compared against the '''2 Fails''' column, with additional damage recorded. The Damage Table is consulted twice to determine the amount of damage for both failed Test rolls (if necessary).		When an initial Test roll is not passed, the mission is deemed a failure. Whether the actual scenario goals were met or not, the Event resulted in an incident that may be regarded as catastrophic (''ex: ''USS da Vinci'''s tragic loss of half the crew at [[Galvan VI]] still allowed for a successful recovery of the ''USS Orion'' and the Wildfire device, but in the spirit of these Events, it would have been seen as a mission failure''). When a mission failure occurs, a percentile roll is made to determine the degree of mission failure (minimal, marginal, major, massive, disaster or catastrophic) on the table appropriate to the level of the Event, down the '''1 Fail''' column. The captain and crew must now deal with the results of this damage. A Test roll of the unmodified Ship skill (i.e., full skill amount) is made again: if the ship passes, no further failures have occurred. If the ship fails again, another percentile roll is made and compared against the '''2 Fails''' column, with additional damage recorded. The Damage Table is consulted twice to determine the amount of damage for both failed Test rolls (if necessary).

Dan: /* Mission Task */

2018-01-23T17:53:21Z

Mission Task

← Older revision		Revision as of 10:53, 23 January 2018
Line 18:		Line 18:
	Note: Line ships are at much greater risk of encountering Events than auxiliaries and other support vessels. When counting the number of commissioned ships (for the purpose of determining the 'subjected' ships), halve the number within each class of vessel that are ''not'' considered line (i.e., not battleships, explorers, warships, cruisers, destroyers, frigates, scouts, escorts, etc.), reducing that class' overall represented percentage. This will result in a greater number of Monthly Events falling upon the categories of ships that are engaged in risky missions. <br>''Ex: In #3 above, the ''Constitution'' class made up 7% of the starships of the sector. In the same roll, the 20 ''Arcadia'' class tankers represent 10% of the ships in the same sector, but instead only receive 5% of the Challenging Events, as their numbers were halved (from 20 to 10) when counting the number of commissioned ships.''		Note: Line ships are at much greater risk of encountering Events than auxiliaries and other support vessels. When counting the number of commissioned ships (for the purpose of determining the 'subjected' ships), halve the number within each class of vessel that are ''not'' considered line (i.e., not battleships, explorers, warships, cruisers, destroyers, frigates, scouts, escorts, etc.), reducing that class' overall represented percentage. This will result in a greater number of Monthly Events falling upon the categories of ships that are engaged in risky missions. <br>''Ex: In #3 above, the ''Constitution'' class made up 7% of the starships of the sector. In the same roll, the 20 ''Arcadia'' class tankers represent 10% of the ships in the same sector, but instead only receive 5% of the Challenging Events, as their numbers were halved (from 20 to 10) when counting the number of commissioned ships.''

	==~~Mission Task~~==		==Event Test==
	To see if the ship and its crew passes an Event, a Test roll is made. A successful roll results in the success of both the ~~mission~~ and the survival of the ship (and its crew), with no further rolls necessary. If the first roll fails, another is made. A success in this roll indicates that although the ~~mission~~ was ~~failed to be accomplished~~, the ship survived, albeit ~~there is~~ a chance of damage to the ship and casualties to the crew [see below]. A failure of the second roll results in the complete destruction of the ship (unless the scenario allows for an alternate result).		To see if the ship and its crew passes an Event, a Test roll is made. A successful roll results in the success of both the Event and the survival of the ship (and its crew), with no further rolls necessary. If the first roll fails, another is made. A success in this roll indicates that although the Event was not perfectly resolved, the ship survived, albeit with a chance of damage to the ship and casualties to the crew (see below). A failure of the second roll results in the complete destruction of the ship (unless the scenario allows for an alternate result).

	* A '''Simple''' Event virtually guarantees a successful outcome. Only a Ship skill below 50 has a chance of failing this Event, as the Test roll requires the ship to pass a roll against a doubled Ship skill.		* A '''Simple''' Event virtually guarantees a successful outcome. Only a Ship skill below 50 has a chance of failing this Event, as the Test roll requires the ship to pass a roll against a doubled Ship skill.
Line 25:		Line 25:

	* A '''Routine''' Event is nearly as easy as a Simple one, though there does exist a sizable potential for failure. The percentile is rolled versus the unmodified Ship skill.		* A '''Routine''' Event is nearly as easy as a Simple one, though there does exist a sizable potential for failure. The percentile is rolled versus the unmodified Ship skill.
	:''Ex: The Ship skill of 62 is higher than ~~the~~ percentile roll of 54, indicating a success. If the roll had been 63 or higher, the mission would have been a failure.''		:''Ex: The Ship skill of 62 is higher than a percentile roll of 54, indicating a success. If the roll had been 63 or higher, the mission would have been a failure.''

	* A '''Challenging''' Event requires a 25% reduction in the Ship skill, before the roll is made. If the percentile roll is higher than the modified Ship skill, the mission is a failure.		* A '''Challenging''' Event requires a 25% reduction in the Ship skill, before the roll is made. If the percentile roll is higher than the modified Ship skill, the mission is a failure.
Line 36:		Line 36:
	:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''		:''Ex: The Ship skill of 62 is modified as 15 (62 - 46.5 (averaged up to 47) = 15). A roll of 15 or less is required for success.''

	''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the 'tens' digit and the second as the 'ones' digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original 'twin' rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)		''Note'': instead of rolling a d100 die for the Test percentile roll, instead roll two d10s, with the first representing the 'tens' digit and the second as the 'ones' digit. If both rolls are the same (''ex: 6 and 6''), then roll a third one and subtract that from the percentile. If the third roll also equals the original 'twin' rolls, roll and subtract again (and again and again, as long as each roll is the same as the original two). The effect is to lower the percentile roll in opposition to the Ship skill. (This represents Good Luck working in favor of the crew.)<br>''Ex: A Routine Event target number (i.e., the unmodified Ship skill) is 63, but a 66 is rolled, indicating failure. However, because '6' and '6' were rolled (twin rolls), a single 1d10 is rolled, this time resulting in a '7,' making the Test roll 59 (66 - 7 = 59). If the third roll had been another '6,' then a fourth roll would be conducted, for maybe a '3.' The final Test roll in that case would be a 57 (66 - 6 - 3 = 57). In both modified rolls, the Test roll was determined to be successful.''

	==Mission Failures==		==Mission Failures==

Dan: /* Event Complexity Determination */

2018-01-23T17:32:22Z

Event Complexity Determination

← Older revision		Revision as of 10:32, 23 January 2018
Line 10:		Line 10:

	==Event Complexity Determination==		==Event Complexity Determination==
	Every month, each commissioned ship has a less than 1-in-12 chance of engaging in an Event of some level. Instead of rolling for each ship every month to see if the ship had an Event, roll 1d100% and multiply by 1/12th of the number of ~~active ships (see ''Note'' below) to determine the number of Monthly~~ Events ~~and then follow these steps:~~		Determine the number of overall Events 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 (i.e. 1d100%) roll.
	~~# Roll percentile dice four times. Each roll represents~~ the number of Events at each level, starting with Simple ones, with each following percentile roll a factor of the remaining Events. Extreme events receive the final remainder.<br>''Ex: For the month of March, 80 Monthly Events are determined to occur. The four percentile rolls are 35, 16, 86 and 19, representing the Simple, Routine, Challenging and Difficult Events. Respectively (and ~~in order~~)~~, those result in 28 Simple, 8 Routine, 38 Challenging and 1 Difficult Events, leaving 5 Extreme Events.''~~
	~~# The Simple Events can be ignored, since -in~~ the ~~majority~~ of the ~~cases- none of the Events will threaten the ship. However, they may be assigned to an individual ship, if preferred, using the below methods.~~
	~~# Routine, Challenging, Difficult~~ and ~~Extreme Events are assigned to individual ships, to have them played out via Test rolls. Determine~~ the percentage ~~for each primary class~~ (''ex: ''[[Constitution]]'' class'') within the totality of all commissioned ships (including those engaged in refits or other similar yard periods) and apply the resulting number to randomized ships within that class as experiencing that level of Event. ~~One ship can experience more than one Event per month~~. Note: Round out to the nearest whole number for the number of Events assigned to each ship class.<br>''Ex: The ''Constitution'' class of twelve ships makes up 7% of the active fleet and 38 Challenging Events have been determined to occur for the month of March. That means the ''Constitution'' class will have 3 Challenging Events (38 x 7% ~~= 2.66, rounded up to 3~~) ~~assigned to its ships~~.''

	''Note: ~~Front-line~~ ships are at much greater risk than auxiliaries and other support vessels. When counting the number of ~~active~~ ships (for the purpose of determining the ~~number of Monthly Events~~), halve the number within each class of vessel that are ''not'' considered ~~combatants or front-~~line (i.e., not battleships, explorers, warships, cruisers, destroyers, frigates, scouts, escorts, etc.), reducing that class' overall represented percentage. This will result in a greater number of Monthly Events falling upon the categories of ships that are engaged in risky missions.''		# Roll percentile dice four more times. Each roll represents the number of Events at each level, starting with Simple ones, with each following percentile roll a factor of the remaining Events. Extreme events receive the final remainder. Based on the randomization of each of these four rolls, some more complex Events may outnumber less complex ones.<br>''Ex: For the month of March, 80 Events are determined to occur. The four percentile rolls are 35, 16, 86 and 19, representing the Simple, Routine, Challenging and Difficult Events. Respectively (and in order), those result in 28 Simple, 8 Routine, 38 Challenging and 1 Difficult Events, leaving 5 Extreme Events.''
			# The Simple Events can be ignored, since-in the majority of the cases-none of the Events will threaten the ship. However, they may be assigned to an individual ship, if preferred, using the below methods.
			# Routine, Challenging, Difficult and Extreme Events are assigned to individual ships, to have them played out via Test rolls. Determine the percentage for each primary class (''ex: ''[[Constitution]]'' class'') within the totality of all commissioned ships (including those engaged in refits or other similar yard periods) and apply the resulting number to randomized ships within that class as experiencing that level of Event. One ship can experience more than one Event per month. Note: Round out to the nearest whole number for the number of Events assigned to each ship class.<br>''Ex: The ''Constitution'' class ships makes up 7% of the sector ships and 38 Challenging Events have been determined to occur for the month of March. That means the ''Constitution'' class will have 3 Challenging Events (38 x 7% = 2.66, rounded up to 3) assigned to its ships.''

			Note: Line ships are at much greater risk of encountering Events than auxiliaries and other support vessels. When counting the number of commissioned ships (for the purpose of determining the 'subjected' ships), halve the number within each class of vessel that are ''not'' considered line (i.e., not battleships, explorers, warships, cruisers, destroyers, frigates, scouts, escorts, etc.), reducing that class' overall represented percentage. This will result in a greater number of Monthly Events falling upon the categories of ships that are engaged in risky missions. <br>''Ex: In #3 above, the ''Constitution'' class made up 7% of the starships of the sector. In the same roll, the 20 ''Arcadia'' class tankers represent 10% of the ships in the same sector, but instead only receive 5% of the Challenging Events, as their numbers were halved (from 20 to 10) when counting the number of commissioned ships.''

	==Mission Task==		==Mission Task==

Dan: /* Event Determination */

2018-01-23T17:05:27Z

Event Determination

← Older revision		Revision as of 10:05, 23 January 2018
Line 9:		Line 9:
	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.		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.

	==Event Determination==		==Event Complexity Determination==
	Every month, each commissioned ship has a less than 1-in-12 chance of engaging in an Event of some level. Instead of rolling for each ship every month to see if the ship had an Event, roll 1d100% and multiply by 1/12th of the number of active ships (see ''Note'' below) to determine the number of Monthly Events and then follow these steps:		Every month, each commissioned ship has a less than 1-in-12 chance of engaging in an Event of some level. Instead of rolling for each ship every month to see if the ship had an Event, roll 1d100% and multiply by 1/12th of the number of active ships (see ''Note'' below) to determine the number of Monthly Events and then follow these steps:
	# Roll percentile dice four times. Each roll represents the number of Events at each level, starting with Simple ones, with each following percentile roll a factor of the remaining Events. Extreme events receive the final remainder.<br>''Ex: For the month of March, 80 Monthly Events are determined to occur. The four percentile rolls are 35, 16, 86 and 19, representing the Simple, Routine, Challenging and Difficult Events. Respectively (and in order), those result in 28 Simple, 8 Routine, 38 Challenging and 1 Difficult Events, leaving 5 Extreme Events.''		# Roll percentile dice four times. Each roll represents the number of Events at each level, starting with Simple ones, with each following percentile roll a factor of the remaining Events. Extreme events receive the final remainder.<br>''Ex: For the month of March, 80 Monthly Events are determined to occur. The four percentile rolls are 35, 16, 86 and 19, representing the Simple, Routine, Challenging and Difficult Events. Respectively (and in order), those result in 28 Simple, 8 Routine, 38 Challenging and 1 Difficult Events, leaving 5 Extreme Events.''

Dan: Dan moved page Events to Random Events

2018-01-23T15:58:04Z

Dan moved page Events to Random Events

← Older revision	Revision as of 08:58, 23 January 2018
(No difference)