Hercules Wiki - User contributions [en]

Data Folder Structure

2016-10-04T03:24:58Z

Wolfeh:

== Description ==
This page currently explains the data folder structure as recognized by the client.
 
'''Take note of this''':
¿© (여) is female, ³² (남) is male.

== Data Structure ==
'''data''' Holds various text files, for items, the bard and dancer scream and frost joker skill messages, error messages, map files (.rsw,.gnd,.gat), etc.
:* '''ai''' The '''ai''' in here means "Artificial Intelligence". As the name implies, this contains all the functions for the AIs (Mercenaries and Homunculus).
:* '''book''' Where the contents of books are.
:* '''imf''' Contains files that control the thumbnail views of characters in the Character Selection Screen.
:* '''lua files''' Interface coding.(Old Clients)
:* '''luafiles514''' Just another set of LUA files which are much more updated.
:** '''lua files''' Interface coding.(New Clients)
:* '''model''' Various map model's. Examples of model's are statues, foliage, street lights, ect. Folder also contains various sub folders which are too many to list.
:* '''palette''' Folder body and hair for palettes.
:** '''¸ö (몸)''' Folder for cloth palettes.
:** '''¸Ó¸® (머리)''' Folder for hair palettes.
:* '''sprite''' Base folder for sprites. Has a sprite for a shadow (goes underneath the character?), a numbers sprite for countdowns (or counting for something).
:** '''¸ó½ºÅÍ (몬스터)''' Folder for monster sprites.
:** '''¾ÆÀÌÅÛ (아이템)''' Folder for drop sprites, for items and skills.
:** '''¾Ç¼¼»ç¸® (악세사리)''' Item sprites.
:** '''¹æÆÐ (방패)''' Folder for shield sprites.
:** '''ÀÎ°£Á· (인간족)''' Hair and job sprites base folder.
:*** '''¸öÅë (몸통)''' Job sprites folder.
:*** '''¸Ó¸®Åë (머리통)''' Hair folder.
:** '''ÀÌÆÑÆ® (이팩트)''' Status effects and other effects. Examples are curse, sleep, the time o attack that pops up in PVP.
:** '''book''' Book sprites. Examples are the open book with pages turning, shown when a book can be read.
:** '''homun''' Homunculus sprites.
:** '''npc''' NPC sprites.
:* '''texture''' Folder for various .bmp images, from items to interface and other things like that. The logo is also stored here, the logo is shown in screenshots, on the lower right hand side. Various map textures in main and sub folders, too many to list.
:** '''effect''' Folder for skill effects. Effects have to be .tga format.
:** '''À¯ÀúÀÎÅÍÆäÀÌ½º (유저인터페이스)''' Similar to its main folder, texture. Has the world map, login background, and loading screens as well.
:*** '''basic_interface''' Interface images, buttons and other graphics having to do with menus.
:*** '''battle_field''' Help buttons.
:*** '''cardbmp''' Card images for when you click view in-game or right click the card. Image has to be .bmp format.
:*** '''collection''' Images for items, the image will show up to the left of the description for the item. Has to be .bmp format.
:*** '''illust''' Images for NPCs, pets, and quest images. Examples are kafra, or the flag in the novice grounds. They have to have the transparent pink background, and be .bmp.
:*** '''item''' Images for the items when seen in the inventory. Images have to have the transparent pink background and be .bmp.
:*** '''login_interface''' As the name suggests, the login interface. Images for character selection, and the login screen. Also has some warning images. .bmp format and needs transparency.
:*** '''map''' Map images, the map is displayed in the upper right hand corner.
:* '''wav''' All the game sounds for monsters, and attacks.
:** '''effect''' All the game sounds for skills.
[[Category:Client Configuration]]
[[Category:Data]]
[[Category:Customization]]

Custom NPC

2016-10-04T03:22:16Z

Wolfeh: /* constants.conf */

=Client-side=
==Adding Sprite==
Download the .spr and .act file for the NPC and place them in data/sprite/npc.
==NPCidentity.lub==
Add your NPC to NPCidentity.lub. Most recommend adding new NPC's with ID's starting at 1500, so that there is room for new official sprites without them overlapping your custom ones. The name of the sprite does not have to be capitalized. If the name of the sprite is lowercase, you can add them to all files as lowercase, such as in the example below, the sprite can be JT_NPCNAME or JT_npcname. The last line of this file does not need a comma at the end of the line, but any lines which are not the last line require a comma.

Format:
JT_NPCNAME = 10500

==jobname.lub==
Exact same rules apply to this file. Can be lowercase or uppercase, last line does not have to have a comma. Slightly different format is all that differs from NPCidentity.lub.

Format:
[jobtbl.JT_NPCNAME] = "NPCNAME",

=Server Side=
==constants.conf==
Located in your db folder. Find the NPC list and add your NPC to the bottom.

Format:
NPCNAME: 10500

==npc.h==
npc.h is located in src/map. Open it in notepad or another text editor.

Find:
#define MAX_NPC_CLASS2_END 10203

Change to:
#define MAX_NPC_CLASS2_END 10800

You can make the max larger if you feel it is necessary, but this should give you plenty of room. Save and [[Compiling|recompile]].

[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom NPC

2016-10-04T03:20:29Z

Wolfeh:

=Client-side=
==Adding Sprite==
Download the .spr and .act file for the NPC and place them in data/sprite/npc.
==NPCidentity.lub==
Add your NPC to NPCidentity.lub. Most recommend adding new NPC's with ID's starting at 1500, so that there is room for new official sprites without them overlapping your custom ones. The name of the sprite does not have to be capitalized. If the name of the sprite is lowercase, you can add them to all files as lowercase, such as in the example below, the sprite can be JT_NPCNAME or JT_npcname. The last line of this file does not need a comma at the end of the line, but any lines which are not the last line require a comma.

Format:
JT_NPCNAME = 10500

==jobname.lub==
Exact same rules apply to this file. Can be lowercase or uppercase, last line does not have to have a comma. Slightly different format is all that differs from NPCidentity.lub.

Format:
[jobtbl.JT_NPCNAME] = "NPCNAME",

=Server Side=
==constants.conf==
Located in your db folder. Find the NPC list and add your NPC to the bottom.

Format:
nurse: 10500
==npc.h==
npc.h is located in src/map. Open it in notepad or another text editor.

Find:
#define MAX_NPC_CLASS2_END 10203

Change to:
#define MAX_NPC_CLASS2_END 10800

You can make the max larger if you feel it is necessary, but this should give you plenty of room. Save and [[Compiling|recompile]].

[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom NPC

2016-10-04T03:20:07Z

Wolfeh: Created page with "=Client-side= ==Adding Sprite== Download the .spr and .act file for the NPC and place them in data/sprite/npc. ==NPCidentity.lub== Add your NPC to NPCidentity.lub. Most recomm..."

=Client-side=
==Adding Sprite==
Download the .spr and .act file for the NPC and place them in data/sprite/npc.
==NPCidentity.lub==
Add your NPC to NPCidentity.lub. Most recommend adding new NPC's with ID's starting at 1500, so that there is room for new official sprites without them overlapping your custom ones. The name of the sprite does not have to be capitalized. If the name of the sprite is lowercase, you can add them to all files as lowercase, such as in the example below, the sprite can be JT_NPCNAME or JT_npcname. The last line of this file does not need a comma at the end of the line, but any lines which are not the last line require a comma.

Format:
JT_NPCNAME = 10500

==jobname.lub==
Exact same rules apply to this file. Can be lowercase or uppercase, last line does not have to have a comma. Slightly different format is all that differs from NPCidentity.lub.

Format:
[jobtbl.JT_NPCNAME] = "NPCNAME",

=Server Side=
==constants.conf==
Located in your db folder. Find the NPC list and add your NPC to the bottom.

Format:
nurse: 10500
==npc.h==
npc.h is located in src/map. Open it in notepad or another text editor.

Find:
#define MAX_NPC_CLASS2_END 10203

Change to:
#define MAX_NPC_CLASS2_END 10800

You can make the max larger if you feel it is necessary, but this should give you plenty of room. Save and [[Compiling|recompile]].

Basic Scripting

2016-09-17T22:17:46Z

Wolfeh: Removed any references to NPC ID's. These are no longer recommended and may lose support.

{{outdated}}

==The Basics==

Scripts control all NPCs, warps, mob spawns, shops, and quests you will find in the game--and nearly everything else! Clearly they play a large part in customizing a server, but learning isn't very hard.

Scripts are built up of predefined script commands, all of which can be found in {{git|doc/script_commands.txt}} (for explanations, see [[:Category:Script_Command|Script Commands]]). Every line should begin with a command and the argument it takes, and must end in a semicolon (or you'll get mapserver errors!). Arguments are usually separated by commas, and are sometimes contained in parentheses () or curly brackets {}. Tabs and proper indentation are standard scripting measures.

Scripts are saved as text (*.txt) files, so all code can be written in Notepad. There are also a lot of scripting programs to use: the most recent and comprehensive one is [http://rathena.org/board/topic/56484-enpc-script-editor/ Vince's eNPC]. All defined functions are highlighted, with an autocomplete feature included, and pressing "F1" will display the corresponding explanation for any command.

==Structure==

===NPC===
A '''Script NPC''' will look something like the following:
prontera,156,145,4 <tab> script <tab> Test NPC <tab> 1_M_MERCHANT,{

The first section is the map location of the NPC, followed by its coordinates in x,y and the direction the NPC will face. Direction numbers are counted counterclockwise in 45º increments, with 0 being the center: 

[1][0][7] 
[2][  ][6] 
[3][4][5] 

After the first tab, the type of script is defined. For our purposes, it'll stay "script" for now, but can also be function, shop, or cashshop, for starters. 
The name of the NPC is next. You can use up to 24 characters, so make it unique! Any duplicates will cause warnings or errors, and the NPC will just be automatically renamed anyway. 
The last number is for the sprite (Ai4rei's sprite list can be found [http://nn.ai4rei.net/dev/npclist/ here]). It's followed by a comma and open curly bracket, marking the beginning of the script contents. Of course, the script must also end in a curly bracket. 

===Function===
A '''Function script''' will look almost identical to:
function <tab> script <tab> Function Name <tab> {

The words "function" and "script" won't change; the name must also be unique. All functions can be called using the "callfunc" command. 

===Shop===
A '''Shop''' starts like a normal script:
prontera,156,145,4 <tab> shop <tab> Fruit Store <tab> 1_M_MERCHANT,512:-1,513:1000

The first section defines the map, coordinates, and direction. The word "shop" replaces "script" (alternately, "cashshop" will use Cashpoints instead of Zeny). The name and sprite ID follow, then a comma. 
Items in the shop are defined in an ID:Price format. A price of -1 uses the default price in item_db.txt. Be sure the price is not too low, or a you will open a Zeny exploit in your server! 

==Fundamentals==

You can always look up commands that you need--even the best scripters don't have everything memorized. There are a few fundamentals that you should know by heart, though, since they are so commonly used.

===Message===

*mes "<string>";
This is the most basic command. Start the line with the word mes, then enter the message in quotes (don't forget the semicolon at the end!). 
To add color, simply add ^ and the hex code anywhere in the message. A list can be found [http://www.immigration-usa.com/html_colors.html here]. 

''As an example:''
mes "[^FF0000Test NPC^000000]";
mes "Hello!";

''Will display:''
[Test NPC]
Hello!

===Labels, Goto, and End===

To create a label, type a label name and a colon at the start of a line. If the label does not end with an "end;" command, everything following the label will be read, so don't forget it between labels! 
To go to a label, use the simple "goto" command:
*goto <label>;

''Note that there are "special" labels that trigger whenever a specific event occurs. The name usually makes it obvious, but you can find explanations in script_commands.txt. Here is a brief sampling:''
OnClock<hour><minute>:
OnInit:
OnAgitStart:
OnAgitEnd:
OnTouch:
OnPCLoginEvent:
OnPCLogoutEvent:
OnPCBaseLvUpEvent:
OnPCJobLvUpEvent:
OnPCDieEvent:
OnPCKillEvent:
OnNPCKillEvent:
OnPCLoadMapEvent:

===Menus, Close, and Next===
{{EntirePage|Menus}}

*menu "<option_text>",<target_label>{,"<option_text>",<target_label>,...};
*close;
*next;
Menus create a set of options, which trigger labels when selected. The text in quotes is what will be displayed, followed by its respective label. Enter as many choices as you want, and end the last one with a semicolon instead of a comma. 
"Close" will close any message window that is open (from "mes" commands). 
"Next" will clear the message window, bringing up a fresh screen. 

''For example:''
mes "[Test NPC]";
mes "How are you doing today?";
menu "I am doing okay!",doingokay,"Not doing too well",bad;

doingokay:
mes "Glad to hear it!";
close;
end;

bad:
mes "Aww, I'm sorry about that.";
close;
end;

===Conditions, Variables, and Set===
{{EntirePage|Variables}}

*if(condition) {<script>;}
*else {<script>;}
Conditional statements "if" and "else" are the same as anywhere else. Multiple conditions can be specified: || means ''or'', while && means ''and''. == is ''equal'', != is ''not equal''. Inequalities can be used as well (<, >, <=, >=). 
The "else" can be omitted, and the brackets aren't necessary unless multiple commands follow a conditional statement. 

The type of variable used is defined in the name. There are permanent and temporary variables, as well as scope (temporary NPC), character, global, and global account. The default type is an integer, and adding $ as a suffix creates a string. 
Here are some example types, taken from script_commands.txt:
name - permanent character integer variable
name$ - permanent character string variable
@name - temporary character integer variable
@name$ - temporary character string variable
$name - permanent global integer variable
$name$ - permanent global string variable
$@name - temporary global integer variable
$@name$ - temporary global string variable
.name - NPC integer variable
.name$ - NPC string variable
.@name - scope integer variable
.@name$ - scope string variable
#name - permanent local account integer variable
#name$ - permanent local account string variable
##name - permanent global account integer variable
##name$ - permanent global account string variable

The "set" command is used to give a value (or string) to a variable:
*set <variable>,<expression>;

''The following script will pick a random number, store it as the temporary scope variable .@random, and display two different messages depending on the result:''
set .@random, rand(1,2);
if (.@random == 1) { mes "I like you! :D"; }
else { mes "I don't like you. Get out of here!"; }
close;

===Duplicating===

It would be a huge waste of time and space to code the same NPC over and over again. By duplication, an NPC can be created in multiple locations. 

Take a look at our old Test NPC:
prontera,156,145,4 <tab> script <tab> Test NPC <tab> 1_M_MERCHANT,{
To be able to duplicate this, we will change the heading to this:
- <tab> script <tab> Test NPC#01::testnpc <tab> 1_M_MERCHANT,{
The location doesn't need to be defined in the NPC, since it will be in the duplicates. 
The displayed name remains "Test NPC". But since NPC names must be unique, adding #01 separates this one from the rest, which will be #02, #03, etc. Lastly, ::testnpc is the reference name used for duplicating NPCs; this part is not displayed on the screen. 

After creating the base NPC, duplicates can be added anywhere to any file, so long as you use the same NPC name:
spl_fild03,150,150,7 <tab> duplicate(testnpc) <tab> Test NPC <tab> 1_M_MERCHANT
niflheim,50,50,2 <tab> duplicate(testnpc) <tab> Test NPC <tab> 1_M_MERCHANT
tha_scene01,140,190,4 <tab> duplicate(testnpc) <tab> Test NPC <tab> 1_M_MERCHANT
The first part is ''map,x,y,direction'', as you're probably used to by now. 
To define a duplicate, the word "duplicate" followed by the NPC, in parentheses, is needed. The last two parameters are the display name and NPC view constant (actual name of the npc sprite, yes, you can change these, too!).

==Finished Product==

Here is an example using the features explained above:

prontera,156,145,4 script Test NPC::test 4_WHIKEBAIN,{
mes "Hello, how are you?";
mes "I am fine, how are you?";
menu "I am doing okay!",-,"Not doing too good",bad;
mes "That's good, I'm glad to hear that";
close;

bad:
mes "Awww, that makes me a bit ^FF0000sad^000000. Sorry to hear that.";
next;
mes "Would you like some zeny to help yourself feel better?";
next;
menu "Sure, give it to me!",L_zeny,"Naw, No zeny for me",-;
close;

L_Zeny:
mes "I can only give you zeny if you have 10,000 or less.";
if (Zeny > 10000) goto toomuch;
mes "You have 10,000 zeny or less, I see.";
set Zeny,Zeny+10000;
next;
mes "Hope you feel better!";
close;

toomuch:
mes "You have over 10,000 zeny, you must feel really good about yourself!";
close;
}

lhz_dun01,157,285,4 duplicate(test) Test NPC 4_F_AGENTKAFRA
hu_fild05,186,210,4 duplicate(test) Test NPC 4_F_AGENTKAFRA
yuno_fild07,221,179,4 duplicate(test) Test NPC 4_F_AGENTKAFRA
tha_scene01,139,194,1 duplicate(test) Test NPC 4_F_AGENTKAFRA

==Adding Scripts==
{{EntirePage|Adding a Script}}
For an NPC to be loaded, it needs to be added to a .conf file. This is typically ''npc/scripts_custom.conf''. 
Add a line, and enter your NPC file in the following format:
npc: npc/path/to/script.txt
That's it! You're finished!

==External Links==
'''Reference Manuals for scriping commands'''
* {{git|/doc/script_commands.txt}} Original documentation

'''Sprite lists'''
* http://nn.ai4rei.net/dev/npclist/

'''Color Charts'''
* http://www.immigration-usa.com/html_colors.html
* http://www.december.com/html/spec/colorcodes.html
* [[wikipedia:Hex_triplet|Hex triplet]]
* http://www.colorschemer.com/online.html

'''Support, Request and Release'''
* [http://herc.ws/board/forum/22-script-support/ Scripting support on Hercules Boards]
* #Hercules on irc.rizon.net : Main Hercules channel.

[[Category:Scripting]]

Custom Items

2016-09-06T04:09:44Z

Wolfeh: /* Files Configured Correctly, sprite does not show up in-game */ Capitalization~

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2 (And so on)
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character. You can look at existing items for an idea of how to format a description.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt
==accname.lub==
accname.lub can be found with the other lua files under RO folder/data/luafiles514/luafiles/datainfo. If you do not have these folders or this file, [http://herc.ws/board/topic/398-client-translation-project/ see this topic] and download the latest translated data folder. It points to the item's sprite file. It is as follows:
[ACCESSORY_IDs.ACCESSORY_ITEM_NAME] = "Item_Name",
==accessoryid.lub==
This is where the view ID for your item can be found. It can be located in the same folder as accname.lub. It is as follows:
ACCESSORY_ITEM_NAME = ViewID#,

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file.

==System/ItemInfo.lub==
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say I want to add a weapon to item id 25000 - a One-handed sword named Devastator with 3 slots and the image/drop sprite files are all named Black_Sword.* . Also I want to display a Sword when not identified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

The unidentifiedResourceName is the Sword item's sprite name, so the client will show it as a sword when not identified. The ClassNum is also 2, for a one-handed sword. If you want to use another sprite for your unidentifiedResourceName, simply search (ctrl+f) for the item's name in iteminfo.lub and copy the identifiedResourceName value for that item and apply it to your custom item's unidentifiedResourceName value.

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, Sprite Still Does Not Show up In-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T04:04:23Z

Wolfeh: /* Defining Items clientside (For New Clients) */ Must. Add. Punctuation. Grammar cleanup. Also added how to find sprite names to use as unidentifiedResourceName's

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2 (And so on)
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character. You can look at existing items for an idea of how to format a description.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt
==accname.lub==
accname.lub can be found with the other lua files under RO folder/data/luafiles514/luafiles/datainfo. If you do not have these folders or this file, [http://herc.ws/board/topic/398-client-translation-project/ see this topic] and download the latest translated data folder. It points to the item's sprite file. It is as follows:
[ACCESSORY_IDs.ACCESSORY_ITEM_NAME] = "Item_Name",
==accessoryid.lub==
This is where the view ID for your item can be found. It can be located in the same folder as accname.lub. It is as follows:
ACCESSORY_ITEM_NAME = ViewID#,

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file.

==System/ItemInfo.lub==
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say I want to add a weapon to item id 25000 - a One-handed sword named Devastator with 3 slots and the image/drop sprite files are all named Black_Sword.* . Also I want to display a Sword when not identified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

The unidentifiedResourceName is the Sword item's sprite name, so the client will show it as a sword when not identified. The ClassNum is also 2, for a one-handed sword. If you want to use another sprite for your unidentifiedResourceName, simply search (ctrl+f) for the item's name in iteminfo.lub and copy the identifiedResourceName value for that item and apply it to your custom item's unidentifiedResourceName value.

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:53:52Z

Wolfeh: /* accessoryid.lub */

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2 (And so on)
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character. You can look at existing items for an idea of how to format a description.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt
==accname.lub==
accname.lub can be found with the other lua files under RO folder/data/luafiles514/luafiles/datainfo. If you do not have these folders or this file, [http://herc.ws/board/topic/398-client-translation-project/ see this topic] and download the latest translated data folder. It points to the item's sprite file. It is as follows:
[ACCESSORY_IDs.ACCESSORY_ITEM_NAME] = "Item_Name",
==accessoryid.lub==
This is where the view ID for your item can be found. It can be located in the same folder as accname.lub. It is as follows:
ACCESSORY_ITEM_NAME = ViewID#,

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:53:32Z

Wolfeh: /* Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) */ Added bit accname and accessoryid.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2 (And so on)
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character. You can look at existing items for an idea of how to format a description.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt
==accname.lub==
accname.lub can be found with the other lua files under RO folder/data/luafiles514/luafiles/datainfo. If you do not have these folders or this file, [http://herc.ws/board/topic/398-client-translation-project/ see this topic] and download the latest translated data folder. It points to the item's sprite file. It is as follows:
[ACCESSORY_IDs.ACCESSORY_ITEM_NAME] = "Item_Name",
==accessoryid.lub==
This is where the viewid for your item can be found. It can be located in the same folder as accname.lub. It is as follows:
ACCESSORY_ITEM_NAME = ViewID#,

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:50:49Z

Wolfeh: Removed xray bit. That project is long dead and we also no longer need to compile and decompile files thanks to newer diffs that load luas.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:13:23Z

Wolfeh: /* Less Than 6 Files */

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a .spr and .act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:12:58Z

Wolfeh: /* Allocating Items on Client Side */

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Custom_Items#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a spr and act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T03:12:28Z

Wolfeh: /* Allocating Items on Client Side */ Removed bit about item having 4 files, there should almost always be 6 files except for garments, accessories, and typically old sprites. Included a section for if there is less than that. Cleaned up extensively.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Most custom items will have 6 files (if yours does not, see [[Allocating_Items_on_Client_Side#Less_Than_6_Files|Less Than 6 Files]]):
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say I downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Sprite Locations==
We place the six files in the following folders

* Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
* Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
* Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
* Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female) '''AND''' ¿©_Helmet.act
* Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male) '''AND''' ³²_Helmet.act

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame and movement animations.

3) Item bmp - 24x24 size 256 bit bmp file. Magenta (FF00FF hexadecimal value) background.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

==How to differentiate between sprite files?==

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

==Less Than 6 Files==
In rare cases or for garment and accessory items, you may have less than 6 files to place. For a garment or accessory, you do not need a spr and act because these items are not visible on a character, therefore they do not require a .spr or .act file. For weapons, headgears, and shields, you should have 6 files. If you do not, you will have to create the missing files yourself. Especially for old sprites, the spriter may have just made the sprites and made no collection image, item image, or drop sprite. See [[Spriting]] on how to create these yourself.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T02:39:22Z

Wolfeh: /* Weapon Sprite Solution (For New Clients) */ Removed underscore. This was an old (and I mean -old-) troubleshooting method that was thought to work. It really doesn't. It's just an extra character for the client to read.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Your custom item will have 4 (6 in case its a headgear or garment) files:
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say i downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Step 1:==
We place the first four files based on what we specified in id2numresnametable.txt (IdentifiedResourceName in Iteminfo.lub).
For our example lets say i used "Helmet" as the resource name :
i) Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
ii) Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
iii) Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
iv) Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
==Step 2 (only for Headgears):==
For displaying headgear on the character there will be two additional files (sprite & act) or 4 if the sprite author intended for a separate set of files for male & female. In my example i have considered the first scenario.

The filename for headgear sprite are now specified in accname.lua file (details of which is available in the [[Custom_Items#View_IDs.2C_Having_A_Custom_Headgear_Without_Xray|View IDs Section]])

lets say i used
[ACCESSORY_IDs.HELMET] = "_Helmet",
then we need to:
i) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female)
ii) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.act
iii) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male)
iv) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.act

Now it is ready to be used provided you have added entries properly to the lua files.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame.

3) Item bmp - 24x24 size 256 bit bmp file.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

How to differentiate between sprite files?

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.

=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T02:37:30Z

Wolfeh: /* Unknown Item */ Fixed it.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Your custom item will have 4 (6 in case its a headgear or garment) files:
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say i downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Step 1:==
We place the first four files based on what we specified in id2numresnametable.txt (IdentifiedResourceName in Iteminfo.lub).
For our example lets say i used "Helmet" as the resource name :
i) Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
ii) Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
iii) Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
iv) Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
==Step 2 (only for Headgears):==
For displaying headgear on the character there will be two additional files (sprite & act) or 4 if the sprite author intended for a separate set of files for male & female. In my example i have considered the first scenario.

The filename for headgear sprite are now specified in accname.lua file (details of which is available in the [[Custom_Items#View_IDs.2C_Having_A_Custom_Headgear_Without_Xray|View IDs Section]])

lets say i used
[ACCESSORY_IDs.HELMET] = "_Helmet",
then we need to:
i) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female)
ii) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.act
iii) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male)
iv) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.act

Now it is ready to be used provided you have added entries properly to the lua files.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame.

3) Item bmp - 24x24 size 256 bit bmp file.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

How to differentiate between sprite files?

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "_Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.
=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Item_clientside_.28Renewal_Clients_.3C.3D_2012-04-10a_.26_Main_Clients_.3C.3D_2012-07-10a.29|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T02:35:30Z

Wolfeh: /* Unknown Item */ Trying to get formatting to work. .-.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Your custom item will have 4 (6 in case its a headgear or garment) files:
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say i downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Step 1:==
We place the first four files based on what we specified in id2numresnametable.txt (IdentifiedResourceName in Iteminfo.lub).
For our example lets say i used "Helmet" as the resource name :
i) Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
ii) Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
iii) Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
iv) Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
==Step 2 (only for Headgears):==
For displaying headgear on the character there will be two additional files (sprite & act) or 4 if the sprite author intended for a separate set of files for male & female. In my example i have considered the first scenario.

The filename for headgear sprite are now specified in accname.lua file (details of which is available in the [[Custom_Items#View_IDs.2C_Having_A_Custom_Headgear_Without_Xray|View IDs Section]])

lets say i used
[ACCESSORY_IDs.HELMET] = "_Helmet",
then we need to:
i) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female)
ii) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.act
iii) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male)
iv) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.act

Now it is ready to be used provided you have added entries properly to the lua files.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame.

3) Item bmp - 24x24 size 256 bit bmp file.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

How to differentiate between sprite files?

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "_Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.
=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[Custom_Items#Defining_Items_Clientside|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T02:35:07Z

Wolfeh: /* Unknown Item */

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Your custom item will have 4 (6 in case its a headgear or garment) files:
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say i downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Step 1:==
We place the first four files based on what we specified in id2numresnametable.txt (IdentifiedResourceName in Iteminfo.lub).
For our example lets say i used "Helmet" as the resource name :
i) Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
ii) Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
iii) Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
iv) Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
==Step 2 (only for Headgears):==
For displaying headgear on the character there will be two additional files (sprite & act) or 4 if the sprite author intended for a separate set of files for male & female. In my example i have considered the first scenario.

The filename for headgear sprite are now specified in accname.lua file (details of which is available in the [[Custom_Items#View_IDs.2C_Having_A_Custom_Headgear_Without_Xray|View IDs Section]])

lets say i used
[ACCESSORY_IDs.HELMET] = "_Helmet",
then we need to:
i) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female)
ii) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.act
iii) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male)
iv) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.act

Now it is ready to be used provided you have added entries properly to the lua files.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame.

3) Item bmp - 24x24 size 256 bit bmp file.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

How to differentiate between sprite files?

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "_Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.
=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[#Defining_Items_Clientside|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.

==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]

Custom Items

2016-09-06T02:33:40Z

Wolfeh: Added a troubleshooting section.

=Structure=
First, let's take a look at the item_db.conf in the db folder, and its structure:
item_db: (
{
// =================== Mandatory fields ===============================
Id: ID (int)
AegisName: "Aegis_Name" (string, optional if Inherit: true)
Name: "Item Name" (string, optional if Inherit: true)
// =================== Optional fields ================================
Type: Item Type (int, defaults to 3 = etc item)
Buy: Buy Price (int, defaults to Sell * 2)
Sell: Sell Price (int, defaults to Buy / 2)
Weight: Item Weight (int, defaults to 0)
Atk: Attack (int, defaults to 0)
Matk: Magical Attack (int, defaults to 0, ignored in pre-re)
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
Archer: true/false (boolean, defaults to false)
Acolyte: true/false (boolean, defaults to false)
Merchant: true/false (boolean, defaults to false)
Thief: true/false (boolean, defaults to false)
Knight: true/false (boolean, defaults to false)
Priest: true/false (boolean, defaults to false)
Wizard: true/false (boolean, defaults to false)
Blacksmith: true/false (boolean, defaults to false)
Hunter: true/false (boolean, defaults to false)
Assassin: true/false (boolean, defaults to false)
Crusader: true/false (boolean, defaults to false)
Monk: true/false (boolean, defaults to false)
Sage: true/false (boolean, defaults to false)
Rogue: true/false (boolean, defaults to false)
Alchemist: true/false (boolean, defaults to false)
Bard: true/false (boolean, defaults to false)
Taekwon: true/false (boolean, defaults to false)
Star_Gladiator: true/false (boolean, defaults to false)
Soul_Linker: true/false (boolean, defaults to false)
Gunslinger: true/false (boolean, defaults to false)
Ninja: true/false (boolean, defaults to false)
Gangsi: true/false (boolean, defaults to false)
Death_Knight: true/false (boolean, defaults to false)
Dark_Collector: true/false (boolean, defaults to false)
Kagerou: true/false (boolean, defaults to false)
Rebellion: true/false (boolean, defaults to false)
}
Job: Job mask (int, defaults to all jobs = 0xFFFFFFFF)
Upper: Upper mask (int, defaults to any = 0x3f)
Gender: Gender (int, defaults to both = 2)
Loc: Equip location (int, required value for equipment)
WeaponLv: Weapon Level (int, defaults to 0)
EquipLv: Equip required level (int, defaults to 0)
EquipLv: [min, max] (alternative syntax with min / max level)
Refine: Refineable (boolean, defaults to true)
View: View ID (int, defaults to 0)
BindOnEquip: true/false (boolean, defaults to false)
ForceSerial: true/false (boolean, defaults to false)
BuyingStore: true/false (boolean, defaults to false)
Delay: Delay to use item (int, defaults to 0)
KeepAfterUse: true/false (boolean, defaults to false)
Trade: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
nodrop: true/false (boolean, defaults to false)
notrade: true/false (boolean, defaults to false)
nostorage: true/false (boolean, defaults to false)
nocart: true/false (boolean, defaults to false)
noselltonpc: true/false (boolean, defaults to false)
nomail: true/false (boolean, defaults to false)
noauction: true/false (boolean, defaults to false)
nogstorage: true/false (boolean, defaults to false)
partneroverride: true/false (boolean, defaults to false)
}
Nouse: { (defaults to no restrictions)
override: GroupID (int, defaults to 100)
sitting: true/false (boolean, defaults to false)
}
Stack: [amount, type] (int, defaults to 0)
Sprite: SpriteID (int, defaults to 0)
Script: <"
Script
(it can be multi-line)
">
OnEquipScript: <" OnEquip Script (can also be multi-line) ">
OnUnequipScript: <" OnUnequip Script (can also be multi-line) ">
// =================== Optional fields (item_db2 only) ================
Inherit: true/false (boolean, if true, inherit the values
that weren't specified, from item_db.conf,
else override it and use default values)
},
)

* '''ID''': ID of the item.
* '''AegisName''': Server name to reference the item in scripts and lookups, should use no spaces.
* '''Name''': Name in English for displaying as output for @ and script commands.
* '''Type''': Purpose of the item.
0 = Usable : healing
2 = Usable : other
3 = Misc
4 = Weapon
5 = Armor
6 = Card
7 = Pet Egg
8 = Pet Equipment
10 = Arrow/Ammunition
11 = Usable : delayed consumption (items with script "pet" or "itemskill")
18 = Another delayed consume that requires user confirmation before using item.
* '''Buy''': Default [[NPC]] buying price in Zeny. When not specified, becomes double the sell price.
* '''Sell''': Default [[NPC]] selling price in Zeny. When not specified, becomes half the buy price.
* '''Weight''': Item's weight. Each 10 is 1 weight. When not specified, becomes 0.
* '''ATK''': Base weapon attack, in case of a weapon. When not specified, becomes 0.
** In '''RE''' enabled servers this field have a optional delimiter ''':''' to define this item's weaponMATK bonus, for example, '''30:50''' would mean the item gives 30 atk and 50 weaponMATK
* '''Matk''': Weapon's magical attack (only used in renewal mode, ignored in pre-renewal). When not specified, becomes 0.
* '''DEF''': Base defense for armor-type items. When not specified, becomes 0.
* '''Range''': Maximum range in map cells a weapon allows to be the player apart from it's target. When not specified, becomes 0.
* '''Slots''': Amount of card slots in weapon/armor-type items. When not specified, becomes 0.
* '''Job''': Which jobs this item is available for. Values below can be combined to achieve availability for multiple job classes, i. e. <code>0x2|0x4 -> 0x6</code> (Swordman+Mage)
(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Mage (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
''Unused'' (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
''Unused'' (2^20): 0x00100000
Taekwon (2^21): 0x00200000
StarGladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000
Rebellion (2^30): 0x40000000
'''Some other commonly used values:'''
All Classes : 0xFFFFFFFF
Every Job Except Novice : 0xFFFFFFFE
* '''Upper''': Specifies whether the item can be used by normal, baby or reborn classes. Values below can be combined, i. e. <code>1|4 -> 5</code> (Normal+Baby Classes)
** Note: Setting <code>2</code> enables the item for Transcendant and 3rd classes. Use <code>8</code> to enable the item for 3rd classes only.
Normal jobs: 0x01 (1)
Upper jobs: 0x02 (2)
Baby jobs: 0x04 (4)
Third jobs: 0x08 (8)
Upper Third jobs: 0x10 (16)
Baby Third jobs: 0x20 (32)

Under pre-re mode third classes are considered upper, making use of
the 8 and above masks is therefore not necessary unless in renewal
mode. When no value is specified, all classes (mask 0x3f) are able to
equip the item.
* '''Gender''': Gender restriction for the item.
0 = Female
1 = Male
2 = No restriction (both)
* '''Loc''': Equipment location of armor and arrow-type items. Values below can be combined, i. e. 136 would indicate both accessory slots (typical value for accessories).
(2^0) 1 = Lower headgear
(2^1) 2 = Right hand
(2^2) 4 = Mantle
(2^3) 8 = Accessory 1
(2^4) 16 = Armor
(2^5) 32 = Left hand
(2^6) 64 = Shoes
(2^7) 128 = Accessory 2
(2^8) 256 = Upper headgear
(2^9) 512 = Middle headgear
(2^10) 1024 = Costume Top Headgear
(2^11) 2048 = Costume Mid Headgear
(2^12) 4096 = Costume Low Headgear
(2^13) 8192 = Costume Garment/Robe
(2^15) 32768 = Arrow (arrow-type items only)
(2^16) 65536 = Shadow Armor
(2^17) 131072 = Shadow Weapon
(2^18) 262144 = Shadow Shield
(2^19) 524288 = Shadow Shoes
(2^20) 1048576 = Shadow Accessory 2
(2^21) 2097152 = Shadow Accessory 1
* '''WeaponLv''': Weapon level of an item (1-4), Becomes 0 when not specified.
* '''EquipLv''': Base level required to be able to equip. It is possible to specify two values, if an item has a maximum level, by using the following syntax:
EquipLv: [minLv, maxLv]

If only one value is specified, maxLv becomes the current server's
MAX_LEVEL. If no values are specified, minLv becomes 0.
* '''Refineable''': Whether the item is available for refining (1) or not (0). If no value is specified, it defaults to true.
* '''View''': For normal items, defines a replacement view-sprite for the item
:(eg: Making apples look like apple juice). The special case are weapons and ammo where this value indicates the weapon-class of the item.
** Weapon-type items:
**# Daggers
**# One-Handed Swords
**# Two-Handed Swords
**# One-Handed Spears
**# Two-Handed Spears
**# One-Handed Axes
**# Two-Handed Axes
**# Maces
**# ''(not used)''
**# Wand/Staff
**# Bows/Crossbows
**# Knuckle Weapons
**# Musical Instruments
**# Whips
**# Books
**# Katars
**# Revolvers
**# Rifles
**# Shotguns
**# Gatling guns
**# Grenade launchers
**# Fuuma shuriken
** Shield-type items:
**# Guard, Novice Guard
**# Buckler
**# Shield, Holy Guard, Evangelist
**# Mirror Shield
** Ammunition-type items:
**# Arrows
**# Throw-able daggers
**# Bullets
**# Shells
**# Grenades
**# Shuriken
**# Kunai
**# Cannonballs
**# Throwable Items (Sling Item)
** Headgear-type items: Please see the View IDs section of this guide.
* '''BindOnEquip''': Whether the item will automatically bind to the character when it is equipped for the first time.
:An item that has this field set, will display a confirmation dialog the first time it is equipped, and, if accepted, the item will become character-bound.
* '''Script''': This is where you put your item bonus. Whether it's an usable item or an equip item, it will take effect according to the item type.
* '''OnEquip_Script''': Script to execute when the item is equipped. Warning, not all item bonuses will work here as expected.
* '''OnUnequip_Script''': Script to execute when the item is unequipped. Warning, not all item bonuses will work here as expected.
* '''Inherit''': This can be used only in item_db2.conf, and if set to true, and the item already exists in item_db.conf,
:all the missing fields will be inherited from there rather than using their default values.
 
In the doc folder look for a text file called "item_bonus", it shows all the scripts items can have and how they work.
 
For more information about this structure read [http://herc.ws/board/topic/2954-item-db-file-structure-overhaul/ Item DB file structure overhaul]

=Defining Item clientside (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a) =
After you make your item, put it in your item_db2.txt, so that you will not run into conflicts when updating your repository later. Then go to your data folder and modify the following files, one after another.

==idnum2itemdisplaynametable.txt==
This file holds the item names, as displayed inside the client. Each item added as:
ItemID#ItemName#
ItemID is the number from your ID column inside the item db. If your item name contains spaces, replace those with _ (underscore).

==idnum2itemdesctable.txt==
This file contains the description of your item, when it is right-clicked. The syntax for an item is:
ItemID#
Item Description Line 1
Item Description Line 2
#
You can use any amount of lines for the description. If your description contains a #, make sure it is followed by a space character.
==idnum2itemresnametable.txt==
This file sets the inventory and drop-sprite for an the item. Item is defined as follows:
ItemID#SpriteName#
The SpriteName is the name of the files in collection and item folders inside texture and the ones inside sprite folder. If you want to use the look of an another item, search for it's id and copy the sprite name from there.
==itemslotcounttable.txt==
In this file you set the amount of visible slots for the item. You do not need to add 0 slot items or items, which do not have slots at all (i. e. usable items). Syntax:
ItemID#NumberOfSlots#
NumberOfSlots should be a number from 1-4, larger values might have undesired effects.
==Files for non-identified items==
The following files specify the name, description and look for items, which have not yet been identified. Their syntax follows the same rules as for the files with ''idnum'' prefix. Normally the same text is entered for non-equipment and generic description (which can be copied from official items) is used for equipment of all sorts (weapons, armor, headgears).
* num2itemdesctable.txt
* num2itemdisplaynametable.txt
* num2itemresnametable.txt

=Defining Items clientside (For New Clients)=
If your client date is newer than specified above then you need to specify all the above item information in 1 file

==System/ItemInfo.lub==
Since ItemInfo.lub is compiled, you need to decompile it to lua , add your customs and recompile back to lub file (Some have said that renaming a decompiled file to lub also works)
Syntax:
[<item id>] = {
unidentifiedDisplayName = <item name to show when not magnified>,
unidentifiedResourceName = <file name prefix used for all the images and drop sprite when not magnified>,
unidentifiedDescriptionName = { <comma separated list of strings>,<to get multiple lines>,<in item description> },
identifiedDisplayName = <item name to show when magnified>,
identifiedResourceName = <file name prefix used for all the images and drop sprite when magnified>,
identifiedDescriptionName = { <same format as unidentifiedDescriptionName but for magnified items> },
slotCount = <number of slots>,
ClassNum = <View ID - yes the same one that was there item_db>
},
For Weapons, ClassNum = View ID specified in Weapon_IDs table (inside weapontable.lub file). Look [[Custom_Items#Weapon_Sprite_Solution_.28For_New_Clients.29|below]] for details.

You can also put the different values in DescriptionName in separate lines.

Example: Lets say i want to add a weapon to item id 25000 - a One handed sword named Devastator with 3 slots & the image files & drop sprite files are all named Black_Sword.* . Also i want to display a Sword when not magnified.

[25000] = {
unidentifiedDisplayName = "Sword",
unidentifiedResourceName = "¼Òµå",
unidentifiedDescriptionName = { "Unidentified item, can be identified with [Magnifier]." },
identifiedDisplayName = "Devastator",
identifiedResourceName = "Black_Sword",
identifiedDescriptionName = {
"An Unholy Sword that was created with the sole purpose of destruction",
"Class :^777777 Sword^000000",
"Attack :^777777 325^000000",
"Weight :^777777 80^000000",
"Weapon Level :^777777 4^000000",
"Required Level :^777777 100^000000",
"Applicable Job :^777777 Novice, Swordsman Class, Merchant Class, Thief Class^000000"
},
slotCount = 3,
ClassNum = 2
},

= Allocating Items on Client Side =
Your custom item will have 4 (6 in case its a headgear or garment) files:
1) Drop sprite -> Helmet_drop.spr
2) Drop act file -> Helmet_drop.act
3) Item Inventory image -> Helmet_item.bmp
4) Item Collection image -> Helmet_collection.bmp (the one you see on its description window)
5) Headgear View sprite -> Helmet.spr
6) Headgear View act file -> Helmet.act

Lets say i downloaded a custom item called Helmet which serves as a headgear and the above six files were in them.

==Step 1:==
We place the first four files based on what we specified in id2numresnametable.txt (IdentifiedResourceName in Iteminfo.lub).
For our example lets say i used "Helmet" as the resource name :
i) Copy Helmet_drop.spr to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.spr
ii) Copy Helmet_drop.act to [RO Folder]\data\sprite\¾ÆÀÌÅÛ\Helmet.act
iii) Copy Helmet_item.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\item\Helmet.bmp
iv) Copy Helmet_collection.bmp to [RO Folder]\data\texture\À¯ÀúÀÎÅÍÆäÀÌ½º\collection\Helmet.bmp
==Step 2 (only for Headgears):==
For displaying headgear on the character there will be two additional files (sprite & act) or 4 if the sprite author intended for a separate set of files for male & female. In my example i have considered the first scenario.

The filename for headgear sprite are now specified in accname.lua file (details of which is available in the [[Custom_Items#View_IDs.2C_Having_A_Custom_Headgear_Without_Xray|View IDs Section]])

lets say i used
[ACCESSORY_IDs.HELMET] = "_Helmet",
then we need to:
i) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.spr (Female)
ii) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\¿©\¿©_Helmet.act
iii) Copy Helmet.spr to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.spr (Male)
iv) Copy Helmet.act to [RO Folder]\data\sprite\¾Ç¼¼»ç¸®\³²\³²_Helmet.act

Now it is ready to be used provided you have added entries properly to the lua files.

==Specifications of the files==
1) Drop sprites - ideally have 1 frame & its act file will be just an empty act (only header will be there inside)

2) Equip sprites - typically have 3+ frames to show images for various orientations & its act file will have the info on where to place each frame.

3) Item bmp - 24x24 size 256 bit bmp file.

4) Collection bmp - 75x100 size bmp file (usually 256 bit but there is no restriction)

How to differentiate between sprite files?

Open both sprite files in [http://ratemyserver.net/download_agent.php?type=1&file_num=10 Spr Conview]. The number of frames in the files can be seen at bottom (Sprite: <currentframe>/<total>). If it says Sprite: 1/1 then its a drop sprite and the other is equip sprite.

Sometimes what sprite authors do is they simply copy the original sprite itself to make a drop sprite. In this case you will see both of them as identical when opened in Spr Conview & we don't need to worry about which one is which (since they are the same).

If the process confused you, [http://www.mediafire.com/?8lzt4cbot100w44 here is an example folder], the sprite is done by drkangel. The folder is virus free.

= View IDs, Having A Custom Headgear Without Xray =
Look in your data folder and make sure there is a folder named "lua files", if there is not make it.[http://svn6.assembla.com/svn/ClientSide/Lua_Project/lubs/ Download the most recent lub package] and extract it to your lua files folder in your data folder. [http://svn6.assembla.com/svn/ClientSide/Lua_Project/lua%20files/datainfo/ Download the most recent accname.lua and accessoryid.lua], put it in your datainfo folder that is inside the lua files folder. Now download [http://svn6.assembla.com/svn/ClientSide/Lua_Project/tool/luac5.0.2.exe this lub compiling tool], and put it in the datainfo folder.
Now, Open accessoryid.lua in the datainfo folder with notepad or a text editor of your choice, go all the way down until the names stop. Add your custom gears before the } symbol. You should use a high number just like with your custom item's database ID, or use unused IDs to be sure you won't have to redo them all in the future, or at least for a while. Example:
ACCESSORY_PINKBUNNY_HAIRBAND = 663,
ACCESSORY_GREENBUNNY_HAIRBAND = 664,
ACCESSORY_OLD_ELFEAR = 665,
ACCESSORY_THA_MAERO_MASK = 666,
ACCESSORY_THANATOS_MAI_MASK = 667,
--668 free
ACCESSORY_FISHPIN = 669,
ACCESSORY_CUSTOM_HAT = 900,
}

''You must compile to lub if you leave space between IDs, if you don't plan on compiling to lub, make sure you do not skip any numbers.''

Now open accname.lua, do basically the same thing but just in a different way, and for the sprite. Add your item to the bottom, have it look like the ones above it, except have your items name and the item's sprite name.
[ACCESSORY_IDs.ACCESSORY_PINKBUNNY_HAIRBAND] = "_ÇÎÅ©Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_GREENBUNNY_HAIRBAND] = "_±×¸°Åä³¢¸Ó¸®¶ì",
[ACCESSORY_IDs.ACCESSORY_OLD_ELFEAR] = "_°í´ë¿äÁ¤ÀÇ±Í",
[ACCESSORY_IDs.ACCESSORY_THA_MAERO_MASK] = "_Å¸³ªÅä½ºÀÇ½½ÇÄ°¡¸é",
[ACCESSORY_IDs.ACCESSORY_THANATOS_MAI_MASK] = "_Å¸³ªÅä½ºÀÇÁõ¿À°¡¸é",
[ACCESSORY_IDs.ACCESSORY_FISHPIN] = "_¹°°í±âÇÉ",
[ACCESSORY_IDs.ACCESSORY_CUSTOM_HAT] = "_Sprite_Name_Here",
}
Delete the accname.lub and accessoryid.lub. Now that you are done, make sure luac.exe is in your datainfo folder, right click the luac.exe, create a shortcut, right click the shortcut, and click properties, in the target area, add right after the quotes, with the quotes:
-o "accessoryid.lub" "accessoryid.lua"
So that it looks something like this:
"C:\Program Files (x86)\Gravity\RO\data\lua files\datainfo\luac5.0.2.exe" -o "accessoryid.lub" "accessoryid.lua"
Do this also to "accname.lub" except instead of accessoryid in the quotes, do accname. If there is any lua file leftover, you may want to move it somewhere else just for future changes, like My Documents. For future reference, this is also how you turn the other lub files to lua files.

=Modifications=
==Sprite Replacement==
To replace a headgear with your customized headgear, just delete one of the items you want, and replace your customised item ID with that id.

Lets say you have something like this:
15000,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}
And there's an item you wont need, such as:
2220,Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
Well, to replace it, just delete everything in the hat line but its ID, and paste there your custom item, all the line but the ID. Should be like this:
'''2220''',Hat,Hat,5,1000,,200,,2,,0,10477567,2,256,,0,1,16,{},{},{}
15000,'''Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
'''2220,Angel_Wing,Angel Wing,4,,10,10,0,,1,0,0,3,0,0,0,0,0,{},{},{}'''
All you need to do now is changing the View ID to the Hat, and change your file names to its name. You can find them on the idnum2resnametable.txt Search for 2220 and the gibberish besides it, w/o the # # is the file name, then rename it to your custom item name.

Remember to add the files to data\sprite\¾ÆÀÌÅÛ (Icon sprite) and both data\sprite\¾Ç¼¼»ç¸®\³² (Male Item Sprite) and data\sprite\¾Ç¼¼»ç¸®\¿© (Female Item Sprite). Remember, these 2 last item names, must have either a ³²_ for male or ¿©_ for female, at the beginning of the name, both .spr and .act. Also, don't forget to change the other files:

idnum2itemdisplaynametable.txt , idnum2itemdesctable.txt , idnum2itemdesctable.txt , num2itemdesctable.txt , num2itemdisplaynametable.txt , num2itemresnametable.txt and itemslotcounttable.txt

Use these files if you want to replace sprites, they will be useful.
* '''actOR:''' with the actor you modify the act file, which is the one who tells the client where does the weapon go and what does it have to do and at a certain moment.
* '''SPR Conview:''' you can use these to view which sprite is which, and also see sequence per sequence.

==Item Restrictions==
Look on your db folder for a file called item_trade.txt and open it

Now, the pattern for a flag is:

Item ID, TradeMask, GM-Level Override

* '''Item ID''': the ID of your item.
* '''TradeMask''': Testrictions the item will have, such as being dropped, stored or traded. These values can be combined to achieve multiple effects.
1:Item can't be dropped
2:Item can't be traded (nor vended)
4:Item can only be traded with wedded partner
8:Item can't be sold to NPCs
16:Item can't be placed in the cart
32:Item can't be placed in the storage
64:Item can't be placed in the guild storage
* '''GM-Level Override''': This is the minimum GM level a player must have to avoid these restrictions.

==Item Script==
{{duplication
|type=section
|what=[[itemskill]], [[sc_start]] and [[skilleffect]]}}
{{disputed
|type=section
|date=September 2010}}
Okay, I'll update this as I go; otherwise, I wont have anything new to show. First with usable items.

Well, there are 3 types of usables:

1.- Healing items, they have in the type field a 0.

2.- Other uses items, such as fly wings and so, which doesn't heal, but does have an instant effect, they have in the type field a 2.

3.- Usable items, which are skills that requires a target selection, therefore they have a delayed use, and in newer versions the item wont be gone until the target is chosen and the cast has finished. Means, you wont lose the item if the skill hasn't been done. They have in the type field an 11.

Now, for an item skill, the pattern for a skill is:
itemskill <skill id>,<skill level>;
Without <> of course.

Now, we go to our db\skill_db.txt and search for the blessing ID, searching for AL_ or blessing, but first, the structure of a skill:
id,range,hit,inf,element,nk,splash,max,list_num,castcancel,cast_defence_rate,inf2,maxcount,skill_type,blow_count,name,description
Now, the AL_BLESSING or Blessing Skill:
34,9,6,16,0,0x1,0,10,1,yes,0,0,0,magic,0, AL_BLESSING,Blessing
We grab the ID and put it on our code:
itemskill 34,<skill lvl>;
Don't mind the actual level of the skill_db.txt for the skill level part. You can actually put the level you want here below 99, so lets pick 4:
itemskill 34,4;
And finally, insert it on the code.
<pre>,{ itemskill 34,4; },{},{}</pre>

There, we have a Lvl 4 Blessing item skill.

Remember, one space before and one after the script, NOT TAB!

And so on with other skills. Just remember these steps and they should be fine. And remember, itemskill is NOT the same as skill. itemskill will make you CAST that skill, while skill will GIVE you the skill. If you give an item, whether delayed use or normal usable two itemskill commands, only the latter will come into effect, as you cannot cast two skills at the same time.

Now, for Potions.

Instead of using itemskill, we will use itemheal:
,{ itemheal 100,0; },{},{}
The green is the HP, the blue is the SP. To add that random heal amount effect, just pick a set amount, let's say 120, then pick 1 or 2 numbers, up to you. Then, add the rand() command, like this:
,{ itemheal rand(120,9,49),0; },{},{}
Explanation: This item will heal about 49~120 hp and 0 SP. To heal SP you change the 0 to a number. Like this:
,{ itemheal rand(120,9,49),50; },{},{}
It will now heal 50 SP.
Now, for skilleffect and sc_start.

Okay, let's see. Here's a example of an item casting a skill and simulating a skill.
,{ itemskill 34,10; skilleffect 29,0; sc_start 12,140000,5; },{},{}
skilleffect will display on your client a skill visual effect. The pattern is:

skilleffect <skill ID>,<number>;

;skill ID
:Self-explanatory.
;number
:Have you seen those skills that shows up numbers upon casting? Such as heal? Well, putting a number there will display it. But only works on skills with numbers floating.

sc_start has the following pattern:

sc_start <status id>,<duration>,<val1>[,<unit id>];

;status id
:Refer to const.txt in your db folder for all effects. Open it with a text editor then search by either clicking edit, then find, or press and hold the ctrl key, and while still holding it press the f key, then release, and search for "SC_ALL -1". Everything below this is an effect. The effects stop at "e_gasp 0" which are emoticons.
;duration
:Is the amount time in milliseconds (1000 msec = 1 sec) that the status will be active.
;val1
:Typically it's the level of the skill, associated with this status.
;unit id
:Allows to start the status on an other unit, than the attached player. For players this is account id. This parameter is optional, and can be omitted.

Now, for the item I said, it will show you the visual effect of Blessing and cast on you a lvl 5 Agi-Up! skill for 140 seconds.

For more item scripts see script_commands.txt in your doc folder, as well as item_bonus.txt in your doc folder.

==Weapon Sprite Solution (Renewal Clients <= 2012-04-10a & Main Clients <= 2012-07-10a)==
For these clients, Weapons are limited to use a range of Item IDs hardcoded in the clientn for each type.
For e.g.

1265,Bloody_Roar,Bloody Roar,4,,10,1000,120,,1,0,4096,7,2,34,4,75,1,16,{ bonus bIgnoreDefRace,RC_DemiHuman; bonus bFlee,-160; bonus bFlee2,-160; bonus bNoRegen,1; bonus bNoRegen,2; },{},{}
1266,Test,Test,4,4000,2000,10,165,,1,0,4096,7,2,34,3,33,1,16,{}

// 1-Handed Axes
1301,Axe,Axe,4,500,,800,38,,1,3,8803555,7,2,2,1,3,1,6,{}

Here the item 1266 is a custom katar and it does show up as a katar (if you have the proper sprite files ofcourse). but if i use some id like say 22000, client wont display it. So what is the range of item ids you can use? Look below:

* One handed Swords = 1100-1149, 13400-13499
* Two handed Swords = 1150-1199, 21000-21999

* Knives, Daggers etc = 1200-1249, 13000-13099
* Katars = 1250-1299 ; Has 35 free IDs

* One handed Axes = 1300-1349; Has 43 free IDs
* Two handed Axes = 1350-1399; Has 32 free IDs

* One handed Spears = 1400-1449; Has 34 free IDs
* Two Handed Spears = 1450-1471, 1474-1499

* Maces = 1500-1549, 16000-16999
* Books = 1550-1599 ; Has only 2 IDs.
* Knuckles = 1800-1899 ; Has 95 free IDs

* One Handed Staves/Rods = 1600-1699; Has 79 free IDs
* Two Handed Staves/Rods = 1472,1473,2000-2099

* Bows = 1700-1749, 18100-18499
* Guitars = 1900-1949 ; Has 32 free IDs
* Whips = 1950-1999 ; Has 130 free IDs

* Handguns = 13100-13149
* Other guns = 13150-13199

* Ninja weapons = 13300-13399

The number of unused Item IDs left known for a range has also been mentioned above. Best practice to follow check in your range in official db before adding custom weapon.

==Weapon Sprite Solution (For New Clients) ==
For new clients the view id system is also applicable to client. To add a custom weapon you need to first edit a file
called weapontable.lub in your data folder
data/luafiles514/lua files/datainfo/weapontable.lub

I will be adding Oriental_Sword which will be a 1-Handed sword. Open weapontable.lub.
First you will see a table called Weapon_IDs. Take note of the first 30 values in this table - these are the only available Weapon types in the client right now.

Anyways go to the last entry which should be for Wizardy Staff = 97. You can use a view id after that like shown below
WEAPONTYPE_Oriental_Sword = 98,

Come down and you see the next table called WeaponNameTable. Here is where you add your sprite name suffix. 
What do i mean by that? Its the last part in your weapon sprite & act file. Before it used to be _<Item ID>.
data/sprite/<job dependent folder>/<job dependent prefix>_<gender><weapon suffix>.spr

OK Back to topic. so I add my entry like shown below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = "_Oriental"

Lastly come down further in weapontable.lub and you see the last table called Expansion_Weapon_IDs. 
Remember the 30 types i told you to take note of ? here we assign one of those to our custom (like a mapping or connection). 
Since mine is a 1-Handed Sword I specify it like below.
[Weapon_IDs.WEAPONTYPE_Oriental_Sword] = Weapon_IDs.WPCLASS_WEAPONTYPE_SWORD

Now for the most important part. For our client to actually pick up all these details we need to provide the view id which we used in Weapon_IDs table as the ClassNum value in ItemInfo.lua. Check the [[Custom_Items#System.2FItemInfo.lub|ItemInfo.lub format]] shown above for details.

With this your weapon sprite will become visible while attacking.
=Troubleshooting=
==File Not Found "Cannot find File : path\to\file\filename.extension"==
As the error states, the client cannot find the file required to display the sprite, act, collection, or item image for the item. Make sure you put your file in the right place and that it is named correctly.
==Unknown Item==
If your item's name is unknown item and it has an apple icon, refer to [[#Defining Items Clientside|Defining Items Clientside]] and make sure you added the item to each and every file, or just iteminfo.lua for a newer client.
==Files Configured Correctly, sprite does not show up in-game==
If you do not have your sprites and files compressed into a GRF, you will need to make sure your client is diffed to read your data folder first.
[[Category:Database]]
[[Category:Data]]
[[Category:Customization]]