diff options
Diffstat (limited to 'doc/script_commands.txt')
| -rw-r--r-- | doc/script_commands.txt | 70 |
1 files changed, 2 insertions, 68 deletions
diff --git a/doc/script_commands.txt b/doc/script_commands.txt index 556401d2f..3467a5366 100644 --- a/doc/script_commands.txt +++ b/doc/script_commands.txt @@ -2056,28 +2056,6 @@ else if (<condition 2>) { --------------------------------------- -*jump_zero (<condition>),<label>; - - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - @ /!\ This command is deprecated @ - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - -This command is deprecated and it should not be used in new scripts, as it is -scheduled to be removed at any time on or after November 27th, 2014. Please -consider using 'if', 'switch', 'for', 'while', as appropriate. - -This command works like an 'if'+'goto' combination in one go. (See 'if'). -If the condition is false (equal to zero) this command will immediately -jump to the specified label like in 'goto'. - -This command should not be used in scripts directly. - -The main reason for this command is that other control statements, like -'switch', 'for' or 'while', are disassembled into simple expressions -together with this command when a script is parsed. - ---------------------------------------- - *while (<condition>) <statement>; This is probably the simplest and most frequently used loop structure. The @@ -8106,8 +8084,7 @@ decision-making for the current pet of the invoking character, and will NOT have any independent effect by themselves, which is why only one of them each may be in effect at any time for a specific pet. A pet may have 'petloot', 'petskillbonus', 'petskillattack' OR 'petpetskillattack2' -and 'petskillsupport' OR 'petheal' at the same time. 'petheal' is -deprecated and is no longer used in the default pet scripts. +and 'petskillsupport' at the same time. *petskillbonus <bonus type>,<value>,<duration>,<delay>; @@ -8138,16 +8115,6 @@ time between activations. The skill numbers are as per It's not quite certain who's stats will be used for the skills cast, the character's or the pets. Probably, Skotlex can answer that question. -*petheal <level>,<delay>,<percent hp>,<percent sp>; - - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - @ /!\ This command is deprecated @ - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - -The petheal command is deprecated and it should not be used in new scripts, as -it is scheduled to be removed after November 27th, 2014. Please consider using -petskillsupport by specifying the AL_HEAL skill id instead. - *petskillattack <skill id>,<skill level>,<rate>,<bonusrate>; *petskillattack "<skill name>",<skill level>,<rate>,<bonusrate>; *petskillattack2 <skill id>,<damage>,<number of attacks>,<rate>,<bonusrate>; @@ -8539,7 +8506,7 @@ that fails, the command returns an empty string instead. *questinfo <Quest ID>, <Icon> {, <Map Mark Color>{, <Job Class>}}; -This is esentially a combination of checkquest and showevent. Use this only +This is esentially a combination of questprogress and showevent. Use this only in an OnInit label. For the Quest ID, specify the quest ID that you want checked if it has been started yet. @@ -8615,39 +8582,6 @@ Add quest of the <ID2> to the the quest log, and the state is "active". --------------------------------------- -*checkquest(<ID>{,PLAYTIME|HUNTING}) - - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - @ /!\ This command is deprecated @ - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ - -This command is deprecated and it should not be used in new scripts, as it -is scheduled to be removed on or after November 28th, 2014. Please consider -using questprogress() instead. Or, in special cases, questactive(). - -If no additional argument supplied, return the state of the quest: - -1 = Quest not started (not in quest log) - 0 = Quest has been given, but the state is "inactive" - 1 = Quest has been given, and the state is "active" - 2 = Quest completed - -If parameter "PLAYTIME" is supplied: - -1 = Quest not started (not in quest log) - 0 = the time limit has not yet been reached - 1 = the time limit has not been reached but the quest is marked as - complete - 2 = the time limit has been reached - -If parameter "HUNTING" is supplied: - -1 = Quest not started (not in quest log) - 0 = you haven't killed all of the target monsters and the time limit - has not been reached. - 1 = you haven't killed all of the target monsters but the time limit - has been reached. - 2 = you've killed all of the target monsters - ---------------------------------------- - *questprogress(<ID>{,PLAYTIME|HUNTING}) If no additional argument supplied, return the state of the quest: |