Difference between revisions of "TYPEDEF"
m (→Built-in Types: fixed details for t_telepad) |
m (→Built-in Types: added t_clock, t_trap, t_trap_active, t_musical, t_spell, t_gem, t_water, and t_clothing) |
||
Line 153: | Line 153: | ||
* MORE1 (or MORE2?) = Amount of damage it will cause when stepped on or dclicked | * MORE1 (or MORE2?) = Amount of damage it will cause when stepped on or dclicked | ||
* MOREZ = Type of light pattern it will cast | * MOREZ = Type of light pattern it will cast | ||
− | |- | + | |- |
− | | ... || | + | | t_clock || 24 || This type is used to tell time (game time, not real time) when double clicked. The result comes out something like "half past eleven o'clock at night". From what I can tell there are no MORE or TDATA modifiers that affect the result. |
+ | |- | ||
+ | | t_trap and t_trap_active || 25 and 26 || These types are used for traps that are triggered when walked on. They leverage the following properties: | ||
+ | * MORE1 = ID of the animation | ||
+ | * MORE2 = The damage the trap will cause | ||
+ | * MOREX = The length of time the animation will run | ||
+ | * MOREY = The length of time the activated trap will idle until reset | ||
+ | * MOREZ = A flag that indicates if the trap must idle before changing from active to inactive. | ||
+ | |- | ||
+ | | t_musical || 27 || This type is used for musical instruments. It leverages the following properties: | ||
+ | * TDATA1 = The sound ID to be played if successful | ||
+ | * TDATA2 = The sound ID to be played if not successful | ||
+ | |- | ||
+ | | t_spell || 28 || This type is used for magic spell effects. It leverages the following properties: | ||
+ | * MORE1L = The polymorph effect on STR | ||
+ | * MORE1H = The polymorph effect on DEX | ||
+ | * MORE2 = The number of charges left | ||
+ | * MOREX = The spell effect that will result when the item is stepped on | ||
+ | * MOREY = The strength of the spell (This has a different effect defending on the spell, usually between 0 and 1000) | ||
+ | * MOREZ = Type of light pattern it will cast | ||
+ | |- | ||
+ | | t_gem || 29 || This type is used for gems, and from what I can tell there is no built-in behavior for it. | ||
+ | |- | ||
+ | | t_water || 30 || This type is used for water, which means it can be fished in or used to clean used bandages. | ||
+ | * MORE1 = The regiontype ID that determines what sorts of resources (fish etc) that it can produce (is this true?) | ||
+ | |- | ||
+ | | t_clothing || 31 || This type is used for all cloth based equip-able items. It is essentially identical to t_armor and t_armor_leather. It leverages the following properties: | ||
+ | * MORE1L = Max hitpoints | ||
+ | * MORE1H = Current hitpoints | ||
+ | * MOREX = Spell effect when worn (for example, setting MOREX=1 causes a permanent Clumsy effect) | ||
+ | * MOREY = There are two possible effects of setting MOREY: | ||
+ | *# If MOREX is set, then MOREY is the power/effect of that spell | ||
+ | *# If the ATTR includes attr_magic, then there is an AR bonus (how is this calculated?) | ||
+ | '''Note:''' Old versions of sphere stored remaining charges in MORE2, this is no longer true. | ||
|- | |- | ||
| t_scroll || 32 || This type is used for scrolls. It leverages the following properties: | | t_scroll || 32 || This type is used for scrolls. It leverages the following properties: |
Revision as of 21:44, 5 November 2010
Type definitions are the equivalent of EVENTS that can be attached to items. There are different properties that can be used to attach a type block to an item or set of items:
- item definitions via their TYPE and/or TEVENTS property.
- items via their TYPE and/or EVENTS property.
In addition to handling triggers, type definitions can also be used to define different types of terrain. This can be used to affect the return value of the TYPE property on map points, or for some hardcoded types such as t_rock it can be used to define which terrain IDs Sphere should consider to be rock when the mining skill is used.
Built-in Types
The built-in types are all listed in the sphere_defs.scp file. The table below only lists some of the built-in types and it is VERY weak on actual details...so use with care.
DEFNAME | Number | Description |
---|---|---|
t_normal | 0 | No built-in behavior. |
t_container and t_container_locked | 1 and 2 | These types are used for containers. They leverage the following properties:
|
t_door or t_door_unlocked | 3 or 4 | This type is used for both locked and unlocked doors. They leverage the following properties:
|
t_key | 5 | This type is used for keys. It leverages the following properties:
Note: Keys, containers, and doors are interesting. If both a key and a door/container contain the same arbitrary MORE1 value, the key can be used to lock or unlock the door/container. That action changes the TYPE of the door/container to indicate whether it is locked or not. It also seems like LINK on the key can be set to the UID of a multi so that it can be used to open all doors/containers inside that multi. |
t_light_lit | 6 | This type is used for light sources that can be turned on or off. It leverages the following properties:
|
t_light_out | 7 | This type is used for light sources that can be turned on or off. It leverages the following properties:
|
t_food | 8 | This type is used for edible food. It leverages the following properties:
|
t_food_raw | 9 | This type is used for raw food. It leverages the following properties:
|
t_armor | 10 | This type is used for armor. It leverages the following properties:
Note: Old versions of sphere stored remaining charges in MORE2, this is no longer true. |
t_weapon_mace_smith | 11 | This type is used for macefighting weapons that can also be used by blacksmiths to forge items. It leverages the following properties:
The following overrides can be set on a per item basis:
|
t_weapon_mace_sharp | 12 | This type is used for macefighting weapons that have sharp cutting edges. It leverages the following properties:
The following overrides can be set on a per item basis:
|
t_weapon_sword | 13 | This type is used for swordsmanship weapons. It leverages the following properties:
The following overrides can be set on a per item basis:
|
t_weapon_fence | 14 | This type is used for fencing weapons. It leverages the following properties:
The following overrides can be set on a per item basis:
|
t_weapon_bow | 15 | This type is used for archery weapons (bow or crossbow). It leverages the following properties:
The following overrides can be set on a per item basis:
|
t_wand | 16 | This type is used for magic wands. It leverages the following properties:
|
t_telepad | 17 | This type is used for teleport pads. It leverages the following properties:
|
t_switch | 18 | This type is used for switches. The way these things work is, when used, they trigger @DCLICK on the LINK object. It leverages the following properties:
|
t_book | 19 | This type is used for books of static or dynamic text. It leverages the following properties:
Note: we need more information on those flags... |
t_rune | 20 | This type is used for recall runes. It leverages the following properties:
|
t_booze | 21 | This type is used for alcohol (it causes a drunk effect when double clicked.) It leverages the following properties:
|
t_potion | 22 | This type is used for potions. It leverages the following properties:
|
t_fire | 23 | This type is used for fires (and ovens?). These items can be used to cook food, and they can burn you if stepped on. It leverages the following properties:
|
t_clock | 24 | This type is used to tell time (game time, not real time) when double clicked. The result comes out something like "half past eleven o'clock at night". From what I can tell there are no MORE or TDATA modifiers that affect the result. |
t_trap and t_trap_active | 25 and 26 | These types are used for traps that are triggered when walked on. They leverage the following properties:
|
t_musical | 27 | This type is used for musical instruments. It leverages the following properties:
|
t_spell | 28 | This type is used for magic spell effects. It leverages the following properties:
|
t_gem | 29 | This type is used for gems, and from what I can tell there is no built-in behavior for it. |
t_water | 30 | This type is used for water, which means it can be fished in or used to clean used bandages.
|
t_clothing | 31 | This type is used for all cloth based equip-able items. It is essentially identical to t_armor and t_armor_leather. It leverages the following properties:
Note: Old versions of sphere stored remaining charges in MORE2, this is no longer true. |
t_scroll | 32 | This type is used for scrolls. It leverages the following properties:
|
... | 33-37 | FIXME!!! |
t_shrine | 38 | This type is used for shrines. Will resurrect a ghost when double-clicked by a ghost. |
t_moongate | 39 | This type is used for moongates. When stepped on they teleport the player to another location. It leverages the following properties:
|
... | 40-41 | FIXME!!! |
t_ore | 42 | This type is harvested by miners, and converted by blacksmiths (using a forge) into something else. It leverages the following properties:
|
... | 43 | FIXME!!! |
t_tree | 44 | This type is chopped by lumberjacks to get logs. It leverages the following properties:
|
... | 45-64 | FIXME!!! |
t_crops | 65 | This type is used to grow plants that likely bear fruit. Double clicking a t_crop item will harvest the fruit if it is ripe. It leverages the following properties:
Note This type has unusual TIMER behavior in that regardless of the ATTR flags, the timer will restart when it reaches zero. |
... | 66-84 | FIXME!!! |
t_seed | 84 | This type is used for seeds. A seed can be created by using a dagger on a fruit (assuming the fruit is setup to have a seed.) A seed can be planted by double clicking it and targeting the ground (specifically t_dirt items). It leverages the following properties:
|
... | 85-114 | FIXME!!! |
t_deed | 115 | This type is used to create something else when double clicked. It is perhaps the best solution for a player to place a multi part item like a house. When double clicked, it will prompt for a target location. It leverages the following properties:
|
... | 116-128 | FIXME!!! |
t_fruit | 129 | This type is used for fruit. When double clicked, fruit will be eaten. Fruit can be grown from crops (t_crop). It leverages the following properties:
|
... | 130-144 | FIXME!!! |
t_foliage | 145 | This type is very similar to t_crops, the difference being the foliage does not disappear when the fruit is harvested. It leverages the following properties:
Note This type has unusual TIMER behavior in that regardless of the ATTR flags, the timer will restart when it reaches zero. |
... | 146-175 | FIXME!!! |
t_eq_script | 176 | This type can have tags and can be equipped. Possibly used for memory objects that leverage @Equip and @UnEquip triggers. |
... | 177-182 | FIXME!!! |
t_script | 183 | This type can have tags, but can NOT be equipped. |
Scripted TYPEDEFs
DEFNAME | File | Description |
---|---|---|
t_advance_gate | ??.scp | MORE = ID of character to change into |
Syntax
The syntax for defining a type is:
[TYPEDEF defname]
TERRAIN=id
TERRAIN=start_id, end_id
ON=trigger_name
script
ON=trigger_name
script
Any number of triggers can be handled by one TYPEDEF definition, however it is not possible to handle the same trigger twice without using multiple definitions.
The trigger name can be the name of any item trigger. The return value from the script can affect Sphere's hardcoded behaviour in different ways. See the documentation for the trigger to discover what parameters are passed in to each trigger and what the return values do.
Note: If the defname matches any of Sphere's hardcoded types (see 'typedefs' block in sphere_defs.scp), then the TYPEDEF can be used to override the behaviours of items of that type.
Examples
// // Water definition from default script pack. // [TYPEDEF t_water] TERRAIN = 0a8 0ab TERRAIN = 0136 0137
// // Makes an item speak when double clicked. // [TYPEDEF t_exampletype] ON=@DClick SAY I have been double clicked! RETURN 2