-
Posts
143 -
Joined
-
Last visited
-
Days Won
3
Dhiana last won the day on March 31 2014
Dhiana had the most liked content!
About Dhiana
- Birthday December 10
Profile Information
-
Gender
Not Telling
-
Location
cd\~
Dhiana's Achievements
Newbie (1/14)
7
Reputation
-
read Repack, read Mac, read first time, stoped reading, sorry
-
OK, if you dont solved you problem with this much useful replies where you only must use your brain and i told you what is to do, you realy should not use 434 Alpha Core. sorry
-
no, if you missed to update the configs, the server will display some kind of message like "Unknown Log Type" or somethink like meaning this. so that isnt the reason for this issue
-
Why u dont use up to date core and import _434 market sqls from core repo in your DB too ? btw. http://bit.ly/1iAvUMK
-
use your brain and your eyes and view your sql folder again. Edit: fuck... i'm to friendly to do something like that... Fix 1: Use Core Rev. from Aug 27, 2013 Fix 2: Use the SQL between Full DB and Latest, but only those which market with _434.sql
-
TrinityCore_4.3.4_DB_Alpha... Step 1: go to DB Repo Step 2: see last commit on Aug 27, 2013 Step 3: go to Core Repo Step 4: see last commit on Nov 10, 2013 Step 5: Use brain Step 6: Think there are many changes between Aug 27 and Nov 10 Step 7: Use brain again Step 8: Found two ways to fix the problem Step 9: Be Happy, -> Now it works Edit: Step 3 is already a good basic idea for on way to fix it.
-
http://www.trinitycore.org/f/topic/4116-how-to-sammlung/#entry24796
-
Du musst natürlich auch die updates aus dem Core Repo für 4.3.4 einfügen, die noch nicht im 4.3.4 DB Repo sind.
-
Ich vermute du hast einfach nur die Full DB 4.3.4 und versucht alle Updates die im Repo der Core dabei sind einzuspielen und hast das 4.3.4 Repo völlig außer acht gelassen.
-
try this: now navigate to your build, compile it and do not use "Debug" change it to "Release". BuildbinRelease <- there now your data