What it does:
Returns columns in the correct order for use in creating the item.sdata file via python scripts WITH calculations* from the DB to the client.
Prerequisites:
You must add the ItemDesc,Type2,and Type3 columns to your items table
and import the values from your client at least one time to have a complete compiled list of items.
Why would you do this or need this?
What you will have at the end of that is all of the columns that the DB needs and all of the columns that the client needs in one place and it makes porting changes easier back and forth, at least it does for me, and your DB and client will match. It also allows you to make changes to the Item descriptions very easy in SQL, for example:
Code:
update items set ItemDesc='this item is new and made for blah blah blah' where itemid=1243456
Code:
update items set buy=buy-1000
One of the main reasons for doing this for me was to be able to merge EP6 items with items that already exist, this was a little tricky as the client doesn't use ItemID and I didn't want to overwrite what I already have.
Now for those of you that don't want to add the columns to your items table, the below script will work with your current items table ( albeit with place holders for the missing columns ) BUT you will have to copy the columns out individually to paste into your item.complete.csv , just make sure the number of rows is correct, or your sdata is hosed,
* calculations are needed for Reqluc ( enchants ) as the DB has negative values for enchant items and client needs positive values. They are also needed for [Range] as this column for some items relates to a skill ID but the client cannot have a value greater than 255.
Anyway, Happy Shaiya-ing







