Nduli

Bro if the item in the inventory exists, if the slot exists ,if in sql the item is present in the belt slot it is 100% sure that it is a binary/client side index error. check better.. also because I too often found myself in these problems because between modifications and additions the sources on that side are always very dirty ( I now no have these problems because i redid them from 0 on my source) Try this.. wear item, check in sql what s his index number of equip.. example: is number 123.. open inventorywindow and set row of belt like : {"index": 123 , "x":39, "y":106, "width":32, "height":32} pack file and check if you can see belt in equipment slot

100% sure the index of the slot is wrong, check it

"can't use" is too generic in this world, can you be more specific? are there any client side errors (sysser)? the button does not change the page? the button works but it doesn't let you put the items inside it?

TraceError makes you output a message on the sysser that you put inside like .......... }; BOOL CItemManager::SelectItemData(DWORD dwIndex) { TraceError(" I'm here! in the SelectItemData" ) TItemMap::iterator f = m_ItemMap.find(dwIndex); ... ... ... so you will find in the sysser client " I'm here! in the SelectItemData" and in this way whether or not the trace will come out you will know where the code stops or how far it goes

no sysser?

try to insert traces (TraceError) in the functions, for example at the beginning and at the end of the function to understand where it stops so as to understand where the error could be