Incorrect values in-game

06/04/2016 02:13 NagySandor96#1
Hey Guys !

I have decided to create a new weapon. Its basis is a D11 EVENT (non-tradeable) weapon [ITEM_EVENT_CH_BOW_11_A_RARE]. Both _RefObjCommon and _RebObjItem editings have done, and also the pk2 edits, but I wonder I've made a mistake, however I haven't been able to find for hours.
If any of you could help me, I'd thank it.

Sincerely,
NS
06/04/2016 02:42 ​Exo#2
itemdata is corrupt
06/04/2016 11:16 blapanda#3
Your itemdata string is mixed up with additional and unnecessary information. E.g. whenever you create a monster/npc, you won't copy all _RefObjChar columns with it, because most of them has no meaning to them specifically. The client whatsoever won't skip those information and will instead fetch them visually for the player.

If you are using the "_GetMediaLines" procedure (somewhere around this and rz forums, just add it to your collection, if you haven't already, pretty useful), also watch always for the comma (,) and dot (.) format. Due to my OS, which uses comma as a separation, my SQL Server was doing the same, though the client needs the dot as a decimal separator. So pay attention to that one as well!
06/04/2016 12:04 NagySandor96#4
I see, thank you both. By the way, would you mind if I ask you which parameters don't have to be marked in itemdata ? Lookin forward to yours answer! :)
NS
06/04/2016 12:25 AceSpace#5
I didn't get your last question well but if you meant getting the correct data from database to itemdata, blapanda above suggested using _GetMediaLines which selects the right columns.

Anyway here: [Only registered and activated users can see links. Click Here To Register...] // the bloody mention cannot be used well in codes aka @

Use:

Code:
/*EXEC SRO_VT_SHARD.._GetMediaLines NULL -- if you want to select all the lines*/

EXEC SRO_VT_SHARD.._GetMediaLines 'CODENAME' -- if you want to select for 1 item, though this uses LIKE.
06/04/2016 18:22 NagySandor96#6
I found the "_GetMediaLines" procedure and used as well,but nothing changed, the incorrect values still exist :/

Ahh, guys! It's finally solved. The prob was the missing DOTs in itemdata :)