Paradox

-DTOOLS=1 when running cmake, If I remember correctly.

huh? the tools compile under both windows and linux (mac too, I believe) also, maps, vmaps, etc. can be extracted under any OS and work just fine on any OS, so, I fail to see the problem here.

follow the directions in the first post exactly, and there will be no problem.

illegal public servers are also still not supported...

sql updates why is that so hard to understand?

Wow, you sure are dense. When TDB structure is changed, and some external project doesn't keep up with that change, that is not our problem, that is a problem with the other project, so, go ask them to update.

Also, some people don't seem to understand that there is a difference between the end user version of a dependency, and the dev version...

You didn't properly install all dependencies, in this case, Bzip2.

If it compiles just fine, what are you doing here?

Some reason you are using a revision from July 31st? did you check all revisions after to see if there was a compile fix related to this? Edit: such as https://github.com/TrinityCore/TrinityCore/commit/f26edf09d31ce77d96c75378991c89475e5f6320

No it isn't you maroon, it's named npc_all

is your script actually named my_script? how about showing all the script and all the edits you made to scriptloader?

could you make your sig a bit bigger? I can't make out what it says, it is so small.

looks normal... the old numeric revision was removed a while back, because, you know, telling what revision you are on by reading a bunch of seemingly random numbers and letters is way easier than using a sequentially updated number...

Could you be a bit more vague, i can almost tell what version of ACE libs Mysql and such you are using, and, knowing that info will keep me from being able to help you at all. Also, if you were to post the hash revision of the core or the DB revision, etc. the mods might just have to lock this topic!

if you download the archived version from the repo, you still have to follow the rest of the wiki, such as running cmake, etc.

Wrong, try reading the server.log very carefully and look for the warning that I know is there, because I already know what the problem is.

It's because you aren't including the proper includes... this should be fixed, PCH or not.

There was never any leaked code from blizzard (unless you count the few times they accidentally released a debug exe, instead of release, allowing a bit more info to be pulled directly from the client) all work on mangos came from a previous project (same project ascent came from) that was created using the same kind of reverse engineering and sniffing that we use now (but, not necessarily as high tech as we do now) as well as a lot of hacky code that "made it work" which we try to avoid as much as possible now.

hints are so last year, when people with half a brain were using our stuff, now we have to pull out the blunt force trauma spoons...

Did you try a clean compile? sometimes file changes don't get picked up by the compiler, and, it can lead to this kind of error.

I'd stop focusing on the unstucker (stupid name) script, and, start checking to be sure the auth (also known as realm) DB is set up properly in the configs, etc. as that is where the username field comes in... in the accounts table.

I don't see username in that anywhere...

Would help if you post your script, your configs, and the names of your DBs...

Is this an existing characters DB? if it is, you need the character DB updates, if it is a new character DB (You just created it) it needs NO UPDATES.