Shauren

No, you should not need to connect to retail anymore, the patcher now downloads required modules if they are missing.

You also need clear s, v and sessionkey

Its not that noone wants to be "that guy" always. Working on this project is something I do for fun in my free time - I choose to work on things I find interesting and in most cases this does not align with what others find interesting or even important.

Boost 1.51 or newer is required. Easiest way would be to upgrade to debian 8.

No, you cant (especially not in a header!)

This just works. You run both authserver and bnetserver on the same machine/using the same database - 3.3.5 clients will connect to authserver and see all realms you defined in realmlist table (for all clients) and 6.2.2 clients connecting through bnetserver will see the same realmlist (obviously realms for a different client version will be displayed in red as incompatible) They both run on different ports by default so there will be no conflict fun fact: if you modify a 3.3.5 client to connect to any bnet 'portal' and try logging in with an email username bnetserver will pick it up and immediately return an error telling you to use old login method (this may not work anymore as noone is capable of doing it AND at the same time stupid enough to try it)

There never was any 5.4.8 version of TrinityCore.

6.2.2.20490 is the supported version (including dbcs) Thread updated.

You could apply 4.3.4/6.x character db queries if you dig them out of sql/old to get an up-to-date structure without huge losses (but I do not recomment blindly taking them all as there might be a bunch of terribly thought out queries that drop data we actually still need (drop column/reintroduce later)) At this point it would probably be better to run some database structure diff tool and start from there - as for data that no longer makes sense (deleted spells/skills/whatever else) it was never done

You are setting SAI event phase (equivalent to encounter phases, not visibility phases!) You need to use SMART_ACTION_SET_INGAME_PHASE_ID with id equal to phaseId from `creature` table however, you should take a look at sniffs to find if a spell is used for phasing instead (its very likely) - then you would just need to cast the spell instead trying to guess correct phase for spawns/sai action

Did you even verify what you changed? Your screenshot clearly shows a missing space between -uid and locale name Also none of this should be neccessary as right now we are on the same version as retail - 6.2.2.20490

This will not do anything. Transports are not managed by grids, they simply don't obey any phasing at all.

it looks like you can just pass any string, but the intention was that you use -uid wow_enGB (or whatever other locale you have)

Here is the thing - even if you do not update your client to latest retail patch, clients CASC handling defaults to online mode and tries to open online file index (which clearly is current blizzard patch 6.2.2). To force the client to use local casc index you have to launch it with "-uid wow_####" command line arg (replace #### with your locale)

Right now you cannot hide transports

The auto updater uses your worldserver config - it will only work on databases that worldserver is actually using (I see no reason for it to update world database Y when worldserver itself reads data from X)

MinGW will not work - they dont implement C++11 threading that we make use of (std::thread, std::mutex, std::condition_variable are all unavailable)

--- Canned message start --- Trinity does not support repacks. Please learn to compile and configure the source yourself, you will learn more and may even find that the error doesnt exist in vanilla TC. Please refer to the author of the repack for your questions if you continue to use said repack. --- Canned message end ---

manually, rofl