NEPHiLiX
October 7th, 2010, 03:21
First, I've been getting BSOD's like mad until I switched to the Beta version (2.7). It was fantastic! Got through 15 rounds of combat with multiple opponents and many books open and no crashes!! Thank you!!!
I did, however, notice a few problems. The first was the dice rolling: the d100 was strange. On the d100, the tens (the first number you read) is noted in "tens" (10, 20, 30 ,40 etc) on the die, while the # that follows is noted in single digits (5, 6, 7, 8, 9, 0, etc). On the program's dice, however, the "0" is noted as "10"). The problem occurs when you roll a "10" on the single-digit die. A roll of 80 + 10 should result in an "80" (80 + 0), not "90". Can I change this to the standard read (where a 00 is a 100)?
Second, the subtraction of rounds of Stun/No Parry/etc should only occur at the end of the next round. For example the program behaves this way:
~first round~
"Foe" swings...misses
"Opponent" strikes...hits, stuns foe for one round.
~next round~
"Foe" swings (because moving to the next round reduces that one round of stun even though "Foe" had already fully acted in round 1). In this instance, it is impossible for "Opponent" to stun "Foe" unless he stuns him for more than 1 round (giving the faster "Foe" a distinct advantage, 1 round of stun can prevent "Opponent" from ever acting, but 1 round of stun delivered to "Foe" will never do anything).
Otherwise, loving the automation!
I did, however, notice a few problems. The first was the dice rolling: the d100 was strange. On the d100, the tens (the first number you read) is noted in "tens" (10, 20, 30 ,40 etc) on the die, while the # that follows is noted in single digits (5, 6, 7, 8, 9, 0, etc). On the program's dice, however, the "0" is noted as "10"). The problem occurs when you roll a "10" on the single-digit die. A roll of 80 + 10 should result in an "80" (80 + 0), not "90". Can I change this to the standard read (where a 00 is a 100)?
Second, the subtraction of rounds of Stun/No Parry/etc should only occur at the end of the next round. For example the program behaves this way:
~first round~
"Foe" swings...misses
"Opponent" strikes...hits, stuns foe for one round.
~next round~
"Foe" swings (because moving to the next round reduces that one round of stun even though "Foe" had already fully acted in round 1). In this instance, it is impossible for "Opponent" to stun "Foe" unless he stuns him for more than 1 round (giving the faster "Foe" a distinct advantage, 1 round of stun can prevent "Opponent" from ever acting, but 1 round of stun delivered to "Foe" will never do anything).
Otherwise, loving the automation!