Overview of errors
This article will, in the end, contain all possible script related errors, what their causes are and what you should do to fix them.
Definition of Error
The errors mentioned in this article, are all the possible script related errors that show in the map-server's console. These errors are often accompanied by a tag in front of it. The tag will be [Error] or [Fatal Error]. Fatal errors mean that it will crash your server.
Also, the errors that display a part of a script with *'s in front of it will be covered in this article. They are called [Parsing Errors].
Please do note that you must be in debugging mode, which is if I'm not mistaking, the default mode. This article will not cover the different kinds of script related warnings, because the error-list alone is already massive.
How do I find and fix my error?
Fixing errors in scripts require some handiness. Single errors are easy to do, but sometimes, you get a lot of errors. Do not be afraid then though, because a large list of errors will often be fixed, by fixing the first error. So, when using this guide, search for the topmost error in your server's console first, and try to fix it. If it is fixed, there is a 50% chance that all the other errors will disappear.
Sometimes though, the amount of errors are so huge, that you cannot scroll high enough to find the first error. If this is the case, then there are three ways to make it easier for you:
Fetch the error stream and save it to a file
Comment out the newly added NPCs, or only make the newly added NPCs load.
Divide your NPCs into smaller NPCs.
How to do the first, I am afraid to say, I forgot. The second one is fairly easy though. Removing your new scripts from the conf files, and starting up your server then, will tell you where to look. If the errors are gone, then they are most likely in your new scripts. Otherwise, they are in the default scripts. If they are in your new scripts, then it is wise to first read to that script again, to remove obvious errors. Also, always check the header. If you make a single mistake in the header, the rest of the script will bug out. If that still doesn't help, decrease the error list, then consider to have your server only load the new scripts, one at the time, in the hope that it will show fewer errors.
However, if that still doesn't allow you to find the topmost error, then there is always the third option - breaking down your script in smaller NPCs. What this means, is that you just randomly put inside your script a } followed by a valid header. Then you've split your script in two halves. 50% chance that 50% of the errors will be gone, and that you are closer to finding the solution. If the error list is still too long, simply split it up again, and again, and again, until you can see all the errors of a single NPC in your screen. That way, you can find the first error in that specific NPC, and fix it. This will result into the mapserver only showing the errors in the broken down NPCs before that NPC. I know, it's a long method, but sometimes, it's the only way. But when you have found the original error, then you can use this guide to find a solution for it.
How will the overview of errors be discussed?
Each error will have it's own section, in which the exact error is listed. These sections will also contain an explanation on what likely caused this error and what possible fixes are. This all is accompanied by one or more examples, to make everything more clear.
To quickly find your specific error, search for a part of the error message, of course, without the Error tag. When searching for it, make sure that you do not include the things that can alter, like NPC name, file name, variable name etc.
How and where do I look for cases relevant to my error?
If the error you want to search for, almost completely contains custom things, like that NPC name etc, and you still want to look for it, then try replacing all the parts that can change by three dots. For example if you want to search for this error:
Out of range spawn coordinates: prt_fild08 (-50,-50), map size is (250,250)
then try using this to search for:
Out of range spawn coordinates: ... (...,...), map size is (...,...)
If this still doesn't give any results, you can always try the main index list. However, older error lines do not show up in this one. So, if you are also unsuccessful there, then please try the [[#Outdated Errors|Outdated Errors]] section as a last resort. It lists all old error message. If you still cannot find it, then you can always try the Scripting Support forum.
Using Older GIT Revisions
You are probably not using the latest version of Hercules. Unfortunately, over time, some errors change in text, or even become obsolete (erased). To not put you in a disadvantage, we will keep track of older error reports. At the moment, we have up to Revision 12340 covered for the script.c related errors, and up to 11501 covered for npc.c related errors.
When time comes, we will try to cover even older errors, and change the list if new errors appear, or when they change in syntax. However, if the error that you are looking for, is not in the normal list, nor the Outdated Errors list, then your best chance is asking for support in the Script Support Forum on the forums. Please, do not forget to mention your GIT revision when doing this.
Overview of Errors
There is a total of over 152 errors at the moment. Currently, 152 of them are covered. This is 100.00% of the total for the script.c section and an unknown percentage for the npc.c section.
Outdated Errors
This list contains all currently known old errors messages that have been changed. They will link you to the current version of the error.
Up to Revision 10812
[[Overview_of_Errors#script:guardian:invalid_data_type_for_argument .236_.28from_1.29|buildin_guardian: invalid data type for argument #8 (...).]]
[[Overview_of_Errors#script:input:_not_a_variable script:|buildin_input: given argument is not a variable!]]
[[Overview_of_Errors#script:set:_not_a_variable|script: buildin_set: not name]]
[[Overview_of_Errors#script:callsub:_argument_is_not_a_label|script: callsub: not label !]]
[[Overview_of_Errors#script:getvariableofnpc:can.27t_find_npc ... script:|getvariableofnpc: can't find npc ...]]
[[Overview_of_Errors#script:getvariableofnpc:_not_a_variable|script: getvariableofnpc: first argument is not a variable name]]
[[Overview_of_Errors#script:getvariableofnpc:invalid_scope .28not_npc_variable.29|script: getvariableofnpc: invalid scope ... (not npc variable)]]
[[Overview_of_Errors#script:goto:_not_a_label|script:goto: not label!]]
[[Overview_of_Errors#script:menu:argument .23..._.28from_1.29_is_not_a_label_or_label_not_found.|script:menu: argument #... (from 1) is not a label or label not found (op=...).]]
[[Overview_of_Errors#script:menu:argument .23..._.28from_1.29_is_not_a_string_or_compatible.|script:menu: argument #... (from 1) is not a string or compatible (op=...).]]
[[Overview_of_Errors#script:op_1:argument_is_not_a_number .28op.3D....29|script:op_1: invalid type of data op:... data:...]]
[[Overview_of_Errors#script:op_1:unexpected_operator ..._i1.3D...|script:op_1: unexpected operator op:...]]
[[Overview_of_Errors#script:op_2:invalid_data_for_operator ...|script:op_2: invalid type of data op:... left:... right:...]]
[[Overview_of_Errors#script:op_2num:_division_by_zero_detected_op.3D..._i1.3D..._i2.3D...|script:op_2num: division by zero detected op:...]]
[[Overview_of_Errors#script:op_2num:unexpected_number_operator ..._i1.3D..._i2.3D...|script:op_2num: unexpected number operator op:...]]
[[Overview_of_Errors#script:op2_str:unexpected_string_operator ...|script:op2_str: unexpected string operator op:...]]
[[Overview_of_Errors#script:op_3:_invalid_data_for_the_ternary_operator_test|script:op_3: invalid type of data op:... data:...]]
[[Overview_of_Errors#script:warpportal:_npc_is_needed|script:warpportal: npc is needed]]
In-depth Info on Errors
The following details the different kinds of errors emanating from the source code (script.c, npc.c, etc.).
Warnings in script.c
Warnings do not necessarily mean, that something is wrong, but can work in an undesired way.
Unexpected type for argument ... Expected ...
Cause
The data type of the value passed into a build-in function's argument differs from the one defined in that function's BUILDIN_DEF definition, typically passing a number where a string is expected and vice versa.
A set of [Debug] messages follow this warning, that specify the function's parameters, the function itself and the NPC that hosts the reported script. This warning occurs only during runtime of a script.
Note, that the affected script continues to run and auto-conversion rules apply, except the script command itself stops the execution of the script (typically commands that deal with variables and labels).
Solution
Verify all values passed to the function and make sure, that all of them have the expected type.
Example
An npc script or item script that contains:
The first parameter is supposed to be a number (amount of HP to heal). So the correct script would be:
Errors (npc.c)
All errors located in npc.c that have the [Error] tag are listed in this section.
bad duplicate name (in ...)! : ...
Source Syntax
Cause
The format of your duplicate line is wrong. What is missing, is either which NPC the duplicate command should copy or the use of an incorrect name or incorrect characters. The error is located in the file that is mentioned between the ( and ). The name that the server found, if any there, is displayed after the : .
Solution
Make sure that you have put an event label in the duplicate name. The format should be one of the following two:
Example (Wrong)
The last line is missing the event label between the brackets:
Example (Correct)
bad duplicate name (in ...)! (not exist) : ...
Source Syntax
Cause
This error is trying to tell you that you are duplicating a non-existing NPC.
Solution
Make sure that the NPC you want to duplicate, has the same Event Label as you specified between the round brackets behind duplicate. Either correct the Event Label of the original NPC or the Event Label in the duplicate line.
Or, erase the duplicate line. Remember, the format for the original NPC is:
And for the duplicate:
Example (Wrong)
The first line is missing the event label between the brackets:
Example (Correct)
Reformatting of this document (from MediaWiki to Markdown) has reached only up to this part of this document (December 2018).
Documentation below this section is not yet finished the reformatting process. For future maintainers, please follow a similar format to the ones above for readability purposes.
Beyond this point, the document has been partially adjusted to use Markdown but is not yet finished.
This partial commit was submitted because the previous MediaWiki version of this document was too large and difficult to render that the Github Wiki just gave up. This partial commit allows the page to be visible, thus giving access to this wealth of information.
bad monster ID : ... ... (file ...)
Source Syntax
Cause
The monster you are trying to spawn, does not exist. At least, the mapserver could not find it's mob_id in mob_db.txt or mob_db2.txt. (Or possibly not in the homunculus db.)
Solution
Either add the monster to the mob_db2.txt file, or change the mob_id number in the spawn line to the correct mob_id number.
Example
Wrong code:
monster "prt_fild08",100,100,"Poring",999,5;
Correct code:
monster "prt_fild08",100,100,"Poring",1002,5;
bad monster line : ... ... ... (file ...)
Source Syntax
Cause
For a monster line to be correct, it needs to have at least the following:
* Valid mapname
* Valid x
* Valid y
And it also needs to have at least:
* Valid class
* Valid amount
If you only have two or less of the topmost, and/or 1 or less of the bottom two, then this error will occur.
Solution
Make sure that your monster line contains at least the needed information. Check if you have a mapname, x, y, mob_id and an amount, and correct it where needed.
Example
Wrong code:
monster "prt_fild08","Poring",5;
Correct code:
monster "prt_fild08",0,0,"Poring",1002,5;
bad script line (in file ...): ...
Source Syntax
Cause
This error occurs when the header of your NPC is incorrect. There are two separate ways for a NPC header to function correctly:
map,x,y,dscriptNamesprite,{
-scriptName-1,{
When the server does not detect a dash (-) at the start of your header, it will check for the other format. If it does not find a mapname, x, y, direction, the word script or a comma after the sprite, then it will give you this error.
Solution
Recheck, if you abide the rules of writing a NPC header. Make sure you have all the commas in the right spots, that you have the location setup correctly and that you are using the script identifier word.
Example
Wrong code:
prontera,200,200scriptMy NPC48,{
Correct code:
prontera,200,200,4scriptMy NPC48,{
bad setcell line : ...
Source Syntax
Cause
You did not obey the format for using the setcell command. The format should be:
%TAB%setcell%TAB%,,,,
This error occurs when you forgot one of the following five things:
* Forgot to define the type.
* Forgot to define x1
* Forgot to define y1
* Forgot to define x2
* Forgot to define y2
### Solution
Recheck, if the way you defined your setcell line is correct. There should be a tab, followed by 5 arguments after the setcell keyword.
### Example
Wrong code:
pronterasetcellcell_wall,170,50,171
Correct code:
pronterasetcellcell_wall,170,50,171,100
## bad shop line : ...
### Source Syntax
shopNamesprite,{item list + prices}
This error occurs when you are missing the mapname, x, y and/or direction.
### Solution
Recheck if you are using the shop header in the correct way. Add the missing mapname, x-coordinate, y-coordinate and/or direction.
### Example
Wrong code:
prontera,100,100shopMy First Shop83,501:-1,502:-1,503:-1,504:-1,506:-1
Correct code:
prontera,100,100,4shopMy First Shop83,501:-1,502:-1,503:-1,504:-1,506:-1
## bad warp line : ...
### Source Syntax
warpNametrigger_x,trigger_y,to_map,to_x,to_y
This error occurs when you are missing one of the parameters given after the name. (Destination map and coordinates and trigger size.)
### Solution
Recheck if you are using the warp header in the correct way. Add what is missing.
### Example
Wrong code:
prontera,107,215,0warpprt01prt_in,240,139
Correct code:
prontera,107,215,0warpprt012,2,prt_in,240,139
## bad warp line (destination map not found): ...
### Source Syntax
warpprt01prontera_in,240,139
Correct code:
prontera,107,215,0warpprt01prt_in,240,139
## Could not parse file '...', line '...'. * ... ... ... ...
### Source Syntax
: . Before the : will tell you exactly where your global variables are being stored.
### Solution
The best solution is to manually fix the broken variable. To do this, make sure that your server is completely offline. Then open the file where the global variables are located. Then search for the specific global variable. When you have found the bugged one, either erase it from the file, or give it a correct value (and if needed, array-index). If it is an important variable, you are advised to look in your most recent backup, and use that value as the new value for the broken variable. When you are done, save the file, exit it, and restart your server to see if the error is fixed.
## buildin_callshop: Shop [...] not found (or NPC is not shop type)
### Source Syntax
,,"mapname",,,,;
where coverage >= 23.
If you intended to use a predefined area, make sure that the numerical value of coverage is smaller than 23. To check this, open up db/const.txt, and look up the values behind the bc_ entries. Add up the numbers of the bc's that you used, to see if it stays under 23.
## buildin_warp: moving player '...' to "...",...,... failed.
### Source Syntax
[%s] \n", cfgName);
; or if the code in advance of the function/sub isn't properly ended. This last thing can happen when you have some code above the sub or function, which doesn't have a close; or end; at the end.
## script:getarraysize: illegal scope
### Source Syntax
",,,"",;
guardian "",,,"",,"";
guardian "",,,"",,;
guardian "",,,"",,"",;
In essence, this means, that your event label and/or guardian index is not respectively a string and/or an integer. (The index needs to be an integer, the event label needs to be a string.)
### Solution
Check if you are using the correct type for the specific argument you want to use. Make sure that the sixth argument really is a string or an integer.
## script:input: not a variable
### Source Syntax
Current: ShowError("script:input: not a variable\n");
Until Rev. 10812: ShowError("script: buildin_input: given argument is not a variable!\n");
### Cause
You tried to use input on a variable which isn't a variable. This means that you are naming your variable wrong, or that you typed the name of a command, label, function or subroutine.
### Solution
Verify that you are obeying the rules for variable naming, and that the name you use isn't already taken by any command, label, function or subroutine.
## script:menu: argument #... (from 1) is not a label or label not found.
### Source Syntax
Current: ShowError("script:menu: argument #%d (from 1) is not a label or label not found.\n", i);
Until Rev. 10812: ShowError("script:menu: argument #%d (from 1) is not a label or label not found (op=%s).\n", i, script_op2name(data->type));
### Cause
The target label you provided for a specific menu option, is not a correct label name, or does not exist. Please note that in a menu, the dash (-) is a valid replacement for a label.
### Solution
Verify that the reported label does exist, and is correctly typed, and that it also obeys the rules for label naming.
## script:menu: illegal number of arguments (...).
### Source Syntax
_ Cause_
An in-script function was used or declared in an invalid manner.
_ Solution_
You tried to write or use an in-script function. The normal format for this is one of the following two:
function test; // Calls upon in-script function test.
function test { // Declaration of a function including needed code.
// Function code goes here.
}
In your case, the script parser encountered something else than the allowed { or ; after the function's name. Recheck your in-script function, and make sure it either has a ; or a { at the end of the line.
## need '('
### Source Syntax
_ Cause_
In your script, there is a function that you are trying to call. This function requires it's arguments to be between round brackets. Your script is lacking at least the left one ('('), and most likely both.
_ Solution_
Search inside your script for the function call displayed by the error. Fix it by making sure there are parentheses around the arguments.
_ Example_
Wrong code:
...
set .var, SF_DummyFunction 5, 7;
...
Correct code is:
...
set .var, SF_DummyFunction(5, 7);
...
## not found '{'
### Source Syntax
{ '. This left curly bracket specifies the start of the body of the script, and must be on the same line as your header.
### Solution
If you forgot to place a { at all, then place it at the end of the header line. If you placed the opening curly bracket at the next line, then move it until it is at the same line as the header.
### Example
Wrong code:
prontera,200,200,4scriptDummy46,
{
mes "hi";
close;
}
It should be:
prontera,200,200,4scriptDummy46,{
mes "hi";
close;
}
## parse_callfunc: callsub has no arguments, please review it's definition
### Source Syntax