| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| game_mechanics:project [2026/07/01 09:36] – ms_wuntch | game_mechanics:project [2026/08/14 12:50] (current) – removed ms_wuntch |
|---|
| ====== Project ====== | |
| When a [[:Character]] is performing a [[Game Mechanics:Definitions:Ability:Ritual]], they may convert it into a [[Game Mechanics:Project#Project|Project]]. A [[Game Mechanics:Project#Project|Project]] doesn’t require [[:Game Mechanics:Multitasking|Multitasking Saves]] to do other activities nor require constant concentration.\\ | |
| \\ | |
| Unless otherwise stated, a [[:Character]] can only maintain 2 [[Game Mechanics:Project#Project|Projects]].\\ | |
| \\ | |
| There is no hard and fast rule for what [[Game Mechanics:Definitions:Ability:Ritual|Rituals]] can be converted into [[Game Mechanics:Project#Project|Projects]]. Typically, it is for tasks that require time, and can’t otherwise be rushed, like growing mushrooms or converting an ancient tablet.\\ | |
| \\ | |
| The [[Game Mechanics:Definitions:Game Master|GM]] has final say on whether or not a [[Game Mechanics:Definitions:Ability:Ritual]] can become a [[Game Mechanics:Project#Project|Project]] or not, however it should take into account the [[:Character]], the narrative and game play. Common sense should prevail but if all else fails, roll a die.\\ | |
| \\ | |
| Some common examples of [[Game Mechanics:Definitions:Ability:Ritual|Rituals]] that probably should not be converted into [[Game Mechanics:Project#Project|Projects]]: Invocations, surgery, installing [[:Cyberware]], applying [[:Items:Gadgets:Consumables:Repair Patch|Repair Patches]] or other forms of emergency repairs or charging a [Generator].\\ | |
| \\ | |
| Some examples of [[Game Mechanics:Definitions:Ability:Ritual|Rituals]] that could be converted into [[Game Mechanics:Project#Project|Projects]]: long form repairs on a [Vehicle], studying an artefact, translating a message, crafting an item or applying a [[:Items:Mods|Mod]].\\ | |
| \\ | |
| Finally, while it should not be common, perhaps when picking back up an [[Game Mechanics:Project#Project|Project]], if it is particularly difficult or fiddly, the [[Game Mechanics:Definitions:Game Master|GM]] may ask for a [[:Game Mechanics:Multitasking|Multitasking Save]]. Should this [[:Game Mechanics:Save]] [[:Game Mechanics:Success and Failure:Failure|Fail]], it should rarely, if ever, result in the [[Game Mechanics:Definitions:Ability:Ritual]] [[:Game Mechanics:Success and Failure:Failure|Failing]] but instead, maybe the progress is halved or the next [[Game Mechanics:Definitions:Ability:Ritual#Interval|Interval’s]] [[:Game Mechanics:Check]] will be taken with [[Game Mechanics:Definitions:Property:Disadvantage]]. The subsequent [[:Game Mechanics:Check|Checks]] may result in the [[Game Mechanics:Definitions:Ability:Ritual]] [[:Game Mechanics:Success and Failure:Failure|Failing]], as normal. | |
| |
| ==== Changelog ==== | |
| <WRAP changelog center 800px> | |
| Version 0.5c - Jun 2026 | |
| * Page moved to Project from Ongoing Projects. | |
| * Page updated. | |
| </WRAP> | |
| |
| |
