VladimirMangos
Members-
Posts
2813 -
Joined
-
Last visited
Never -
Donations
0.00 GBP
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
VladimirMangos's Achievements
Advanced Member (3/3)
0
Reputation
-
Lol, next will be 8...
-
maybe, but those accounts can be logged perfectly by game... Client apply upper case to login/password before send. Mangos apply upper case at accound creating by internal command and expect that in DB you store hascode created from _upper_ version login/password if it calculated by external tools
-
possible missing some code in backports. As i remember this fixed in past in mangos master version.
-
Just check its by self. In past like topics start flame war only. So closed.
-
If mutex need only for original LootItem structure then you can overwrite operator= or LootItem(LootItem const&) to proper way avoid copy mutet (create new in new struct copy. Also i not look but possible LootItems stored as value in storage container and then copy constructor can called when container grow/etc. But posible most correct answer: you add mutex to wrong type when it not expected and wrong placed for any uses.
-
You add mutex field to copyable object. In other cases related objects not copy. In result compiler attempt find operator= or ACE_RW_Mutex(ACE_RW_Mutex const&) but both private because mutex copy is strange idea
-
If commiter set author for commit then he meaning that author write/prepare all/most added in commit code. Sometime in result applied by commiet cleanup/improve codesyle or another reasons commit code can be different from original patch ofc. In case backporting to another mangos repos commit cherry-picked from main mangos repo direcly by use cherry-pick command or by using special script created in past for simplify like backports. Ofc, commiter often do some locla chnages after cherrypick for make backported commit compatible with related clietn version
-
Compress condition table by remove duplicates can be contra-productive infact. This make very hard fix condition because will be unclear is it shared or not with other condition as part its. At condition loading it registered and lookup by condition data so it auto merge with same data to single record.
-
commiter can provide author data when commit added to repo. In command line case this something like: git commit --author="lillecarl <[email protected]>" Then i will be commiter and you will be author of created commit.
-
In general change make sense for me. If target mode same for 2 effects and for example expected random target selection then expected as i think same targets for both effects. Avoid relookup targets also will provide some speedup for related code part. Good catch.
-
It's meaning: if client binary allow use this world ids for zone then it will show. If client bionary not allow then you will can't do anything with it.
-
if world id listed for zone in binary you can do, if not listed then you can't do...
-
Look in http://github.com/mangos/mangos/blob/master/src/mangosd/Main.cpp#L61
Contact Us
To contact us
click here
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
Copyright © getMaNGOS. All rights Reserved.
This website is in no way associated with or endorsed by Blizzard Entertainment®
This website is in no way associated with or endorsed by Blizzard Entertainment®