Aokromes

No, you don't follow guide, guide tells you DON'T run: 2. for file in TrinityCore_4.3.4/sql/updates/world/*.sql; do mysql -u root -p world < $file; done

2013-07-07 01:00:56 (10.7 MB/s) - `500MB.rar' saved [524288000/524288000]

4.3.4 is only for development if you can't understand that, this is not your core.

https://github.com/TrinityCore/TrinityCore/blob/master/README#L65 http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry47706 --- Canned message start --- Please Look in upper right hand corner of the forum, there is a button labeled search field, feel free to search for your issues first before posting, most questions like this one have already been answered. If you still cannot find the answers you seek feel free to make a post and tell us the steps you took to resolve this issue and we will do our best to help you. --- Canned message end ---

Hosting change, for sure kingpin used one old backup.

Well, get enGB one, i don't think no one will die because that

[15:00:05] <Amit86> 4.5h to create mmaps [15:01:44] <Aokromes> Finished. MMAPS were built in 8761307 ms! [15:02:11] <Aokromes> 2,43h [18:25:41] <Vincent_Michael> Finished. MMAPS were built in 3947336 ms! XD

Unsupported things on tracker: - Levels over 100 into 6x branch, 85 on cata branch and 80 on 3.3.5a branch. - Gear modification (increased damage/hp/mana/custom models/etc). - Custom spells/items/npcs. - Ancient revisions, when reporting a bug please update at least to the current TDB version. - Non-TDB databases. - 3rd party TC branches. And to make it a little not-so-harsh for those that actually DO understand what the tracker is and use it correctly : Your feedback is, as always, important to us, and we appreciate the testing and information that you assist us with.

And now some additional information: - Make sure you are running on the latest revision of the source (we are constantly pushing changes, so your issue might have been resolved already) - When testing for bugs, make sure you are NOT running a modified core (test without ANY custom patches at all, even if it's just a tiny text change) - Don't ask when something will be fixed (it will be sorted as fast as we can, or when someone has the time to look at it) - Don't claim that your issue is "very important" (every issue is equally important to us - the only exception is when it crashes the core AND have a proper crash dump attached) - Don't claim that a change "makes function XXX unusable/unplayable" (give a FULL and DETAILED report) - Don't posts multiple bug reports on a single ticket, unless they are directly related, and no, reporting all the bugs of one raid don't fits on "directly related", because if no, we can put all the bugged quests on a single ticket

Attachement requirements: - C++ Patches : MUST be pull request, if the C++ patch contains sql attach it to the pull request, and date it 9999_99_99_99_world.sql 9999_99_99_99_auth.sql etc. - SQL Only fixes : MUST be posted has ticket, use: ```sql -- comment sql comes here ``` If the amount of rows is big, consider to use pastebin/gist and post link on a ticket on tracker. Also, it seems like certain elements in the community like to think the issue tracker is a forum, and attempts to "BUMP" issues. Here's some news to those of you that think so : Our tracker's issues CAN NOT be "bumped" - the only thing you do is add noise to the issues you attempt to bump. In short making it harder for us to actually SEE what a problem might be; don't do it!

For those that wonder what I'm talking about, here's a link to our issue tracker : Issues · TrinityCore/TrinityCore · GitHub Supplement your crash reports with back traces - any issues reported as a crash report and not having a back trace attached will be deleted on sight. DO NOT DIRECT-PASTE CRASH DUMPS INTO THE COMMENTARY FIELD - USE ATTACHMENTS OR A PASTEBIN THAT DOES NOT EXPIRE (avoid to use paste2.org) Don't post Release mode crashlogs, they are useless for devs, any crashreport on release mode is almost imposible to fix. On windows machines copy .pdb files to your server's directory, Linux uses read How-to:Advanced:GDB - TrinityCore Wiki Please note that you MUST search through the existing issues to avoid duplicate reports - duplicate reports are bad, and you're way better off adding to existing reports if they are of the same type. Also, for the simplicity of it, when filing reports, our trackers attachment feature when attaching fixes, code snippets etc. DO NOT USE PASTEBINS THAT EXPIRE FOR FIXES OR CODE SNIPPETS, IT MAKES IT WAY HARDER FOR US TO KEEP TRACK OF YOUR ISSUE/REPORT/SUGGESTION

https://github.com/TrinityCore/TrinityCore/blob/master/README#L44

Since it's your 1st instalation, drop auth database update your TC sources, recompile and import base auth sql file again, it had a bug and it was fixed yesterday.

You have cloned 4.3.4 branch and you are trying to use 3.3.5a DB.

https://github.com/TrinityCore/TrinityCore/issues/9755

--- Canned message start --- Please Look in upper right hand corner of the forum, there is a button labeled search field, feel free to search for your issues first before posting, most questions like this one have already been answered. If you still cannot find the answers you seek feel free to make a post and tell us the steps you took to resolve this issue and we will do our best to help you. --- Canned message end ---

What makes you think you need to run files dated before 2013-02-14? TDB_full_434.04_2013_02_14.7z

I am sure he got TDB 4.3.4 lower than 4.

http://collab.kpsn.org/display/tc/How-to_Linux If you are using Ubuntu 12.04 LTS or Debian 7 you will also need:sudo apt-get install libncurses5-dev

No, you don't, you need to search or read.

read wiki. Also this is not the place to learn linux.

autobroadcast was moved into auth db few days ago. And yes, he forgot to apply some sql files.

Missing updates into main auth_db import http://www.ip2nation.com/ip2nation/Download or 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) ); [/sql] to fix the bug

<div>TrinityCore rev. 6521b1aad60d 2013-04-11 02:14:49 +0200 (master branch) (Win64, Release) (worldserver-daemon)</div> You can't use 4.3.4 on master branch.

http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/