* Rename `realmlist`.`color` field to `realmflags`
* Client 2.x and later support show in realm list supported
client version for specific realm.
For client 1.x this implemented by adding version to name
in similar way as it look in more recent clients.
For enable version show each affected realm must have in `realmflags` set
flag 4.
For realm work with not officially supported builds (build > last suported)
will show version 0.0.0 and correct build value.
* Supported 1.12.1, 1.12.2, 2.4.3, 3.2.2a in same time as relams in same realmlist
* mangosd by self check correct for it client build and reject all incorrect cases
* realmd know from mangosd what builds supported each realm and
if realm not support it then in relamlist for specific client this relam show as offline.
Not need any manual settings for this.
Signed-off-by: VladimirMangos <vladimir@getmangos.com>
now they just getting executed when realmd is started
i think this will improve speed a bit.. cause we don't need to cleanup those
bans so often we just can check the conditions inside the select
* Revert realmd changes:
- typos in prev. commit prevent correct work of realmd code.
- useless log login packets
- and really horrible idea log of patch packets (how nice convert some MB in hex strings)
* Revert output world packet format to more readable old but output timestamp
* Drop outWorld, but use explcit fprintf calls into new outWorldPacketDump.
Not nice have 16 flush calls at hex line.
* Also, some minor things:
- Remove duplicate sWorldLog define.
- Add sRealmList macro for RealmList::Instance().
- Use sLog macro in scripting log functions.
* Common.h -> Threading.h -> Errors.h -> Common.h
* Remove reduncdent #include "ByteBuffer.h" in headers
* Remove redundent #include "Auth/BigNumber.h" in headers
* Avoid multyply data copy at use some now dropped functions in BigNumber.
* Avoid copy fixed byte count from byte arrays with unknown real size created from BigNumber.
The SRP-6 specifications clearly say, that v and s are only to be
calculated on registering a user and changing his password; calculating
them on every login is plain waste.
CHECK_PACKET_SIZE was pretty error prone; once it was forgotten mangosd
could crash due to the asserts in ByteBuffer.h. That was exploitable by
malicious players.
Furthermore, there were duplicate checks: Additionally to
CHECK_PACKET_SIZE, the ByteBuffer assertions keept an eye
on not exceeding the packet boundaries - just to crash the server for
sure in such a case.
To prevent memory leaks or other undesirable states, please read in
every handler all variables _before_ doing any concrete handling.
