 Simple Software Bug Rule, Simple Optional Rule |
  |
 Mar 4 2007, 10:59 PM
Post
#1
|
|
|
Target  Group: Members Posts: 31 Joined: 28-October 02 Member No.: 3,512  |
One of the things I like most about S4 is that it makes it possible to succeed, and yet not have things work according to plan.
I had a simple but effective idea for including Bugs for software-and really for any B/R task. On extended tests, every glitch rolled adds a 1 point Bug instead of increasing the threshold by one. Each bug acts exactly like a level of gremlins for that piece of software. Meaning it reduces the amount of one's rolled needed to incur a glitch. This can also be used for any hardware. I also expanded this for foci as well using the cursed quality as a guideline. That is about all. I have not yet come to a reasonable and simple procedure to remove bugs or flaws in a focus design, but I'll be thinking on it. |
 |
 
|
|
Mar 4 2007, 11:01 PM
Post
#2
|
|
|
Moving Target Group: Members Posts: 138 Joined: 1-September 02 From: France Member No.: 3,208 |
I like it. Maybe on another scale, but the principle, I like it.
|
|
|
|
|
|
Lo-Fi Version | Time is now: 6th May 2025 - 01:12 PM |
Topps, Inc has sole ownership of the names, logo, artwork, marks, photographs, sounds, audio, video and/or any proprietary material used in connection with the game Shadowrun. Topps, Inc has granted permission to the Dumpshock Forums to use such names, logos, artwork, marks and/or any proprietary materials for promotional and informational purposes on its website but does not endorse, and is not affiliated with the Dumpshock Forums in any official capacity whatsoever.