Iterative Attacks

[Bone White]

You're moving more and more towards requiring a weapons database. In the meantime you could have different properties on a token. Attack1CriticalRange, Attack2CriticalRange etc so:

[code=php][attack1CriticalRange = "19,20"]
[attack2CriticalRange = "18,19,20"]
[for(attack,0,listLength(meleeAttackList)),Code:{
   [currentAttackCriticalRange = getProperty("attack" + attack + "CriticalRange")]
   [attackRoll = 1d20+attack]
   [if (listContains(currentAttackCriticalRange,attackRoll)): attackRoll = attackRoll + 1d20]
   [attackRoll] for [meleeDamage] [if (listContains(currentAttackCriticalRange,attackRoll)): "Critical!"]
}] [/code]

Yes this is messy, and you may need to tweak the code to fit your game, but I can't think of a simpler way off the top of my head. A database is the way to go and the sooner you start on that the easier your life will be.

[wolph42]

Why would you use ranges ? It's convoluted and slower. Simply set the crit value eg critRange=18 and then if(roll >= critRange):... Is much simpler.

[Xannelson]

Oh...well that makes a lot more sense.

[Bone White]

Why would you use ranges ? It's convoluted and slower. Simply set the crit value eg critRange=18 and then if(roll >= critRange):... Is much simpler.

It's more powerful and allows for ranges which are not simply just greater than or equal. It also teaches the user about lists, which is the current topic of tutoring.

[wolph42]

Why would you use ranges ? It's convoluted and slower. Simply set the crit value eg critRange=18 and then if(roll >= critRange):... Is much simpler.

It's more powerful and allows for ranges which are not simply just greater than or equal. It also teaches the user about lists, which is the current topic of tutoring.

true, but I think the lesson to be learned should be: use the most optimal form for the occasion!

[Queenwalts]

I'm planning a character that has 2 claw attacks and a tail attack as natural weapons, but now I'm a little confused about the mechanics of using them all.