Newbie Spellweaver
- Joined
- Jan 4, 2006
- Messages
- 46
- Reaction score
- 8
Welcome to my next guide :> This time we'll look into making custom items. We should start with something simple and nice, so how about we make a talisman 
And not just some ordinary one, but Queen Puppinka's Talisman of Intensification ^^
You need all the basic stuff you need every time so we'll skip that part.
Step 1 : Serverside setup
Items on the server are stored (surprisingly) in MainSvr/Config/InitItem.txt. The syntax is a little more complex, while there is a variety of items and not all parameters can be used by all items. It's not a problem to check the .txt to see how different item classes are defined, so we'll just go on with the making of our talisman:
(item (name N) (Index I) (Image "item017") (class general charm) (code 3 5 12 0) (country 252) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon %1 P1 %2 P2)))
Such a long line and this is just a simple talisman ;]
N = number of the name that is stored in the client (message-e.dat). For a talisman of intensification this will be 531 or 723 (dunno why they have it twice there)
I = unique index for the item. Make it far away from other items, you never know when you may get an updated InitItem and there may be conflicts :>
"item017" is the name of the .bmp file that is shown for the item. They are stored in HyperText folder of the client. For a talisman we have this image ofc :>
class = well for a tali we have "general charm". For a sword it would be "weapon sword" etc :>
code is something that defines the item type, just check every item and you'll see the differences between classes.
country = 252 as always for international version
use = if the item is useable
plural = if the items stack on each other, or if they're one each slot in inventory
buy = buying price @ shop
sell = selling price @ shop
specialty = defines exactly what parameters the item has. A weapon will have it's attack, otp, endurance, stats etc. specified. A talisman has percentages and prefixes :]
%1, P1 = the percentage and prefix number of the first type that can be made from the talis. Let's say fo our tali we will try to make a new prefix with a very low percentage. So we'll write 5 100
%2, P2 = the percentage and prefix number of the second type that can be made from the talis. Well let's make it classic, rash ^^ 50 91
(desc DN) = this is not included by TOIs, but if you look at other items, they have this parameter. It's the index of a description that is written in message-e.dat too.
So our talisman will look something like this:
(item (name 531) (Index 1200) (Image "item017") (class general charm) (code 3 5 12 0) (country 252) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon 5 100 50 91)))
Next step will be defining our nr. 100 prefix, because we want to make a new talisman right? So let's open Prefix.txt. There we add something like this:
(prefix (index 100) (level 3) (sell 350) (str 7) (Hth 7) (Int 7) (Wis 7) (Dex 7) (hp 200) (mp 200) (defense 8))
index = unique index of course
level = you know that +1 +2 +3 that's added to your g50 after enchanting
sell = this is either added to the price of the weapon, or multiplied or something like that :]
stats... well you can set a lot of stats to be added, just check other prefixes too
now save it and we're done serverside :]
Step 2 : Clientside setup
We inserted a custom item in the InitItem.txt. But don't forget there is a InitItem.dat in our config! So we need to add it here too. Extract config.pk, decrypt InitItem.dat and add the correct line:
(item (name 531) (Index 1200) (Image "item017") (class general charm) (code 3 5 12 0) (country 0) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon 5 100 50 91)))
Watch out for the country parameter that is different (although imho it can stay 252). Save, encrypt and add back to config.pk.
Next, we also need to add the new prefix to the client :> So we decrypt prefix.dat and add the correct line (the same as on the server). Save, encrypt, add.
Now we know numbers and stats and stuff like that, but we don't know names ;] So let's decrypt message-e.dat. Here we will find the part that has prefixnames. And we add our name:
( prefixname 100 "The Queen, Puppinka's")
Save, encrypt and put into the config.pk again :>
Now just run your server and client and /get 1200 hehe ^^ btw I tried 30 of these 5% talis and all failed lol...
And not just some ordinary one, but Queen Puppinka's Talisman of Intensification ^^You need all the basic stuff you need every time so we'll skip that part.
Step 1 : Serverside setup
Items on the server are stored (surprisingly) in MainSvr/Config/InitItem.txt. The syntax is a little more complex, while there is a variety of items and not all parameters can be used by all items. It's not a problem to check the .txt to see how different item classes are defined, so we'll just go on with the making of our talisman:
(item (name N) (Index I) (Image "item017") (class general charm) (code 3 5 12 0) (country 252) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon %1 P1 %2 P2)))
Such a long line and this is just a simple talisman ;]
N = number of the name that is stored in the client (message-e.dat). For a talisman of intensification this will be 531 or 723 (dunno why they have it twice there)
I = unique index for the item. Make it far away from other items, you never know when you may get an updated InitItem and there may be conflicts :>
"item017" is the name of the .bmp file that is shown for the item. They are stored in HyperText folder of the client. For a talisman we have this image ofc :>
class = well for a tali we have "general charm". For a sword it would be "weapon sword" etc :>
code is something that defines the item type, just check every item and you'll see the differences between classes.
country = 252 as always for international version
use = if the item is useable
plural = if the items stack on each other, or if they're one each slot in inventory
buy = buying price @ shop
sell = selling price @ shop
specialty = defines exactly what parameters the item has. A weapon will have it's attack, otp, endurance, stats etc. specified. A talisman has percentages and prefixes :]
%1, P1 = the percentage and prefix number of the first type that can be made from the talis. Let's say fo our tali we will try to make a new prefix with a very low percentage. So we'll write 5 100
%2, P2 = the percentage and prefix number of the second type that can be made from the talis. Well let's make it classic, rash ^^ 50 91
(desc DN) = this is not included by TOIs, but if you look at other items, they have this parameter. It's the index of a description that is written in message-e.dat too.
So our talisman will look something like this:
(item (name 531) (Index 1200) (Image "item017") (class general charm) (code 3 5 12 0) (country 252) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon 5 100 50 91)))
Next step will be defining our nr. 100 prefix, because we want to make a new talisman right? So let's open Prefix.txt. There we add something like this:
(prefix (index 100) (level 3) (sell 350) (str 7) (Hth 7) (Int 7) (Wis 7) (Dex 7) (hp 200) (mp 200) (defense 8))
index = unique index of course
level = you know that +1 +2 +3 that's added to your g50 after enchanting
sell = this is either added to the price of the weapon, or multiplied or something like that :]
stats... well you can set a lot of stats to be added, just check other prefixes too
now save it and we're done serverside :]
Step 2 : Clientside setup
We inserted a custom item in the InitItem.txt. But don't forget there is a InitItem.dat in our config! So we need to add it here too. Extract config.pk, decrypt InitItem.dat and add the correct line:
(item (name 531) (Index 1200) (Image "item017") (class general charm) (code 3 5 12 0) (country 0) (use 1) (plural 1) (buy 0) (sell 1500) (specialty (Changeprefix weapon 5 100 50 91)))
Watch out for the country parameter that is different (although imho it can stay 252). Save, encrypt and add back to config.pk.
Next, we also need to add the new prefix to the client :> So we decrypt prefix.dat and add the correct line (the same as on the server). Save, encrypt, add.
Now we know numbers and stats and stuff like that, but we don't know names ;] So let's decrypt message-e.dat. Here we will find the part that has prefixnames. And we add our name:
( prefixname 100 "The Queen, Puppinka's")
Save, encrypt and put into the config.pk again :>
Now just run your server and client and /get 1200 hehe ^^ btw I tried 30 of these 5% talis and all failed lol...
