The optional slot parameter is not working as intend anymore since the application of the 10.2.6 patch.
Previous and intended behaviour (pre-10.2.6)
Specifying a slot by its InvSlotId in EquipItemByName() would equip the item in the specified slot if appropriate, or return a "That item does not go in that slot" error.
Current behaviour (10.2.6)
Specifying a slot by its InvSlotId in C_Item.EquipItemByName() returns a "That item does not go in that slot" error, even when the proper slot number is specified. Specifying one number lower however, does equip the item.
Example testingGetInventorySlotInfo("FEETSLOT") returns an InvSlotId of 8/run C_Item.EquipItemByName("Nimblefinger Boots", 8) returns the "That item does not go in that slot" error.
/run C_Item.EquipItemByName("Nimblefinger Boots") equips the item as expected.
/run C_Item.EquipItemByName("Nimblefinger Boots", 7) equips the item, despite the wrong slot number being specified.
zeptognome
commented
2 months ago
The optional
slotparameter is not working as intend anymore since the application of the 10.2.6 patch.Previous and intended behaviour (pre-10.2.6) Specifying a slot by its
InvSlotIdinEquipItemByName()would equip the item in the specified slot if appropriate, or return a "That item does not go in that slot" error.Current behaviour (10.2.6) Specifying a slot by its
InvSlotIdinC_Item.EquipItemByName()returns a "That item does not go in that slot" error, even when the proper slot number is specified. Specifying one number lower however, does equip the item.Example testing
GetInventorySlotInfo("FEETSLOT")returns anInvSlotIdof8/run C_Item.EquipItemByName("Nimblefinger Boots", 8)returns the "That item does not go in that slot" error./run C_Item.EquipItemByName("Nimblefinger Boots")equips the item as expected./run C_Item.EquipItemByName("Nimblefinger Boots", 7)equips the item, despite the wrong slot number being specified.