How to Fix

07/23/2020 03:02 Bron*#1





07/23/2020 11:26 xTwiLightx#2
Errors 1 and 2 occur when a player tries to trade two stacks of the same item (same unique-id) in one trade.

Fix: Make the PK_tblTradeItemLog non-unique
- That is not possible by definition, because Primary Keys are explicitly unique. Create a non-unique clustered index as a replacement instead.

Errors 3 and 4 are follow-up errors because of the first/second one happened.

Errors 5 and 6 are happening when a socket receives messages with no/invalid content - most likely empty messages. There is no real fix yet besides removing the call which prints out the message.