I don't know if ScaleItem() if fully implemented yet..could very well be...
https://github.com/EQEmu/Server/blob.../Item.cpp#L710
The last assignment of that function sets the m_scaledItem->CharmFileID = 0 to keep the client from scaling it.
If the item is being sent with the original m_item data and not overriding the m_item->CharmFileID..and the client does its own
scaling modifications..you might see a double scaling going on...
I dunno..I haven't gotten that far in the code yet
If this is the case, I'll fix it in my rework..I've already got ornamentations planned. If it's not, I'll let someone else touch it because
I don't want to stop my rework
Threaded Mode
