[b]The Issue[/b]
The rules concerning Tests are inconsistent. In opposed tests, high is good. In other tests, low is good.
Also, the rules call for a fair bit of subtraction. While very much able to do basic arithmetic, I prefer to keep my numbercrunching to a minimum.
[b]The Proposed Solution[/b]
I'm thinking about extending the "high is good" rule to include all Tests. This is essentially the same mechanic as in Blackjack, familiar to many card players, and was first (was far as I know) used as a roleplaying mechanic in the game Pendragon.
The basic idea is this: High is always good. A high roll is always better than a low roll - [i]within the same result space[/i]. There are two basic result spaces: Success and Failure. If target number is 45 and one succeeds with a 12, that's not as good a success as a 30, but a better success than a 3. At 45 there's a breaking point. 80 is, in this instance, worse than 30. However, its better than 50.
This takes some time to get used to, but easy enough to determine by simple comparison:
1) did the roll succeed?
2) Higher is better: A high fail is a "lesser" fail than a low roll, and a high "success" is better than a low success.
(this, incidentally, also enables values above 99, since one can quickly try to add 100 to any successful roll - if target number is 120, and the roll is 3, the result is 103)
Margin of Success and Margin of Failiure are defined from the bottom. If MoS is 30, then the roll needs to be at least 30 to be within MoS. No more subtraction, just simple comparison.
MoF still requires addition, but addition takes less time than subtraction, so it's OK. If MoF is 20 on a target number of 34, then you need to either succeed or get a really high failed roll. Again, [i]Higher is better[/i].
Rolls of 99 and 00 are reversed. 00 is always a failure, 99 is always a success.
[b]The question[/b]
I am not much of a rules geek. That is, I enjoy designing rule systems, but I prefer simplicity and I'm not very good at remembering complex systems (and yes, by my standards Eclipse Phase is complex). So, I'm wondering - what will my Pendragon Hack break? Is there some mechanic I'm not aware of, which invalidates the entire idea?
—
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist