zergtmn

I've never seen related bugs because I try to avoid dangerous code. When I need to initialize one field with another I just write it in constructor body. In this case order of initialization cannot be altered by accidental field rearrangement (that happens sometimes). Btw, VC++ doesn't have such warning at all. In reality even standard libraries cannot be compiled without warnings under /Wall.

I don't see point in bothering about this type of warning ('a' will be initialized after 'b'). This one I'd always leave disabled.

That is totally unreadable.

UNIT_FIELD_BASEATTACKTIME is just array of two int. SetUInt32Value(UNIT_FIELD_BASEATTACKTIME, main hand attack time); SetUInt32Value(UNIT_FIELD_BASEATTACKTIME+1, offhand attack time);

MaNGOS doesn't have SpellFamilyFlags.test<> stuff. And the way chosen is wrong.

CMake support on Windows is not finished afaik. Use project files from \\win subfolder.

That's just small speedup and reduction in number of memory allocations. From Schmoo's crash dump I can see that AuctionSorter predicate is not strict weak ordering. That's the problem.

Probably item was cached by client already so you need to reset cache from client side (by deleting Cache folder) or from server side (changing ClientCacheVersion in mangosd.conf).

Problem already fixed in 11621, you should upgrade asap. Unfortunately it is impossible to restore items that were sent by mail during bug presence

Well, it is another mount.

Ground mode was added in 4.0.1.

Patch is partially incorrect, rage is set to zero after preparation phase ends.

Check latest revision.

Fixed in 11589.

To deal with ASLR something like http://paste2.org/p/1441229 can be used.