SphereWiki - User contributions [en]

LAYER

2010-07-31T19:03:26Z

Crafty: Created page with '=Paperdoll= {| border="1" cellspacing="4" cellpadding="4" | '''Layer ID''' || '''Default Layer Defname''' || '''Description''' |- | 1 || layer_hand1 || |- | 2 || layer_hand2 || |...'

=Paperdoll=
{| border="1" cellspacing="4" cellpadding="4"
| '''Layer ID''' || '''Default Layer Defname''' || '''Description'''
|-
| 1 || layer_hand1 ||
|-
| 2 || layer_hand2 ||
|-
| 3 || layer_shoes ||
|-
| 4 || layer_pants || bone legs + pants
|-
| 5 || layer_shirt ||
|-
| 6 || layer_helm ||
|-
| 7 || layer_gloves ||
|-
| 8 || layer_ring ||
|-
| 9 || layer_talisman || talisman (se and ml)
|-
| 10 || layer_collar || gorget or necklace
|-
| 11 || layer_hair ||
|-
| 12 || layer_half_apron ||
|-
| 13 || layer_chest || armor chest
|-
| 14 || layer_wrist || watch
|-
| 15 || layer_light || a itemid_light_src equip item can be put here
|-
| 16 || layer_beard ||
|-
| 17 || layer_tunic || jester suit or full apron
|-
| 18 || layer_ears || earrings
|-
| 19 || layer_arms || armor
|-
| 20 || layer_cape || cape
|-
| 21 || layer_pack || only used by itemid_backpack
|-
| 22 || layer_robe || robe over all
|-
| 23 || layer_skirt || skirt or kilt
|-
| 24 || layer_legs || plate legs
|}

=Others=
these are not part of the paper doll (but get sent to the client)
{| border="1" cellspacing="4" cellpadding="4"
| '''Layer ID''' || '''Default Layer Defname''' || '''Description'''
|-
| 25 || layer_horse || ride this object. (horse objects are strange?)
|-
| 26 || layer_vendor_stock || the stuff the vendor will restock and sell to the players
|-
| 27 || layer_vendor_extra || the stuff the vendor will resell to players but is not restocked. (bought from players)
|-
| 28 || layer_vendor_buys || the stuff the vendor can buy from players but does not stock
|-
| 29 || layer_bankbox || contents of my bank box
|}

internally used layers - don't bother sending these to client.
{| border="1" cellspacing="4" cellpadding="4"
| 30 || layer_special || can be multiple of these. memories
|-
| 31 || layer_dragging ||
|}

=Spells=
{| border="1" cellspacing="4" cellpadding="4"
| 32 || layer_spell_stats || stats effecting spell. these cancel each other out
|-
| 33 || layer_spell_reactive ||
|-
| 34 || layer_spell_night_sight ||
|-
| 35 || layer_spell_protection ||
|-
| 36 || layer_spell_incognito ||
|-
| 37 || layer_spell_magic_reflect ||
|-
| 38 || layer_spell_paralyze || or turned to stone
|-
| 39 || layer_spell_invis ||
|-
| 40 || layer_spell_polymorph ||
|-
| 41 || layer_spell_summon || magical summoned creature
|}

=Flags=
{| border="1" cellspacing="4" cellpadding="4"
| 42 || layer_flag_poison ||
|-
| 43 || layer_flag_criminal || criminal or murderer ?
|-
| 44 || layer_flag_potion || some magic type effect done by a potion. (they cannot be dispelled)
|-
| 45 || layer_flag_spiritspeak ||
|-
| 46 || layer_flag_wool || regrowing wool
|-
| 47 || layer_flag_drunk || booze effect
|-
| 48 || layer_flag_clientlinger ||
|-
| 49 || layer_flag_hallucination || shrooms etc
|-
| 50 || layer_flag_potionused || track the time till we can use a potion again
|-
| 51 || layer_flag_stuck || in a trap or web
|-
| 52 || layer_flag_murders || how many murders do we have ? and decay timer
|-
| 53 || layer_flag_bandage || bandages go here for healing
|}

[[Category:Reference Compendium]]

Category:Statements

2010-02-07T15:49:27Z

Crafty:

{| border="1" cellspacing="4" cellpadding="4"
| '''Statement''' || '''End Statement''' || '''Description'''
|-
| [[BEGIN]] || END || Groups a set of lines together, for use with [[DORAND]] and [[DOSWITCH]] statements.
|-
| [[DORAND]] ''line_count'' || ENDDO || Executes a random line of code within the block.
|-
| [[DOSWITCH]] ''line_number'' || ENDDO || Executes the specified line of code within the block.
|-
| [[FOR]] ''start end'' || ENDFOR || Loops through the block of code
|-
| [[FORCHARLAYER]] ''layer_id'' || ENDFOR || Loops through all items that a character has equipped on a specified layer.
|-
| [[FORCHARMEMORYTYPE]] ''memory_flags'' || ENDFOR || Loops through all memory items on a character that have one of the specified flags.
|-
| [[FORCHARS]] ''distance'' || ENDFOR || Loops through all characters within ''distance'' tiles.
|-
| [[FORCLIENTS]] ''distance'' || ENDFOR || Loops through all connected clients within ''distance'' tiles.
|-
| [[FORCONT]] ''container_uid, max_subcontainers'' || ENDFOR || Loops through all items inside a container.
|-
| [[FORCONTID]] ''item_id, max_subcontainers'''' || ENDFOR || Loops through all items inside a container with a specified [[BASEID]]
|-
| [[FORCONTTYPE]] ''type, max_subcontainers'' || ENDFOR || Loops through all items inside a container with a specified [[TYPE]]
|-
| [[FORINSTANCES]] ''defname'' || ENDFOR || Loops through all instances of characters or items with the specified [[BASEID]]
|-
| [[FORITEMS]] ''distance'' || ENDFOR || Loops through all items within ''distance'' tiles.
|-
| [[FOROBJS]] ''distance'' || ENDFOR || Loops through all items and players within ''distance'' tiles.
|-
| [[FORPLAYERS]] ''distance'' || ENDFOR || Loops through all players (online and offline) within ''distance'' tiles.
|-
| [[IF]] ''condition'' [[IF|ELIF]] ''condition'' [[IF|ELSEIF]] ''condition'' || ENDIF || Executes the block of code if ''condition'' is true.
|-
| [[WHILE]] ''condition'' || ENDWHILE || Loops through the block of code whilst ''condition'' is true.
|-
| <local._for> || || Current Step of the Loop
|}

[[Category: Reference Compendium]]
[[Category: Scripts]]

TYPEDEF

2010-01-12T15:14:52Z

Crafty:

__FORCETOC__
Type definitions are the equivalent of [[EVENTS]] that can be attached to [[Items|items]]. There are different properties that can be used to attach a type block to an item or set of items:
* [[ITEMDEF|item definitions]] via their [[TYPE]] and/or [[TEVENTS]] property.
* [[Items|items]] via their [[TYPE]] and/or [[EVENTS (Property)|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|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.

==Syntax==
The syntax for defining a type is:

<tt>
[TYPEDEF ''defname''] 
TERRAIN=''id'' 
TERRAIN=''start_id'', ''end_id'' 
 
ON=''trigger_name'' 
    ''script'' 
 
ON=''trigger_name'' 
    ''script'' 
 </tt>

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 [[Items#Triggers|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==
<spherescript>
//
// Water definition from default script pack.
//
[TYPEDEF t_water]
TERRAIN = 0a8 0ab
TERRAIN = 0136 0137
</spherescript>

<spherescript>
//
// Makes an item speak when double clicked.
//
[TYPEDEF t_exampletype]
ON=@DClick
SAY I have been double clicked!
RETURN 2
</spherescript>

[[Category: Reference Compendium]]
[[Category: Definitions]]