Damn! This one is nasty. I've been playing with item transformations for a while but I haven't noticed this one before. Basically it's about temperature not being recreated when attachments get recreated during the item transformation (their status i.e. does get checked and is properly recreated). To give an example: I have a weapon with 2 attachments: a grenade launcher and a retractable stock with transformation option to extend/retract it. I fire a few shots from the underbarrel grenade launcher and it gets its temperature high. Then I use transformation option to extend the stock (retracted retractable stock transforms into extended retractable stock). After this the temperature on the grenade launcher drops to 0. The same of course happens to attachments temperature if I would use transformation directly on the gun itself. I hope I've managed to explain this problem clearly.

OBJECTTYPE tempAttachment;
CreateItem(iter->usItem, (*iter)[0]->data.objectStatus, &tempAttachment);

FLOAT barreltemperature = (*iter)[0]->data.bTemperature;
OBJECTTYPE tempAttachment;
CreateItem(iter->usItem, (*iter)[0]->data.objectStatus, &tempAttachment);
(tempAttachment)[0]->data.bTemperature = barreltemperature;

if(Item[Item[pObj->usItem].defaultattachments[cnt]].inseparable == 1){
	FLOAT barreltemperature = (*pObj)[ubStatusIndex]->data.bTemperature;
	OBJECTTYPE defaultAttachment;
	CreateItem(Item [ pObj->usItem ].defaultattachments[cnt],(*pObj)[ubStatusIndex]->data.objectStatus,&defaultAttachment);
	(defaultAttachment)[0]->data.bTemperature = barreltemperature;
	AssertMsg(pObj->AttachObject(NULL,&defaultAttachment, FALSE, ubStatusIndex, -1, FALSE), "A default attachment could not be attached after merging, this should not be possible.");
}