Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Magnuss last won the day on June 18

Magnuss had the most liked content!

Community Reputation

20 Excellent

About Magnuss

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    : Switzerland

Recent Profile Visitors

2565 profile views
  1. Why you are on master branch (which is for Legion and newer) and are showing us screens of WotLK and BC ?
  2. No, I wanted to say that maybe different people do the same thing at the same time and nobody knows it.
  3. Haha, I'm wondering how much people on german p-server translate quest_complete_texts parallel and manually :-) But the quest_template_locale table contains a lot of field names from an earlier core version. Actually the relations are: quest_template:LogDescription - quest_template_locale:Objectives quest_template:AreaDescription - quest_template_locale:EndText quest_template:QuestDescription - quest_template_locale:Details quest_template:ObjectiveText1 - quest_template_locale:ObjectiveText1 quest_template:ObjectiveText2 - quest_template_locale:ObjectiveText2 quest_template:ObjectiveText3 - quest_template_locale:ObjectiveText3 quest_template:ObjectiveText4 - quest_template_locale:ObjectiveText4 quest_template:QuestCompletionLog - quest_template_locale:CompletedText quest_requested_items:CompletionText - quest_template_locale:RequestedItemsText quest_offer_reward:RewardText - quest_template_locale:OfferRewardText May it helps, otherwise please make an example of a quest.
  4. You have to use the different search options.
  5. Magnuss

    Compile or cmake problems

    Just use any new folder you want but NOT the build folder. (And also NOT c:/program files/something because they are write protected.) This configuration is the same for static or dynamic linking.
  6. I see. For caching purpose.
  7. Locking to the code I came to the same conclusion. xD Thanks for the fast fix. But I also got the impression that this table is only to save the quest status as a kind of summary. Internal the requirements seems to be checked on the fly whenever needed. What is the purpose of this table exactly?
  8. Quest templates can have up to 6 required items. Quests are working well with 6 requested items. I checked it with a custom quest. But in the table character_queststatus are only 4 fields (itemcount1 - itemcount4) that have counters for the requested items. How does this work? Is the character_queststatus only an informal table for the first 4 items ?
  9. You should set your focus on the fact you have TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 in your log. It's quite useless to search the problems at the different SQL files. If you setup the files manually it's likely you will do it wrong. If your core is up to date and has a proper commit hash incl. timestamp you don't need to take care anymore for the sql update. Everything will be done automatically. Post your CMake log. I'm quite sure there is already a warning there.
  10. Personally I think you should check why you have TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 in your log. Normally there is a new timestamp and a commit hash. Maybe you made something different by pulling the git repository. Please read the wiki again. I don't know if this is the reason for your problems with the database. But at this point I don't have any more ideas, sorry.
  11. Repack is a very bad word here in this community. ;-) You have to take an original Trinity Core as descripted in the wiki. Nothing else, otherwise we can help you. TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 shows that you have used a repack (or have done something else wrong) Or you have to ask the issuer of the repack what you have to do. TDB_full_world_335.64_2018_02_19.sql goes into the folder where your worldserver.exe is. But it works mostly only well together with original Trinity Core.
  12. Yes, that's it. Is your world database still empty or was the inital setup from the TDB 335.64 successful ? Edit: 1146] Table 'world.updates_include' doesn't exist ( Ok, I think it's still empty ;-) )
  13. The crashlog is useless. This line show that you have made something wrong or didn't use original Trinity Core: TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 As far as I remember you have to change in the worldserver.conf something that autopopulates an empty world database. Please recheck if it's on.
  14. I found 2 very simple solutions: Solution 1: Change the name back to TDB_full_world_335.63_2017_04_18.sql (or whatever you have started once with the custom project). Thanks to the magic of programming of this wonderful updater the updates are processed in the right order. The name of the full database is in revision_data.h.in.cmake . Solution 2 (not tested): Provide an own full world database file. As far as I have seen you need only to do all updates incl. custom updates into a clean database and than export it. Thanks to the table updates and its hashes the updater knows later what to do. (Additionally you may also need to save a starting file with the db structure of auth and characters at the beginning of a custom project. Depends of what kind of custom sql queries you have.)