![]() |
![]() |
![]()
Post
#1
|
|
jacked in ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Group: Admin Posts: 9,425 Joined: 26-February 02 Member No.: 463 ![]() |
I'm always wondering how this is supposed to work. (IMG:style_emoticons/default/smile.gif)
You can use Edge to negate a Glitch. But can you also use Edge to gain extra hits, despite having rolled a Glitch (without negating it, of course)? i.e. you roll 10 dice, 2 hits and a Glitch. Can you use Edge to re-roll 8 dice, in order to increase the number of hits you get (but still suffer the Glitch)? Or does a Glitch automatically negate all other Edge-options (apart from negating the Glitch, that is)? Bye Thanee |
|
|
![]() |
![]()
Post
#2
|
|
Shooting Target ![]() ![]() ![]() ![]() Group: Members Posts: 1,647 Joined: 22-April 12 From: somewhere far beyond sanity Member No.: 51,886 ![]() |
Interesting. I always thought that you can negate a glitch by re-rolling dice without hits. Now I know better. I wonder if I'll keep that houserule. (IMG:style_emoticons/default/smile.gif)
|
|
|
![]()
Post
#3
|
|
Runner ![]() ![]() ![]() ![]() ![]() ![]() Group: Members Posts: 2,536 Joined: 13-July 09 Member No.: 17,389 ![]() |
Interesting. I always thought that you can negate a glitch by re-rolling dice without hits. Now I know better. I wonder if I'll keep that houserule. (IMG:style_emoticons/default/smile.gif) There's not enough evidence to prove one way or another. |
|
|
![]()
Post
#4
|
|
Immortal Elf ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Group: Members Posts: 10,289 Joined: 2-October 08 Member No.: 16,392 ![]() |
There's not enough evidence to prove one way or another. This. At my table, if you pick up failed dice and reroll them, they're no longer 1s. Glitches aren't determined until after the dice stop rolling. So at our table you can "negate" a glitch by rerolling the dice. Maybe it doesn't make sense "any other way" if the rule exists...unless it doesn't make any sense for the rule to exist. It's like an if(false) { } statement in programming. It'll never execute, but it'll compile anyway! (Most compilers will throw a warning that it won't ever execute, but there are valid reasons to do it). (Similarly there's if(a != a) { }--read "if a value does not equal itself," which appears at first glance to always evaluate to false, but there is one case where it will evaluate to true: NaN.* All comparisons for equality to NaN return false. I.e. NaN == NaN will return false, so the inverse will return true). *Special value, "Not A Number." Happens when you attempt to divide by 0 or similar. |
|
|
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 14th March 2025 - 04:43 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.