Repaired items loose group

Repaired some armor today and tried to F12 to switch between the groups but the armor no longer had a group associated with it. Can it be made to keep the group association after a repair?

It is an interesting problem.

When you repair something it deletes the item and recreates it again from the original template. Hence it is not just the grouping that it loses but any other added attributes. This includes but not limited to the owner of an item e.g. soulbound items lose their binding if u are able to repair them.

I would need to look at the code in more detail before being able to commit to fixing this.

Problem fixed.

Next time I restart the server these will be active (too many online at the moment).

Switch group retained when item is repaired.
Owner is retained for soulbound items repaired.

I tried to repair a gold th axe on my alt but failed and it was instantly destroyed (was only slightly damaged b4 trying to repair)

Any item that is repairable can also get damaged while you try to repair it.

Generally if you damage it then it goes to the next damage state (0-5) assuming it has damage states. Think 5 = destroyed.

If you damage an item there is a chance that you will also double damage it, change 2 states.

So an item that is in the worst damage state will get destroyed if you repair it and it fails.
In theory an item in the 2nd last state can also get destroyed if it double fails.

Only problem is my axe was 1/5 not 3or4/5, assumin 5 is destroyed... might have been a quad damage as my repair is that low

I am completely and totally confused by all of this, someone explain to the old geezer what is going on here? o.0

Two totally seperate and independent issues covered in this topic, one of which was solved.

When you repair an item, it resets its stats and all its characteristics back to the default template stats. This includes the "Switch group" and the owner if it is soulbound.

The fix was to stop the loss of thos attributes.


The second issue was as to why the items was destroyed while being repaired. Without being able to observe or repeat the activity I am not able to say whether it is an operator or system problem. Hence I ignored it and hoped it went away. This worked - until now