Aokromes

Get TDB53 to fix your problems.

You need 2013 NOT 2012.

http://www.trinitycore.org/f/topic/9214-updated-trinitycore-requirements-c11-compilers-are-mandatory-and-cmake-289-linux-28112-windows/

You need GCC 4.7.2 or > or VS 2013. Also, we arent wizard and we can't know your exact errors. Plus pinned you have a topic for post this issues.

Trinitycore's own mac wiki was updated few weeks ago,jeremymei's changes now are unneeded. http://collab.kpsn.org/display/tc/How-to_Mac

It's that hard to read http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/ or post on "Compile or cmake problems"?

It's that hard to post on the thread called "Compile or cmake problems"?

You must compile AND use mmaps extractor again.

You missed this part: Because the TDB 4.3.4 is not always updated, usually you cannot use latest core revision: If the last sync commit in the TDB 4.3.4 repository is "Sync with TrinityCore/12345example" in the core repository you have to execute

I have shared if few times already.

And again, you have fucked your database deleting existing spawns/adding incorrect scripts to incorrect mobs YOU CAN'T apply every sql blindly only skipping 3.3.5a marked ones.

d

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

That's why i made http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/ where reading the 1st topic anyone can run updated 4.3.4 core.

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

No, the guides aren't broken, they state for 4.3.4 branch you must stay on the last sync revision. Also if you have low knowledge of sql (like myself) you can make yourself the core work on 4.3.4 head, it's not hard at all to start core and look the startup errors asking you for sql structure/new tables, if with that they can't figure what to do, i must say sorry, stop using computer because you are to stupid to read.

No, 1-3 is not direct result of lazy developers, those files must be there for people with knowledge of how to do properly things. Well help and suport forum have this description linking to that thread " Most of your questions about instalation problems have the answer -- -- -- HERE -- -- --"

1 and 2, they are temporaly there. 3 it's result of merging branches. 4) http://www.trinitycore.org/f/topic/1518-trouble-with-your-trinity-install-readme-1st-faqs/#entry42704 and still we have people asking the same question every time.

I say that TDB repo is outdated an wiki states to stay on TC revision of last TDB sync. And no, i don't contradicted myself, i simply answered the question and the incorrect affirmation on a single line.

Wiki also states to clone TC revision of the hash of the last sync. The only "safe" files to apply of TC repo are the ones altering db structure or creating new structures.

No, there are not errors on TDB updates, if you "fixed" errors on TC 4.3.4 repo you very likely fucked your db even you see your core running. Wiki is clear DON'T apply sql/updates/world files from TC 4.3.4 repo.

vmap3extractor? that's ancient, update your source.

That error is usualy incorrect db structure vs core. Wipe your world DB and pull source and import TDB plus the merge of all WORLD updates, if it's your 1st instalation import also the base for characters and auth databases WITHOUT apply any AUTH or CHARACTERS updates.

The problem is the huge desync of TDB 4.3.4 with TC 4.3.4, you need to apply a lot of files from TC repo if you wanna have a working updated repo (the ones with alter tables or create tables) or stay on the TC revision of las TDB sync.