Paradox

+1 me too.

Just like you will come down and spend some time with our love child... you are such a liar.

Hopefully, by the time I feel like mucking about with a 4.3.4 server, someone will have PM'ed me the location of this client (torrent or whatever) and I will have downloaded it...

I'm sure he must have meant while 4.3.4 was still current...

doh!

someone else's extractors will likely not help you, you need to get a FULL client that has been fully streamed for 4.3.4.

what link? the one at the top of every page works just fine, is there another one you are referring to?

Also make it more clear that asking how to write code, or what function does what IS NOT a help and support issue, and should not be posted there...

Make sure you have applied any Service packs that are available for your compiler, make sure you have installed all of the necessary runtimes, etc. and, also make sure you are using a C++ version of VS .NET and not, say, C# or VB .NET only version... Edit: Just noticed so, it is a C/C++ version. make sure some of your dependencies (such as mysql or openssl) are not 64 bit, since you are using a 32 bit compiler...

DO NOT USE NAVICAT. it is pure shit.

I signed out, waited over 10 minutes and tried, still logged out, it must be some kind of auto login you have setup and don't realize it.

obviously, you don't have a user named trinity, probably because you used either another server in the past (such as mangos or whatever Ascent is calling itself these days), or, you were previously using a repack that used a different user in the DB, and, in either case, used the same DB setup when you switched to TC. In any case, you shouldn't be using the create mysql sql without using the one that creates the trinity user.

Your logic is backwards, since you are too lazy to install the mysql 32 bit client, you NEED to use the mysql sources that come with TC....

Staying on the old release is fine, as long as you don't update the DB, thinking that it will benefit you somehow.

Two months ago... UPDATE!

a two month old repack core? compile your own a new core. or, you can stay on the DB for that core and not apply updates.

Probably another one who thinks he can update his repack by applying new sql updates.

What part of no support without a valid revision, and no support for 4.3.4 at all, do you not understand?

Funny how you keep leaving off the core revision info... is there a reason for that?

We don't openly help with illegal public servers here, just saying...

Some people don't seem to understand that if you buy a Ford conversion van and then contact Ford to ask why your TV isn't working, they will tell you, while we did make the original frame, engine, etc. for your vehicle, we did not put the conversion body or any of the seats, carpeting, or, even electronics in it, and cannot provide you with help on your issue, please contact the company that actually did the conversion for help with those issues... the analogy isn't perfect, because Ford can generally, still help you with issues you have with the parts they did build, because they have records that show what was changed by the conversion company, and what they put in it, while we don't have any clue whatsoever what the repacker changed, and, so, we just steer clear of supporting "conversion cores" at all.

traitor? I didn't realize we were competing with a defunct 2.4.3 fork of our own repo...

did you try using some port other than 8085? maybe your host has gotten tired of wow server kiddies and has enabled some kind of packet dropping for the port 8085...

This is a very common response I get. From the outside the insane seem to be insane, from the inside,they seem to be geniuses... not trying to say I'm a genius, but, hopefully, you get the inference.