Guybrush

KP was working on it

They are marked with "434".

KP is fixing fixed that now.

Yes

Yes. Check the source/sql/updates/world for queries marked 4.3.4 and apply them in order. Under normal circumstances this would not be appropriate, but given recent changes, this is the temporary solution.

Depending on what the query is, you can simply remove it and reexecute the SQL. You do not need to use a specific username for your db user, so long as the credentials you're giving to auth conf and world conf are the same credentials you used when you created the db user.

What? Why are you applying sql/updates/world queries to 434? Doesn't the guide specifically say (multiple times) NOT to?

Well hell, what was I supposed to say? Glad to see he's nostalgic?

Lol...I didn't even notice that. Traitor!

Remove the first line (the one that does the ALTER table) in the SQL you're trying to run, and then run it again. OR Just run this query... DROP TABLE IF EXISTS ip2nation; CREATE TABLE ip2nation ( ip int(11) unsigned NOT NULL default '0', country char(2) NOT NULL default '', KEY ip (ip) ); DROP TABLE IF EXISTS ip2nationCountries; CREATE TABLE ip2nationCountries ( code varchar(4) NOT NULL default '', iso_code_2 varchar(2) NOT NULL default '', iso_code_3 varchar(3) default '', iso_country varchar(255) NOT NULL default '', country varchar(255) NOT NULL default '', lat float NOT NULL default '0', lon float NOT NULL default '0', PRIMARY KEY (code), KEY code (code) );

Huh? Solved? You missed the latest auth update. Check source/sql/updates/auth https://github.com/TrinityCore/TrinityCore/commit/7542049eba46205572b9c9498d6891df31d0ca5b -- https://github.com/TrinityCore/TrinityCore/blob/master/sql/updates/auth/2013_04_22_00_auth_misc.sql Read the errors you're having more thoroughly. 9.9/10 chance the error will tell you exactly what's wrong with the hope that you're capable of resolving the problem...if you read the error.

I'll say this with the possibility that it's already been said / assumed. The problem does not lay with realmlist.wtf (or authserver connection) because you know you can login. The problem rests between the worldserver and the authserver. (specifically your settings for realmlist in auth.realmlist) Make sure that: a) your port in worldserver.conf matches the port in your realmlist entry worldserver is actually running and up (run a command on console) c) everything that CDawg said above ^

Your mySQL login isn't the issue. The issue is stated just above that. Unknown column 'unit_flags2' in 'field list'This suggests a missing SQL update. I highly suggest you use the merge tool found in the DB Alpha source to create your update SQL. http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry9360 Make sure you are following the 4.3.4 guide thoroughly, specifically the part about populating the world db with TDB Full 4.3.4 and then continuing with the updates found at TrinityCore/TrinityCore_4.3.4_DB_Alpha

Revision just provides the commit you stopped at to clone the repo (or updated to) TrinityCore/TrinityCore/commits/acf6c79d9bd What do you have entered into auth db -> realmlist?

Please dear god...spoilers....spoilers! You got brownie points for providing a breakdown of your specifics, but you bummed me out when you didn't give a revision, just "latest...2 days ago". Then you really got my knickers in a bunch when you decided to copy/paste your config directly into your post. Have you no shame?

When cloning in git bash, make sure you specify "-b 4.3.4" or that you're selecting the 4.3.4 branch when you clone using Git GUI

Nothing to see here. Move along.

lmao

The wiki (instructions site) refers to the git, which changes almost hourly. You should provide a revision (select * from version @ world) so that if there is a problem with the commit, it can be corrected in addition to resolving your issue. It's hard to solve a problem if we have no idea what you're starting with.

The problem is repetition. There is tons of documentation on how to properly set up master. It's been thought out and every possible problem has already been asked on the forums. I can't count how many times Aokromes (and others) have said that 434 is not a branch intended for public consumption (yet). The assumption is that if you're attempting to build a working 434 branch, then you've mastered compiling TC with master, and running into something like an unknown column error (which immediately says "HEY YOU MISSED A SQL") should be no problem. The argument that "people with difficulty aren't getting attention" is a copout. Do what everyone else has already done and do some research. TrinityCore didn't spent thousands of manhours putting together documentation just for people to ignore it. There aren't enough people with enough time to keep repeating the same things over and over. When 434 has proper documentation and is considered more than just "in development" then you can expect positive feedback on troubleshooting actual issues. If your attempt at 434 ends at you running into the first problem you come to and giving up, then you shouldn't be attempting 434. Don't take it personally. If you do, you're seriously in the wrong place for sympathy.

Since the TDB was last created on 2/14, you will also need to apply all updates in "source/sql/updates/". This process is pretty thoroughly explained in the wiki: http://collab.kpsn.org/display/tc/How-to_Win#How-to_Win-InstallingTheTrinityDatabases

Nope. Refer to this post once you have completely patched up. Oh yeah, right. So used to typing 4.x...

Yes, it's a pain in the ass, and yes, you're screwed. But it's virtually impossible to make that mistake. Just download all the patches you need, and then apply them one by one. A patch applied out of order will refuse to patch. My advice: once you've fully patched your client, make a copy of the folder (/World of Warcraft/). This way you will always have a good copy should you need to restore. I run mine from an external so it's always there.

Make sure you are specifically opening wow.exe from your /World of Warcraft/ directory. Do not launch using the desktop icon (delete that or change the exe it points to) and do not open "launcher.exe". Doing either of these will force your client to update from official, which will bring you straight to 4.x 5.x.

Open WoW.exe and note the text on the bottom left. (it should say Version X.X.X). This is your starting point. Patch up from there until you reach 3.3.5a or 12340. Feel free to use whatever patch source you want, I just provided the one that looked the most trustworthy on first google attempt.