Diana Coat [1] ( Diana_Suits )
| ID 15430 |
|
|||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Prix d'achat: zeny | Prix de vente: 0 zeny | Poids: 30 | Emplacements: 1 | ||||||||||||||||||||||||||||||||||||
| Type: Armure/Vêtement/Bottes/Coiffure/Accessoire. | Sous-type: Non spécifié | Genre: Les deux | Lieux: Armure | |||||||||||||||||||||||||||||||||||||
| Attaque: Non spécifié | Attaque magique: Non spécifié | Portée: Non spécifié | Défense: Non spécifié | |||||||||||||||||||||||||||||||||||||
| Niveau d'arme: Non spécifié | Niveau d'armure: 1 | Niveau d'équipement min.: 100 | Niveau d'équipement max.: Non spécifié | |||||||||||||||||||||||||||||||||||||
| Affûtage: 1 | Améliorable: Non spécifié | Élément: Neutre | Classes: Non spécifié | |||||||||||||||||||||||||||||||||||||
|
An extravagant suit modeled after one of the twelve legendary pantheon. Non spécifié
Drapeaux
Empilement
Non spécifié
Utilisation
Non spécifié
Commerce
Délai
Non spécifié
.@r =getrefine();
bonus bDex,3*(.@r/4);
bonus bMaxHPrate,3*(.@r/4);
bonus2 bSkillCooldown,"SU_LOPE",-1000*(.@r/4);
if (.@r>=12) {
bonus2 bSkillCooldown,"SU_PURRING",-20000;
autobonus "{ bonus bDex,80; }",50,5000;
autobonus3 "{ bonus bMatk,100; }",1000,3000,"SU_SV_ROOTTWIST";
}
Références du Script
getrefine
Commande
getrefine
Signature:
Description:
function is called.
This function is intended for use in item scripts.
bDex
Bonus d’Objet
bDex
Signature:
Description:
DEX + n
bMaxHPrate
Bonus d’Objet
bMaxHPrate
Signature:
Description:
MaxHP + n%
bSkillCooldown
Bonus d’Objet
bSkillCooldown
Signature:
Description:
Increases cooldown of skill sk by t milliseconds
if
Commande
if
Signature:
Description:
This is the basic conditional statement command, and just about the only one
available in this scripting language.
The condition can be any expression. All expressions resulting in a non-zero
value will be considered True, including negative values. All expressions
resulting in a zero are false.
If the expression results in True, the statement will be executed. If it isn't
true, nothing happens and we move on to the next line of the script.
For more information on conditional operators see the operators section above.
bothering to store it in a specific variable:
More examples of using the 'if' command in the real world:
Example 1:
Example 2:
Notice that examples 1 and 2 have the same effect.
Example 3:
Example 4:
Example 5:
See 'strcharinfo' for an explanation of what this function does.
Example 6: Using complex conditions.
The script engine also supports nested 'if' statements:
If the condition isn't met, it'll do the action following the 'else'.
We can also group several actions depending on a condition:
Remember that if you plan to do several actions upon the condition being false, and
you forget to use the curly braces (the { } ), the second action will be executed regardless
the output of the condition, unless of course, you stop the execution of the script if the
condition is true (that is, in the first grouping using a return; , and end; or a close; )
Also, you can have multiple conditions nested or chained.
Exemple:
autobonus3
Commande
autobonus3
Signature:
Description:
These commands are meant to be used in item scripts only! See 'petautobonus' for pet usage.
What these commands do is 'attach' a script to the player which will get
executed on attack (or when attacked in the case of autobonus2).
Rate is the trigger rate of the script (1000 = 100%).
Duration is the time in milliseconds that the bonus will last for since the script has triggered.
Skill ID/skill name the skill which will be used as trigger to start the bonus. (autobonus3)
The optional argument 'flag' is used to classify the type of attack where the script
can trigger (it shares the same flags as the bAutoSpell bonus script):
Range criteria:
Attack type criteria:
Skill criteria:
The difference between the optional argument 'other script' and the 'bonus script' is that,
the former one triggers only when attacking(or attacked) and the latter one runs on
status calculation as well, which makes sure, within the duration, the "bonus" that get
lost on status calculation is restored. So, 'bonus script' is technically supposed to accept
"bonus" command only. And we usually use 'other script' to show visual effects.
In all cases, when the script triggers, the attached player will be the one
who holds the bonus. There is currently no way of knowing within this script
who was the other character (the attacker in autobonus2, or the target in
autobonus and autobonus3).
//Grants a 1% chance of starting the state "all stats +10" for 10 seconds when
//using weapon or misc attacks (both melee and ranged skills) and shows a special
//effect when the bonus is active.
Exemple:
bMatk
Bonus d’Objet
bMatk
Signature:
Description:
Magical attack power + n
Non spécifié Références du ScriptAucune référence documentée n’a été détectée dans ce script. Non spécifié Références du ScriptAucune référence documentée n’a été détectée dans ce script. Non spécifié Non spécifié Non spécifié
Non spécifié Non spécifié Non spécifié Non spécifié |
||||||||||||||||||||||||||||||||||||||||