Talk:Aberrant 2.0 Mental Systems - Revision history

Peel: /* Examples */

2011-03-16T02:07:02Z

Examples

← Older revision		Revision as of 19:07, 15 March 2011
Line 60:		Line 60:
	**3d automeds: 30 sux		**3d automeds: 30 sux
	**+2d failsafe: 10 sux		**+2d failsafe: 10 sux
			**Soak 6B/8L, Strength + 1/Dexterity + 1/Perception + 1, 3d automeds, 6d failsafe, Mass 9

Peel: /* Examples */

2011-03-16T02:03:44Z

Examples

← Older revision		Revision as of 19:03, 15 March 2011
Line 49:		Line 49:
	**Ultralight: 15 sux		**Ultralight: 15 sux
	**Accuracy +2, Dmg 12L [6], Range 2,500, Rate 2, Magazine 10, AA, Exp(3), Guided, Conceal O, Mass 20, Min Str. 3		**Accuracy +2, Dmg 12L [6], Range 2,500, Rate 2, Magazine 10, AA, Exp(3), Guided, Conceal O, Mass 20, Min Str. 3

			*'''Rapier Special Operations Armour''': 175 sux
			**Field Suit: (4+1) x 5 = 25 sux
			**+2B soak: 6 sux
			**+2L soak: 14 sux
			**Powered: 20 sux
			**+1 dexterity: 30 sux
			**+1 stamina: 20 sux
			**+1 perception: 20 sux
			**3d automeds: 30 sux
			**+2d failsafe: 10 sux

Peel: /* Examples */

2011-03-15T21:12:27Z

Examples

← Older revision		Revision as of 14:12, 15 March 2011
Line 42:		Line 42:

	=Examples=		=Examples=
	*'''Itano Minimissile Launcher''': ~~109~~ sux		*'''Itano Minimissile Launcher''': 124 sux
	**Missile Launcher: (6+2) x 5 = 40 sux		**Missile Launcher: (6+2) x 5 = 40 sux
	**Concealable (O): 50 sux		**Concealable (O): 50 sux
	**ROF +100%: 10 sux		**ROF +100%: 10 sux
	**Ammo + 150%: 9 sux		**Ammo + 150%: 9 sux
			**Ultralight: 15 sux
	**Accuracy +2, Dmg 12L [6], Range 2,500, Rate 2, Magazine 10, AA, Exp(3), Guided, Conceal O, Mass 20, Min Str. 3		**Accuracy +2, Dmg 12L [6], Range 2,500, Rate 2, Magazine 10, AA, Exp(3), Guided, Conceal O, Mass 20, Min Str. 3

Peel at 18:31, 15 March 2011

2011-03-15T18:31:16Z

← Older revision		Revision as of 11:31, 15 March 2011
Line 40:		Line 40:
	*Known issues: The Bug mechanic does not handle possibly very different success counts for working on similar items.		*Known issues: The Bug mechanic does not handle possibly very different success counts for working on similar items.
	*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.		*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.

			=Examples=
			*'''Itano Minimissile Launcher''': 109 sux
			**Missile Launcher: (6+2) x 5 = 40 sux
			**Concealable (O): 50 sux
			**ROF +100%: 10 sux
			**Ammo + 150%: 9 sux
			**Accuracy +2, Dmg 12L [6], Range 2,500, Rate 2, Magazine 10, AA, Exp(3), Guided, Conceal O, Mass 20, Min Str. 3

Peel: /* Gaining Flaws */

2011-03-15T14:38:30Z

Gaining Flaws

← Older revision		Revision as of 07:38, 15 March 2011
Line 33:		Line 33:
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.
	Flaws are gained in three ways:		Flaws are gained in three ways:
	*'''Concessions''': Straightforward performance increases can be matched with straightforward performance decreases to reduce technical challenge. One or more minor flaw s can be added to a project to reduce the cost by half of the flaw's equivalent value in successes, up to half the total cost of the project.		*'''Concessions''': Straightforward performance increases can be matched with straightforward performance decreases to reduce technical challenge. One or more minor flaw s can be added to a project to reduce the cost by half of the flaw's equivalent value in successes, up to half the total cost of the project. I'm dubious about this one.
	*'''Bugs''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.		*'''Bugs''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.
	*'''Errors''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.		*'''Errors''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.

Peel: /* Gaining Flaws */

2011-03-15T12:41:16Z

Gaining Flaws

← Older revision		Revision as of 05:41, 15 March 2011
Line 32:		Line 32:
	*'''Major Flaws''' could be the requirement of expert dice pools to operate the device, a vulnerability to a fairly common environmental condition like sand or heavy rain, or a more severe impairment of function. Moderately impaired functions should be a different one to the one intended to be improved by the project.		*'''Major Flaws''' could be the requirement of expert dice pools to operate the device, a vulnerability to a fairly common environmental condition like sand or heavy rain, or a more severe impairment of function. Moderately impaired functions should be a different one to the one intended to be improved by the project.
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.
	Flaws are gained in ~~two~~ ways:		Flaws are gained in three ways:
			*'''Concessions''': Straightforward performance increases can be matched with straightforward performance decreases to reduce technical challenge. One or more minor flaw s can be added to a project to reduce the cost by half of the flaw's equivalent value in successes, up to half the total cost of the project.
	*'''Bugs''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.		*'''Bugs''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.
	*'''Errors''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.		*'''Errors''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.

Peel: /* Gaining Flaws */

2011-03-15T06:23:51Z

Gaining Flaws

← Older revision		Revision as of 23:23, 14 March 2011
Line 33:		Line 33:
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.
	Flaws are gained in two ways:		Flaws are gained in two ways:
	*'''~~Concessions~~''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.		*'''Bugs''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.
	*'''~~Bugs~~''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.		*'''Errors''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.


	*Known issues: The ~~Concession~~ mechanic does not handle possibly very different success counts for working on similar items.		*Known issues: The Bug mechanic does not handle possibly very different success counts for working on similar items.
	*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.		*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.

Peel: /* Gaining Flaws */

2011-03-15T06:23:21Z

Gaining Flaws

← Older revision		Revision as of 23:23, 14 March 2011
Line 33:		Line 33:
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.
	Flaws are gained in two ways:		Flaws are gained in two ways:
	*'''~~Concession~~''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.		*'''Concessions''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.
	*'''Bugs''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.		*'''Bugs''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.

Peel: /* Gaining Flaws */

2011-03-15T06:23:11Z

Gaining Flaws

← Older revision		Revision as of 23:23, 14 March 2011
Line 33:		Line 33:
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.
	Flaws are gained in two ways:		Flaws are gained in two ways:
	*'''~~Errors~~''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.		*'''Concession''': When you push the envelope into immature technology, unforseen issues spring up. Each type of project has a Bleeding Edge Threshold. When the number of successes accumulated exceeds this threshold, a minor flaw of the ST's choice becomes apparent to the developers. When the number of successes exceeds twice that threshold, a second minor flaw becomes apparent, or a minor flaw becomes major. Three times the threshold adds a major flaw or makes a major flaw severe. Each additional threshold multiple reached adds another major flaw or replaces a major flaw with a severe one.
	*'''Bugs''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.		*'''Bugs''': Avoidable mistakes in development that become apparent far too late. If a development roll is botched, the project develops a minor flaw. If a second roll is botched, the project develops a major flaw. If a third roll is botched, the project develops a severe flaw. A fourth botch forces the project to start from scratch.


	*Known issues: The ~~Error~~ mechanic does not handle possibly very different success counts for working on similar items.		*Known issues: The Concession mechanic does not handle possibly very different success counts for working on similar items.
	*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.		*Possible fix: Instead apply it to going beyond the limits on improvements per project, and tighten them up slightly.

Peel: /* Gaining Flaws */

2011-03-15T06:18:38Z

Gaining Flaws

← Older revision		Revision as of 23:18, 14 March 2011
Line 29:		Line 29:
	==Gaining Flaws==		==Gaining Flaws==
	Flaws are aberrations but for gadgets. They are the price of power, sometimes willing and sometimes accidental. Flaws are categorised into three levels of severity.		Flaws are aberrations but for gadgets. They are the price of power, sometimes willing and sometimes accidental. Flaws are categorised into three levels of severity.
	*'''Minor Flaws''' could be a weakening of armour soak one level ~~blow~~ spec, a small loss of accuracy from a gun, 25% reduced fuel efficiency in a vehicle or some other minor impairment of function. This may be a function the project was designed to improve, and represent the project falling short of expectations.		*'''Minor Flaws''' could be a weakening of armour soak one level below spec, a small loss of accuracy from a gun, 25% reduced fuel efficiency in a vehicle or some other minor impairment of function. This may be a function the project was designed to improve, and represent the project falling short of expectations.
	*'''Major Flaws''' could be the requirement of expert dice pools to operate the device, a vulnerability to a fairly common environmental condition like sand or heavy rain, or a more severe impairment of function. Moderately impaired functions should be a different one to the one intended to be improved by the project.		*'''Major Flaws''' could be the requirement of expert dice pools to operate the device, a vulnerability to a fairly common environmental condition like sand or heavy rain, or a more severe impairment of function. Moderately impaired functions should be a different one to the one intended to be improved by the project.
	*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.		*'''Severe Flaws''' are potentially crippling drawbacks, like a gun that explodes on a d1 roll of 1 each time it is used, or an FTL drive that travels via Hell. In general they should make scrapping the entire project look more tempting than actually trying to use the thing.