Custom Lower Costume Headgear Always Throws an Error

[msecastro]

Hello and good day, rAthena community!

 

I have a question regarding custom items that will be used as costumes. I managed to get most of my custom upper headgear costumes to work but I cannot make the lower ones work (4096).

 

I currently have this on my item_db.txt:

50000,Shaman_Wings,Shaman Wings,4,0,,0,,0,,0,0xFFFFFFFF,63,2,4096,,1,0,1000,{},{},{}

This on on my accessoryid.lub:

ACCESSORY_Shaman_Wings = 1000

..and this on my accname.lub:

[ACCESSORY_IDs.ACCESSORY_Shaman_Wings] = "_shaman_wings"

Upper costume headgears work, just the lower part, it keeps closing the client immediately on equip but I can view it, drop it, and acquire it in game - I just can't wear it. What might be causing this issue?

 

Some additional information:

• I am using the bypass client 2012-04-10a.
• I am using the latest 2012-04-10 lub/lua files which I downloaded in the SVN.
• GRF data is read.

[msecastro]

I think it's because your item ID is 50000 while max you can use is 1 - 32867 according to this topic: https://rathena.org/board/topic/76587-max-item-limit/(But you can increase it as well)

 

Try making the item ID to 25000

 

Thank you for replying, I fixed the problem by using a newer client.

 

..but also considering going back to 2012-04-10 once I get to know what's wrong.

 

Additional information on the 2014-04-10 client::

• I've tried with ID 25000 - 30000 but still no luck, wearing the costume still kicks me out.
• Putting the data on db\import-tmpl\item_db.txt just gave me more unknown sprite errors and kicks me out

[Scylla]

I think it's because your item ID is 50000 while max you can use is 1 - 32867 according to this topic: https://rathena.org/board/topic/76587-max-item-limit/(But you can increase it as well)

 

Try making the item ID to 25000

[Scylla]

Ah i see, maybe there's something buggy on the 2014 client you were using.

 

Well happy to see it's solved

[msecastro]

Ah i see, maybe there's something buggy on the 2014 client you were using.

 

Well happy to see it's solved

 

Thank you and sorry what I meant was the 2012-04-10 client. I currently switched to the  2013-08-07a client and the problem disappeared.