GenAbility

CoffeeMUD
Administrator                                                  Builder                                                              Player

=CoffeeMUD Administrator Information=
Installation     Help     Development    Modification     Feature Requests     Mud Grinder     ini     Security     CMARE Share     Wiki

=CoffeeMUD MUDGrinder=
Control Panel     File Browser     Journal Browser    Account Manager     Player Manager     Clan Manager     Polls Manager     System Reports     Server Log     Statistics    Cache Resources     Races     Classes     Abilities     Skill Recipes     SkillComponents     Quest Manager    Achievements     Holidays     Factions     Socials     Deities     Catalog

GenAbilities are abilities that are created virtually within CoffeeMUD.

Creating GenAbilities

Creating GenAbilities Using the Command Line

To create an ability in-game, use the command CREATE ABILITY [ability_name].

To create a crafting skill, use the command CREATE CRAFTSKILL [ability_name].

To create a language skill, use the command CREATE LANGUAGE [language_name].

• [ability_name] should be very descriptive to the nature of the ability. For example, if you are creating an ability that only wolves would use, you may wish to name the ability Wolf_Rake. You will have an opportunity to provide a more user-friendly display name later. Uniqueness of this name is important for making help file entries.

Creating GenAbilities Using the MUDGrinder

Select the Abilities link in the main Grinder menu. Scroll to the bottom of the list in the Abilities Creator page and type your ability name in the appropriate skill type, then click the Create new (skill type) link to the left of the entry box you chose.

GenAbility Data

Ability/Skill name

This is the display name of the ability that players/mobs will use.

Type, Domain

The type of ability will determine where it appears on a player's abilities list, whether it is a chant, prayer, skill, song or spell. The Domain affects which expertises apply to it, as well as other domain-related affects.

• Do not put a space between the type and the domain, only place a comma between the two fields.
• The domain name should not have any spaces. Typically, an underscore is used between domains with multiple words, like nature_lore.
• Do not attempt to create new domains with this field. It does not work.

Command Words

This is the command you must state before specifying the ability name and target. For spells, this is CAST, CA, C. For properties, this field is blank. This field can be any command word desired, but may result in some conflicts within your mud when players are using socials or other commands of the same name as this field.

Minimum Range

The minimum range in which the mob must be to use the ability on the target. This is a descriptive list, with values of:

• Melee
• Close
• Short
• Medium
• Long
• Longer
• Longerstill
• Extremelylong
• Infinite

Maximum Range

The maximum range in which the mob must be to use the ability on the target. Maximum Range uses the same descriptive list as minimum range, and should be the same or further than Minimum Range.

Ticks Between Casts

This field determines the frequency in which the ability may be used. If set to 0, this ability may be used as frequently as commanded. Any positive integer will cause this ability to be unavailable for use until that number of ticks has gone by.

Duration Override

This field will override an ability's duration. Normally, abilities will last for a Standard Duration.

Affect String

This is the display players will see when using the AFFECTS or SCORE command for abilities that persist. Generally, the affect string should be enclosed in parentheses. This may be left blank if you do not desire a player to be able to detect the affect. Obvious affects (like paralysis, losing a limb, or having a horrid stench) should have an affect string. If the #Can Affect is not set properly, this field will not be used.

Help Text

This field provides additional information from the HELP (ability_name) command to players. It should always start with the tag <ABILITY> and does not require a closing tag. It is also useful to add in any Usage and Example information to be consistent with other help files. To add these additional fields using the help text, include the field name and enough spaces to reach the tenth character, which should be a colon (:), then a space and your field information. For subsequent lines within the same field type, use a colon, eight spaces, a colon, a space, and subsequent text. Repeat for each additional field you wish to include. At the end of each field, include a carriage return or %0D to force the formatting. After including all of your field data, put in your abilities description to help players understand and use the ability.

Command Line Example 

<ABILITY>Usage : RAKE [TARGET NAME]%0DExample : rake orc%0DUsing his powerful hind-claws, a wolf may rake flesh from his opponent.

MUDGrinder Example 

<ABILITY>Usage : RAKE [TARGET NAME]
Example : rake orc
: : rake bob
Using his powerful hind-claws, a wolf may rake flesh from his opponent.

Notes

.