Something strange

[Damnit]

I have a strange error.. When I try to socket using ( these two items are also displayed wrong in-game ), and perhaps other jewels that I haven't tested and are crafted using this item and after I equip the items Wow.exe encounters an error.. and it crashes.

I get this error message

This application has encountered a critical error:

ERROR #134 (0x85100086) Fatal Condition

---------------

I use mangos rev 10721

UDB 0.12.1 (394) for MaNGOS 10720 with SD2 SQL for rev. 1863

ScriptDev2 (for MaNGOS 10610+)

ACID 3.0.7

and Ahbot

[Marik]

I remember we had (or still have) a similar bug on our server.

The user told me, that if someone equipp more than 3 of these special gems, their wow crashes.

How many gems did you equip?

Marik

[Damnit]

I remember we had (or still have) a similar bug on our server.

The user told me, that if someone equipp more than 3 of these special gems, their wow crashes.

How many gems did you equip?

Marik

Only one.. But I also noticed.. that some work on different items.. but only a few

[EARTHWALKER]

I've had that on various servers for months now. I have a plan though. Don't equip special gems

Not ideal I know, but it's the only solution I've been able to come up with.

[darkstalker]

its a client crash caused when you get an equip error from an item with limited category count. The error itself causes the crash (bad packet structure?), disabling it prevent the error

[Damnit]

Glad it's not only me .. Well then.. not using them seems the best solution

[Warlord123]

Hack fix in topic http://ru-mangos.ru/showthread.php?p=15645#post15645

[EARTHWALKER]

Hack fix in topic http://ru-mangos.ru/showthread.php?p=15645#post15645

Link just comes up with a blank page dude. Please look into it.

[Warlord123]

Link is normal.

Patch from link.

index 149aaa0..7b17437 100644
--- a/src/game/Player.cpp
+++ b/src/game/Player.cpp
@@ -12295,7 +12295,35 @@ void Player::SendEquipError( uint8 msg, Item* pItem, Item *pItem2, uint32 itemid
            case EQUIP_ERR_ITEM_MAX_LIMIT_CATEGORY_EQUIPPED_EXCEEDED_IS:
            {
                ItemPrototype const* proto = pItem ? pItem->GetProto() : sObjectMgr.GetItemPrototype(itemid);
-                data << uint32(proto ? proto->ItemLimitCategory : 0);
+                uint32 LimitCategory=proto ? proto->ItemLimitCategory : 0;
+                if (pItem)
+                    // check unique-equipped on gems
+                    for(uint32 enchant_slot = SOCK_ENCHANTMENT_SLOT; enchant_slot < SOCK_ENCHANTMENT_SLOT+3; ++enchant_slot)
+                    {
+                        uint32 enchant_id = pItem->GetEnchantmentId(EnchantmentSlot(enchant_slot));
+                        if(!enchant_id)
+                            continue;
+                        SpellItemEnchantmentEntry const* enchantEntry = sSpellItemEnchantmentStore.LookupEntry(enchant_id);
+                        if(!enchantEntry)
+                            continue;
+
+                        ItemPrototype const* pGem = ObjectMgr::GetItemPrototype(enchantEntry->GemID);
+                        if(!pGem)
+                            continue;
+
+                        // include for check equip another gems with same limit category for not equipped item (and then not counted)
+                        uint32 gem_limit_count = !pItem->IsEquipped() && pGem->ItemLimitCategory
+                            ? pItem->GetGemCountWithLimitCategory(pGem->ItemLimitCategory) : 1;
+
+                        if( msg == CanEquipUniqueItem(pGem, pItem->GetSlot(),gem_limit_count))
+                        {
+                            LimitCategory=pGem->ItemLimitCategory;
+                            break;
+                         
+                        }
+                    }
+
+                data << uint32(LimitCategory);
                break;
            }
            default: 

[goodbadguy]

I have this code applied in my build yet client STILL crashes when attempting to socket a 4th Jeweler's Gem.