Difference between revisions of "Techno-Babble!"

From benscondo.wiki-rpg.com
Jump to: navigation, search
(Tasks)
(How To Use Technobabble)
Line 31: Line 31:
  
 
There still may be problems once the solution is implemented. In the given example, the planet might successfully navigate the wormhole, but undergo great stresses and have massive planetary damage caused. The more specific the player makes their declaration, and the less complications which can occur after the solution, the more difficult the problem will be (higher TN).
 
There still may be problems once the solution is implemented. In the given example, the planet might successfully navigate the wormhole, but undergo great stresses and have massive planetary damage caused. The more specific the player makes their declaration, and the less complications which can occur after the solution, the more difficult the problem will be (higher TN).
 +
 +
==Anatomy of a Solution==
 +
Each solution must adhere to a specific structure. This structure must answer the following: Who-> What-> How? Some solutions might also contain Where and Why, but they are not required. All elements of the structure must be successfully completed for a solution to be considered completed.
 +
 +
Cards drawn as tasks fulfill the 'What'. Each task is a subset of the 'What', once all tasks are completed the 'What' is considered completed. The 'Who' can generally be answered by the player creating the solution, but in special cases, indicated on the card, a non-standard crew member must complete the task. The reason should be evident based on the card, but if it is not the player may decide why. Alternatively, they may ask the GM to determine why. Like 'Who', 'How' can usually be left to player creativity. In special cases, as marked on the card, it will be dictated.
 +
 +
If a task has the Where or Why keyword, then those must be determined. Draw cards and consult the appropriate section.
  
 
==Setting Difficulty TN==
 
==Setting Difficulty TN==

Revision as of 18:35, 16 December 2012

Some thoughts for Star Trek problem-solving:

Techno-Babble can be used to generate steps that guarantee a solution to difficult situations. NOTE THAT THIS IS NOT A GUARANTEE OF SUCCESS. Separate skill rolls to implement the various steps of the solution are still required. What the solution does guarantee is if you can successfully implement the solution and overcome the complications presented the issue will be positively resolved.
1) This skill is Player-initiated, meaning the Player must inform the Narrator they wish to attempt to use Techno-Babble.
2) Using Techno-Babble costs 1 Courage.
3) Narrator sets the TN and negotiates with the Player to determine the Primary System involved in the solution.
4) Player declares how much Courage (worth 5 per point used) they want to invest and makes the standard roll of 2d6 + Techno-Babble level + Courage.
5) The Player then draws cards from the appropriate skill deck, following the Matrix, to make up the difference between the roll and the TN.
6) The Player then works through the complications on the cards and the jargon tables privately and then makes their public proposal to the group and GM of their solution.
7) The group decides whether or not to attempt the Techno-Babble solution and then follows through or ignores the potential solution.


Matrix to separate skill levels and worth

How do we reward skill levels?

Risk of important NPCs/PCs as substitutes for cards?

Break down ship systems into a physical/logical map: Starship Systems
- COMPUTER is adjacent to all systems

Table of particles, adjectives, hardware components
Vocabulary: Ionization, particles, fluctuations, disruptions, interference, unstable

Individual decks for each skill type: Engineering/Science, Combat/Command, Social/Medicine

How To Use Technobabble

The first step in using the technobabble skill is declaring what the problem is the character is trying to solve, and which skill they would like to use. The player and GM then determine which type of technobabble this is, and, if appropriate, which systems are involved. The player must be clear what the resolution will be.

Example: I want to figure out how to create an artificial wormhole in the path of the planet so that it can be transported into a nearby system and thereby survive the upcoming nova explosion. If properly implemented, the planet will successfully navigate the wormhole and arrive in the declared system.

There still may be problems once the solution is implemented. In the given example, the planet might successfully navigate the wormhole, but undergo great stresses and have massive planetary damage caused. The more specific the player makes their declaration, and the less complications which can occur after the solution, the more difficult the problem will be (higher TN).

Anatomy of a Solution

Each solution must adhere to a specific structure. This structure must answer the following: Who-> What-> How? Some solutions might also contain Where and Why, but they are not required. All elements of the structure must be successfully completed for a solution to be considered completed.

Cards drawn as tasks fulfill the 'What'. Each task is a subset of the 'What', once all tasks are completed the 'What' is considered completed. The 'Who' can generally be answered by the player creating the solution, but in special cases, indicated on the card, a non-standard crew member must complete the task. The reason should be evident based on the card, but if it is not the player may decide why. Alternatively, they may ask the GM to determine why. Like 'Who', 'How' can usually be left to player creativity. In special cases, as marked on the card, it will be dictated.

If a task has the Where or Why keyword, then those must be determined. Draw cards and consult the appropriate section.

Setting Difficulty TN

The difficulty TN assigned in a Technobabble test is likely to be extremely high, potentially 40+. This difficulty is never secret. It should be noted that the player should not expect to pass the TN test, but if they do it means that the solution can be implemented with no complications (in other words, just a set of one or more standard tests). Normally, Technobabble is used for very difficult situations, where complications and dangers should be expected. The difference in roll and TN determines how many complications may be discarded, and how serious the complications are.

The Matrix

The matrix is the method for determining the number of tasks required to complete the solution. Roll the appropriate skill and consult the matrix. The number is the maximum number of cards the player may draw to implement the solution. The player may choose to draw less, but he must state how many cards he will draw before he looks at any of them.

Cards As Tasks

Completing a Technobabble solution involves successful completion of a series of tasks. These tasks may be independent or interdependent, and could potentially rely on others to be completed before they can be started. Each card drawn in the initial phase represents one task. Each task has a value associated with it on the card.

To architect a series of tasks, draw the appropriate number of cards and choose tasks from those cards that meet or exceed the TN for the solution. All cards drawn must be used as tasks. If the cards do not have enough points to complete the solution, continue drawing cards one at a time and applying them to the solution. All cards drawn in this manner must choose the highest value task.

Cards As Details

Each Technobabble card also has a section to provide details to a player attempting to craft his solution. Once all tasks are created, the player may choose to draw any number of cards to consult the details for filling in the 'What' portion of the solution. There is more flexibility on cards drawn this way, but every attempt should be made to use all of them.