VladimirMangos

I just check and see that client self output error at account with @ use without any data send to server.

BN authorization mode totally different from GRUNT authorization mode.

In mangos we have special case also when typeid data required by client so we already have in any case typeid for object ready for checks

In [s0073]. Thank you

s0041_10254_01_characters_auctionhouse.sql already have and it added to mangos-0.12 sql updates So i not understand about what you talk also... [added] Oh, I see now.... sometime my brain stuck

Possible some corrupted data in player DB data. Ofc, in good case it must be detected by code at load, but possible some checks missing. If you catch related character, please make pdump (.pdump command in console) and send created file to me by PM.

Client not allow @ in account names

Look in s0041_10254_01_characters_auctionhouse.sql tail.

Exactly. Posible you look in some spell effect code that can be casted only by player caster

Test with [10288] or later

Exist common threads for crash posts. Bug report must be about specific problem, in different collection random unrelated crashes. Just crash isn't specific problem. Closed without view.

Crash described by LordJZ (and possible source many other crashes after aura holder code adding) must be fixed in [10287-10288] Before last your post i not read any _normal_ description for repeating problem. Just note "Crash with spell" isn't normal description.

Crash confirmed. Not related in fact to auras change... [added]Ok, infact this si 2 not directly connected porblems. 1) with pet out of range lost direct control -> it must dismissed in like case 2) problem with auras remove after aura holder code adding, so crash related to aura holders. If crash related to (1) fixed then we get crash (2) as bonus (it just not get chance triggering in result (1)). Crash (2) happens in result double delete aura in some cases.

In fact same error i see at local computer with client and server often But i agree another source fake packets.

Fix for `creature_addon` added in [10286].

This is usless have any IP address in this case. Error related to client reaction at long disconnected state and later attempt connect to server. Not mangos problem. Just client wrong data send in described case. Just need close client and start new copy. Ofc, possible another cases of error but this 99% cases of it. This is not first time answered.

In [10284]. Thank you

And you forgot add "with custom patches"...

Crash logs often not help, just because not have any useful info for catch bug... Only really 100% help way: provided steps for repeat bug with some good chance...

This is week as fixed in mangos.

Thank you for finding this probems with items. But same porblem exist also at guild unload at server shutdown. Ofc, memory free in any cases at shutdown, but different memory leak detectors will triggering at this memory as lost. So i plan rewrite your patch for use same code (without DB deleting) for ~Guid and possible remove m_PurchasedTabs... About used code itself: items in guild bank considered as in world, so before deletion its must be moved from world pItem->RemoveFromWorld(); Or you can have problems with not finished update packets for clients /etc

Great catch! In [10283] Thank you I check and i think it writes correctly...

In [10282]. Thank you

In [10281] with described changes. Thank you /guildinfo can be used for check work. [added]Hmm, i use forum nick as author name

GetPlayerAccountIdByGUID do always DB query for offline player. So N quearies at each member add/remove. Very bad way update. [added]I test patch with modification that let avoid this query. If all ok i will commit soon.