Revision as of 19:03, 3 January 2011

The Ruby Engine is a component of a LARP engine. So far we are talking about skill use, and how often players should be able to "do things". The intent of this design mockup is to find a method of controlling use-rates for player skills. Design goals:

• Two frequencies of skills: Per Encounter, and Per Event
• high and low level players can contend with each other. High level players have better options.
• Players choose a limited number of feats - which are essentially passive skills
• Many skills can only be activated in certain conditions or situations - this is intended to (a) limit the ability to "supernova", ie unload a ton of rough skills at once, (b)encourage teamwork. ie the fighter sets up the monster with a disarm attack, then the rogue shanks him using a skill that can only be used on an unarmed target.
• It has to be absolutely clear whether or not a player is affected by a status effect.
• Some skills are tagged as Teamwork skills. This means that you or the target needs a certain status in order to activate the skill, and you cannot be the one that created that status. For example, a skill called Self-Heal will heal 3 points of damage if you to have the status Blessed. Since the skill has the Teamwork keyword, you cannot Bless yourself, you need somebody else to do it for you.

Statuses and Conditions

These are things which might trigger or key off skills.

• Keen - requisite for using certain weapon skills
• Rage - requisite for using certain martial skills
• Sly - requisite for using certain rogue / stealth skills
• Charged - requisite for using certain arcane skills
• Blessed - requisite for using certain divine skills

• Unarmed - you have this status whenever you are not holding weapons
• Dizzy - Status - prevents throwing packets
• Weak - Status - prevents you from using called melee attacks
• Slow - Status - you cannot run
• Winded - Status - you can only use one call every 3 seconds
• Stunned - Status - knocked out