Leaderboard

if you don't have any custom thing i sugest you to drop world database, if you have custom things i recomend you to pull to tdb 335.19031, then 335.19041.... there are to much commits betweeen your db and head.

Since we are targeting C++17 compilers, GCC 6.3, clang 4 and Visual Studio 2017 under version 15.7 will become unsupported after summer We give this warning to allow people to ready their systems with enough time to update (it's very likely Debian 10 will be shipped on 2nd quarter 2019). (Visual Studio 2019 release date is on 2nd quarter 2019) https://clang.llvm.org/cxx_status.html https://gcc.gnu.org/projects/cxx-status.html#cxx17

I wrote an article explaining why I hate most of the World of Warcraft private servers. This is my personal opinion and if you are a developer I ask you to read the disclaimer first. I'd appreciate your feedback about it, enjoy! https://github.com/FrancescoBorzi/why-I-hate-wow-private-servers/blob/master/ENGLISH.md

google arctium launcher

This table exists only to send sniffed hotfixes for db2 files that are not loaded by TC. You should never try to manually insert data into it. If you really must know - blob is simply the entire db2 row written as binary

Here, have mine https://paste2.org/PMN1IWYK

Enabling the Misc items in the cfg will post many undesired items onto the auctionhouse. The best way (so far) to get glyphs to show up seems to be the following - all credit goes to Mightylink @ cmangos. (Haven't verified all id's one by one, but assuming they are correct for wotlk) All you need to do is add all the glyphs to the force include line, this will ignore any settings and make them start appearing at random times. Here are all the glyphs sorted by class: Code: |Death Knight: 43533,43534,43535,43536,43537,43538,43539,43541,43542,43543,43544,43545,43546,43547,43548,43549,43550,43551,43552,43553,43554,43671,43672,43673,43825,43826,43827,45799,45800,45803,45804,45805,45806 Warrior: 43395,43396,43397,43398,43399,43400,43412,43413,43414,43415,43416,43417,43418,43419,43420,43421,43422,43423,43424,43425,43426,43427,43428,43429,43430,43431,43432,45790,45792,45793,45794,45795,45797,49084 Paladin: 41092,41094,41095,41096,41097,41098,41099,41100,41101,41102,41103,41104,41105,41106,41107,41108,41109,41110,43340,43365,43366,43367,43368,43369,43867,43868,43869,45741,45742,45743,45744,45745,45746,45747 Shaman: 41517,41518,41524,41526,41527,41529,41530,41531,41532,41533,41534,41535,41536,41537,41538,41539,41540,41541,41542,41547,41552,43344,43381,43385,43386,43388,43725,44923,45770,45771,45772,45775,45776,45777,45778 Hunter: 42897,42898,42899,42900,42901,42902,42903,42904,42905,42906,42907,42908,42909,42910,42911,42912,42913,42914,42915,42916,42917,43338,43350,43351,43354,43355,43356,45625,45731,45732,45733,45734,45735 Rogue: 42954,42955,42956,42957,42958,42959,42960,42961,42962,42963,42964,42965,42966,42967,42968,42969,42970,42971,42972,42973,42974,43343,43376,43377,43378,43379,43380,45761,45762,45764,45766,45767,45768,45769 Druid: 40896,40897,40899,40900,40901,40902,40903,40906,40908,40909,40912,40913,40914,40915,40916,40919,40920,40921,40922,40923,40924,43316,43331,43332,43334,43335,43674,44928,44922,45601,45602,45603,45604,45622,45623,46372,48720,50125 Mage: 42734,42735,42736,42737,42738,42739,42740,42741,42742,42743,42744,42745,42746,42747,42748,42749,42750,42751,42752,42753,42754,43339,43357,43359,43360,43361,43364,44684,44955,44920,45736,45737,45738,45740,50045 Warlock: 42453,42454,42455,42456,42457,42458,42459,42460,42461,42462,42463,42464,42465,42466,42467,42468,42469,42470,42471,42472,42473,43389,43390,43391,43392,43393,43394,45779,45780,45781,45782,45783,45785,45789,50077 Priest: 42396,42397,42398,42399,42400,42401,42402,42403,42404,42405,42406,42407,42408,42409,42410,42411,42412,42414,42415,42416,42417,43341,43370,43371,43372,43373,43374,45753,45755,45756,45757,45758,45760 | And here are all the glyphs together you can just copy and paste into the config: Code: |43533,43534,43535,43536,43537,43538,43539,43541,43542,43543,43544,43545,43546,43547,43548,43549,43550,43551,43552,43553,43554,43671,43672,43673,43825,43826,43827,45799,45800,45803,45804,45805,45806,43395,43396,43397,43398,43399,43400,43412,43413,43414,43415,43416,43417,43418,43419,43420,43421,43422,43423,43424,43425,43426,43427,43428,43429,43430,43431,43432,45790,45792,45793,45794,45795,45797,49084,41092,41094,41095,41096,41097,41098,41099,41100,41101,41102,41103,41104,41105,41106,41107,41108,41109,41110,43340,43365,43366,43367,43368,43369,43867,43868,43869,45741,45742,45743,45744,45745,45746,45747,41517,41518,41524,41526,41527,41529,41530,41531,41532,41533,41534,41535,41536,41537,41538,41539,41540,41541,41542,41547,41552,43344,43381,43385,43386,43388,43725,44923,45770,45771,45772,45775,45776,45777,45778,42897,42898,42899,42900,42901,42902,42903,42904,42905,42906,42907,42908,42909,42910,42911,42912,42913,42914,42915,42916,42917,43338,43350,43351,43354,43355,43356,45625,45731,45732,45733,45734,45735,42954,42955,42956,42957,42958,42959,42960,42961,42962,42963,42964,42965,42966,42967,42968,42969,42970,42971,42972,42973,42974,43343,43376,43377,43378,43379,43380,45761,45762,45764,45766,45767,45768,45769,40896,40897,40899,40900,40901,40902,40903,40906,40908,40909,40912,40913,40914,40915,40916,40919,40920,40921,40922,40923,40924,43316,43331,43332,43334,43335,43674,44928,44922,45601,45602,45603,45604,45622,45623,46372,48720,50125,42734,42735,42736,42737,42738,42739,42740,42741,42742,42743,42744,42745,42746,42747,42748,42749,42750,42751,42752,42753,42754,43339,43357,43359,43360,43361,43364,44684,44955,44920,45736,45737,45738,45740,50045,42453,42454,42455,42456,42457,42458,42459,42460,42461,42462,42463,42464,42465,42466,42467,42468,42469,42470,42471,42472,42473,43389,43390,43391,43392,43393,43394,45779,45780,45781,45782,45783,45785,45789,50077,42396,42397,42398,42399,42400,42401,42402,42403,42404,42405,42406,42407,42408,42409,42410,42411,42412,42414,42415,42416,42417,43341,43370,43371,43372,43373,43374,45753,45755,45756,45757,45758,45760

we don't support that wow version.

when ready.

we recommend to avoid centos to run trinitycore, because they give a lot of issues.

Our dependency versions are set to whatever ships in current stable debian release, not centos

Use https://github.com/Arctium/WoW-Launcher/releases to start wow

in case someone wonders what means "over cataclysm" only wow 4.3.4 spawns are completed. there are few spawns on mop and higher expansions but not completed at all.

EDIT: There i fixed it for the Developer, somehow i was advertising.. I notice why though, because it included my servers name. My bad... Hey guys i recently migrated a new dedicated server from a VPS so i can continue working on something and i have ran into a snag... The server is running fine, it loads up super fast, but whenever someone tries to login it gets stuck at "Connected" after you select the realm, what could possibly cause this issue? Configs: Authconfig http://pastebin.com/aiBE2jvC <- World Config, too big to put on AC-Web An image to represent the issue :/ Hope some of you can help. Thanks! Will reward +rep to anyone who posts some useful information.

Thats normal, just ignore them

100% and i use that percentage rarely. If you edit src/server/scripts/EasternKingdoms/zone_undercity.cpp only that file will be recompiled. if you edit src/server/game/Entities/Unit/Unit.cpp everything will be recompiled. unless you do full rebuild, then everything will be recompiled. also 3 hours recompile? what processor you have?

What Aokromes said is true. I will tell you any advices in case you didnt know it: - Dont use cmake if you only changed any lines in any files. Every time that you use cmake, compilation will take more time to compile. - Dont clear proyect in visual studio if you didnt add new files in the project or it will compile everything there. - You can disable tools (map extractors) of source in cmake so it wont compile with the project and it will be faster. Regards

the amount of recompilation depends of the files you change.

It is definitely still there in git history, you just need to find the correct commit or tag - however there is no guarantee that you will be able to compile it with latest compiler/dependency versions

UPDATE `creature` SET `spawndist` = 7, `MovementType` = 1 WHERE `id` = XXX;

Hello and welcome Acciderk, i can only suggest you to read over the Loot Article in the wiki, since what you are missing here is a loop through the loot reference table. The Lich King (c.e. 39168) has 5 directly attached items in his default loot template, one if them requires to be on a quest. Every other loot comes from loot references (also part of said template). I attached a picture to make this more visible/clear:

There are a lot of things that could have been written better or different, but without trying to compile this myself, there is something that really bothers me and i would say this could potentially result in your crash: You spamforce the boss an attackorder here on every update diff. The more i think about this, the more i wonder where he even gets "target" from in this case? That should not even compile. In general, there is a pretty basic and simple pattern you can follow in UpdateAI: void UpdateAI(uint32 diff) override { if (!UpdateVictim()) return; events.Update(diff); if (me->HasUnitState(UNIT_STATE_CASTING)) return; while (uint32 eventId = events.ExecuteEvent()) { switch (eventId) { case EVENT_NAME: stuff that should happen; break; default: break; } if (me->HasUnitState(UNIT_STATE_CASTING)) return; } DoMeleeAttackIfReady(); }

A lot of people have asked how to debug so I made this short guide on how to set up debugging. This guide only tells you how to actually set up debugging in TrinityCore on Windows and Linux. This will not explain the basics of debugging. You can google those or play around with the debugger to learn. Here are a few videos that explain how to actually debug after setting debugging up on visual studio: https://youtu.be/0ebzPwixrJA and linux: https://www.youtube.com/watch?v=sCtY--xRUyI This guide contains multiple guides. Each list of bullet points is it's own guide. Make sure you can run the server normally before trying to debug. Windows: On Windows before anything you should check these - Before debugging or making crashlogs etc. with Visual Studio you must compile the core in "Debug" instead of "Release". You can select this in "Build>Configuration Manager" or at the top of Visual Studio window http://i.imgur.com/5oHd59j.png - You also need to move the new pdb files generate by compiling in debug mode on Visual Studio from the compile output folder (bin) to your server folder - these files contain information needed for debugging. - It is assumed that Solution Explorer is open. Open it by selecting "View>Solution Explorer" in Visual Studio http://i.imgur.com/hkW6Gk0.png -- You may want to click on the Home icon to reset the view on Solution Explorer http://i.imgur.com/N8UPwDh.png - You can place breakpoints in Visual Studio editor by right clicking a line of code and selecting "Breakpoint>Insert Breakpoint" http://i.imgur.com/L2TxBVG.png - At the top of the window you should see controls for stepping and continuing when you have started to debug. - Here is a video showing the basic Visual Studio functionality https://www.youtube.com/watch?v=Ijdk4z8-2OI Fastest way to debug on windows. This is the easiest way to start up debugging a script. - Start the authserver and worldserver normally - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core - In Visual Studio at the top select "Debug>Attach to process...>worldserver.exe" and click "Attach" http://i.imgur.com/jDEI2Hq.png - You are now debugging The second slower way of debugging on windows. This is useful for debugging something that occurs in the startup of the server. - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core - In solution explorer right click on worldserver and select "Set as StartUp Project" http://i.imgur.com/wvMzeRA.png - In solution explorer right click on worldserver and select "Properties" http://i.imgur.com/rTNEF9O.png -- In Properties you should go to "Configuration Properties>Debugging" and edit "Working Directory" to point to the server folder. For me this is the default compile folder so I use "$(OutDir)" http://i.imgur.com/aRI29fB.png - Start the authserver normally - Start the worldserver by selecting "Debug>Start Debugging". The server will start with debugging attached from the beginning http://i.imgur.com/cg1KJNw.png - You are now debugging Crashlogs on windows. Once you have a way to reproduce a crash you can get a crashlog that can help you resolve it. - After compiling the core in "Debug" instead of "Release" start up the worldserver and authserver - Reproduce the crash you have - In the server folder there is now a folder called Crashes that contains txt and dmp files. http://i.imgur.com/9eQIdql.png - You can open the txt files in text editors http://i.imgur.com/EH6R17E.png -- At the top of a txt file there is some information about your system and below it there is the Call Stack and below that there are Variables of each part of the call stack -- The Call Stack will tell you at the top what was the last function call before crashing and what function calls led to that function call. -- Next to the function names there is the file that the function is defined in and the line number the code was executing in that function. -- In the Variables section you can inspect variables that were present at each function call. -- Based on this information you are often able to see what crashed or get a better view of what you need to inspect more in your code. - The dmp file can be opened in Visual Studio -- Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core -- Drag and drop the dmp file to Visual Studio -- In the window that opens click to "Debug with Native Only" http://i.imgur.com/OgyU2kM.png -- In the window popup click "Break" http://i.imgur.com/4jDzqRn.png -- You are now in a state like you would have hit a break point in the code or a crash while debugging. You can inspect the call stack and the variables. Edit and continue on windows. When debugging this allows you to change the code and without restarting the server apply those changes so they actually work ingame. - Open TrinityCore.sln in Visual Studio. This is what you usually open when you want to compile the core - In solution explorer right click on worldserver and select "Properties" http://i.imgur.com/rTNEF9O.png -- In Properties select "Configuration Properties>Linker>General" and set "Enable Incremental Linking" to "Yes". http://i.imgur.com/caQqwN5.png -- In Properties select "Configuration Properties>Linker>Advanced" and set "Image Has Safe Exception Handlers" to "No". http://i.imgur.com/FYzN8Ks.png -- In Properties select "Configuration Properties>C/C++>General" and set "Debug Information Format" to "Program Database for Edit And Continue". http://i.imgur.com/pxQ6I8N.png - At the top of the window select "Tools>Options". In the Options select "Debugging>General" and in there select "Enable Edit and Continue", "Enable Native Edit and Continue" and "Require source files to exactly match the original version". - Compile the server for the changes to take effect. - Set up "The second slower way of debugging" (I did not test edit and continue on other configurations) - Start the authserver normally - Start the worldserver by selecting "Debug>Start Debugging". - Try edit a cpp file a little and save it. - At top of Visual Studio window select "Debug>Apply Code Changes" and wait until the changes are applied. Warning: it can take considerable amount of time for the changes to be applied. http://i.imgur.com/77pb58E.png - If you have issues, be sure to check the error messages in Output. You can view it by selecting "View>Output" http://i.imgur.com/4cIznW9.png - This guide was written based on https://msdn.microsoft.com/en-us/library/esaeyddf.aspx and https://blogs.msdn.microsoft.com/vcblog/2015/07/22/c-edit-and-continue-in-visual-studio-2015/ Linux: First we need to compile the server in debug mode. - Compile the server with the cmake flag -DCMAKE_BUILD_TYPE=Debug Debugging on linux. You can debug on linux by using GDB. - Here is a good video about it: https://www.youtube.com/watch?v=sCtY--xRUyI - Basically you -- Start the authserver -- Start the worldserver by using "gdb ./worldserver" -- Enter breakpoints by using break command on gdb -- Use the run command on gdb to start the server -- You are now debugging - You may also be interested in using VScode or some other more visual debuggers. https://www.youtube.com/watch?v=B0xTgyCwsAo Crashlogs on linux. Once you have a way to reproduce a crash you can get a crashlog that can help you resolve it. - Take crashreport.gdb from /contrib/debugger from source folder and place it to your server folder - Start the authserver - Start the worldserver by using "gdb -x crashreport.gdb ./worldserver" - Reproduce your crash - There should be a backtrace.log in your server folder that contains information about the crash like the callstack and variables in each function call in the call stack - This guide was written based on https://github.com/TrinityCore/TrinityCore/blob/master/contrib/debugger/README Running valgrind on linux. This helps you find memory errors like invalid reads and writes and memory leaks. - Here is a good video about it: https://www.youtube.com/watch?v=fvTsFjDuag8 - Basically you -- Start the authserver -- Start the worldserver by using "valgrind ./worldserver" -- Run your code that you want to analyze and close the server -- The console or an output log should contain the valgrind log

You mean the tag? You clearly did not build the extractor from that tag. WDC3 was introduced much later

https://github.com/TrinityCore/WoWSimpleRegistration

You cannot select it manually, it will happen automatically, depending on dungeon/raid difficulty (only works inside instances)

Try clearing your cache. I also experienced same stuff. Somehow after trying lots of trial it worked somehow.

I checked and the core is master = 9.0.2.37474 and WoW version is now at 9.0.5.37988. Which means that the core and the version is not on the same level. Not sure if I am correct in this, but I am also having this same issue.

bnetserver, just like authserver in the past, doesn't accept console input.

Hi Folks, As mentioned in a later post, I no longer play WoW and decided to not port the trinitycore packages to Debian 11 'Bullseye' which was just released. I have discontinued builds and removed the packages from the repo. Thank you all for using the packages in the past few years and all of the feedback I received! Please check the 'Rolling your own' section on how to set this up for yourself! :-) Cheers! == Original message == Hi folks, Having issues compiling? Don't want to wait for an hour to compile a new server? Want a steady stream of updates? Well then, you came to the right place! With the following instructions, one can install their own TrinityCore server using pre-compiled packages. The current state of the 2 branches is: - 3.3.5a: fully functional and installable using the instructions in this topic - master: Still WIP, the packages are compiled and in the repository, but still need to be tested and validated against the installation instructions. Not compiled automatically. == Background == There are 3 packages, server, database and tools:The database package will also install MariaDB from the default Debian Repository Server package: pre-compiled version using the instructions provided on the TrinityCore wiki. Date and commit-hash are included in version tag. By default this package will also install database, but it is possible to run the database on a remote server. And it will not overwrite any configuration files in place without asking. Database package: Contains TDB335.62 with all the database updates provided by the commit. Also contains a slightly modified auth_database (which has to be setup with the provided script), so you can control the server while it's started without console (in order to run it as a service, details below). Tools package: contains the extractors, so you can run them on your desktop with the client instead of uploading a copy to the server. I also included a script that will queue all the commands you need to generate a data package for your TC server. This package isn't supposed to run on the same system as the server (because it would require you to upload a complete WoW client to your server). The packages come with a default configuration to support service control by SystemD. A few details: /opt/trinitycore - server files and data files /var/log/trinitycore - server logs /var/run/trinitycore - PID files See https://github.com/TrinityCore/TrinityCore/issues/18069 for more info on how and why == Update frequency == These packages will be recompiled everyday at midnight, compiling/uploading takes about an hour per tree, so expect fresh packages: - 3.3.5a: around 01:30 AM CEST - master: not compiled automatically (per 2019-09-09) The script will automatically download the latest TDB version if it is updated in the source files. If there are any changes with the configuration files (new options added etc.) I will add them as soon as I can. == Installation Instructions == This instruction will help you setup a TrinityCore server on a Debian Buster server with it's own local MySQL server. If you require a seperate MySQL server, please adjust where needed. All packages provided are only tested on Debian Buster stable (with updates). !!! WILL NO LONGER WORK ON DEBIAN VERSIONS BELOW 10 !!! It is in your best interest to read the entire instruction first before installing! Install a server with Debian Buster and log in on it You don't need anything except the basic install! Add the following line to /etc/apt/sources.list deb http://repo.element-networks.nl/ buster main Add the repository key for package verification wget http://repo.element-networks.nl/public.gpg -O - | apt-key add - Update your package lists apt-get update Install the server 3.3.5a: apt-get install trinitycore-server3.3.5-en master: apt-get install trinitycore-server-master-en NOTE: This command will install the TrinityCore server and all it's dependencies (including a MariaDB server) If you want to run a seperate database server, run this command with '--no-install-recommends' to skip the installation of the database package. FIRST TIME ONLY: Run the following script to setup the databases setup_database.sh If you run the database on a different server, run the script on that server. Also, change worldserver.conf and authserver.conf accordingly! Extract the MAPS, MMAPS and VMAPS using the extractors. Pro-tip, if you have a (fast) Linux (gaming) desktop, do the following: Install the trinitycore-tools3.3.5 package on your desktop with the WoW client. apt-get install trinitycore-tools3.3.5-en Go to your WoW client folder and run the script cd /to/my/wowclient generate_data_package.sh After extracting all the maps, mmaps, vmaps and dbc's it will ask you the following question: # Your data package is in /to/my/wowclient/trinitycore-data.tgz # Would you like this script to apply it on your server? y/N If you select yes, it will ask you where to upload the data package See https://trinitycore.atlassian.net/wiki/display/tc/Linux+Server+Setup for all the details surrounding the extracting process. Start the server! systemctl start trinitycore-authserver.service systemctl start trinitycore-worldserver.service You can control the server using the following command: telnet localhost 3443 Username: admin Password: ChangeMeNOW! Change the password for the admin account: .account set password admin NEWPASSWORD NEWPASSWORD Create a new user .account create USERNAME PASSWORD Press Enter again to log out Set your client's realmlist to your newly installed server GameClientDir/Data/enUS/realmlist.wtf Note: enUS could also be enGB if you have a European version of the client Start your game, log in and enjoy! == Upgrade to Debian 10 Buster == When upgrading my system to Debian 10 (Buster) I ran into an issue where my MariaDB server was no longer starting properly. In order to fix it, do the following: Make a snapshot of your current machine (and always make backups!) Before upgrading, run the following command, this will upgrade some MariaDB internals to the current version you have running. If you are already up to date, the script will say so. No need to run it with --force mysql_upgrade -u root -p Upgrade your system to Debian 10 via the usual way (lots and lots of guides already on the interwebz, find one) When you run your server on LXC, please enable Nesting and restart the LXC container again. After starting the server, check if MariaDB is running, and run the upgrade script (step 2) again to update MariaDB's internals again. == Updating == Updating the server to a newer version is very easy, I do it using the following script: #!/bin/bash # Upgrade the TrinityCore server to the latest build # Stop running server systemctl stop trinitycore-worldserver.service # Upgrade packages, change the packagename if you wish to run the 'master' branch apt-get update apt-get upgrade trinitycore-server3.3.5-en trinitycore-database3.3.5-en -y -o Dpkg::Options::='--force-confdef' -o Dpkg::Options::='--force-confold' # Start server systemctl start trinitycore-worldserver.service == Feedback == Any feedback is appreciated! I have been running my test-server with this setup for a few days now and it is still alive and kicking. However, my userbase is quite small (5) and I would like to know if the current way of updating is doable. Thoughts, feelings, emotions? == Rolling your own? == Want to compile it yourself, but make it easier? Don't trust me? Need custom patches? No problem! Below are the recipes I use for the build script I use to generate the binaries and the packages. They are still only suitable for Deb based distro's, but feel free to roll your own! https://github.com/Thulium-Drake/trinitycore-recipes

updating visual studio AND cmake.

Just download the client from battle.net app, even a trial (or "starter" as they call it now) is enough

Hey folks, I'm currently building a BfA repack, following Windows Server Setup, and at the bottom of this page it says "4. Move the vmaps, maps, dbc, cameras and gt (master only) folders to the same directory as the TrinityCore binaries." Which TrinityCore binaries is it referring to? Sorry for sounding like a div, Isk.

It sounds like you connect both worldservers into the same character database, you need to separate them and share only auth (and world if you dont want to customize anything for only one realm)

You don't need the client at all after extraction (but you will need it again if there are fixes/changes done to extractors, to extract again), you can also delete Buildings

Hi, i'm not a expert at this full topic. But have fight this issue for myself. I have solve this with this steps. Software Version use, base on the Wiki. Visual Studio 2019 (MSVC 16.2) Boost 1.70 (set Env BOOST_ROOT=C:/SDK/boost_1_70_0) Setup from boost_1_70_0-unsupported-msvc-14.2-64.exe cmake 3.15 (cmake-3.15.1-win64-x64.msi) Fix on the Master Branch. Remove or Rename \TrinityCore\cmake\macro\FindBoost.txt. So cmake pickup lastest FindBoost.cmake from C:\Program Files\CMake\share\cmake-3.15\Modules\FindBoost.cmake . To find Boost 1.70.0. Fix TrinityCore\CMakeLists.txt . Add cmake_policy(SET CMP0074 OLD) Fix src/common/Utilities/TaskScheduler.h with patch from 3.5.5 for Visual Studio 2019 see https://github.com/TrinityCore/TrinityCore/pull/2363 Keyword use const . Line ~123 /// Container which provides Task order, insert and reschedule operations. struct Compare { OLD: bool operator() (TaskContainer const& left, TaskContainer const& right) NEW bool operator() (TaskContainer const& left, TaskContainer const& right) const Mybe this helps a bit.

not confirm! use Arctium launcher not retail tools launcher and extrators https://github.com/ReyDonovan/TrinityCoreReforge/tree/master/contrib/launcher (sorry link)

This isnt a supported scenario, bnetserver has three separate build ranges that are incompatible with each other due to changes in client 6.0 to 6.2.3 6.2.4 to 7.2.5 7.3 to now

Fixed

I figured it out. I still had 127.0.0.1 set in a couple of places. I had to change the IP address in the following locations: Database: auth.realmlist.address and auth.realmlist.localaddress to 10.x.y.z bnetserver.conf: LoginREST.ExternalAddress=10.x.y.z LoginREST.LocalAddress=10.x.y.z Client: World of Warcraft\ _retail_\WTF\Config.wtf SET portal "10.x.y.z"

I do not know, with arctiumlauncher works perfectly for me. Have you tried modifying the ip address in the file "WTF/Config .wtf" 127.0.0.1? What is your SO? Some ppl with Linux have the same problem.

Hello, Which DB table, or Core files conatins the player level up spells? I need to find some spells, and modify them for a class. For example: - Hunter Disengage Spell auto place on action bar on level up. I want to change the Disengage level requirement for placing on the actionbar level req.

Two new full world database has been upload to Github Releases. TDB 735.00 (2018/02/19) was released for the master branch (previous release TDB 720.00 from 2017/04/18). TDB 335.19031 (2019/03/19) was released for the 3.3.5 branch (previous release TDB 335.64 from 2018/02/19). Notes: If you are installing a new DB you only need the 2 full SQLs plus any file at /sql/updates/world/ and sql/updates/hotfixes/ on Trinitycore repository. On 3.3.5: single full SQL file plus any file at /sql/updates/world/

TDB 335.19031 released new naming standard: 19 year 03 month 1 1st release of month.

known bug it needs to be fixed. you did nothing incorrect on your side.

No, I wanted to say that maybe different people do the same thing at the same time and nobody knows it.

for anyone wanting to test the beta irc <--> discord relay : https://discord.gg/HPP3wNh

How to add Waypoints to a creature: Note: I'm just adding a copy paste tutorial without further information on the DB-Structure behind it, because i know, you will understand this soon enough.Example: We want to add this Guy some waypoints 1.) Get the latest sniffer from http://community.trinitycore.org/topic/9849-trinity-cores-sniffer-for-wow-62020338/ 2.) Log in on retail and start the attach_sniffer and follow the Creature until it has completed it's whole path. It's important, that you DO NOT RUN OUT of sight of this mob, else the path will look really creapy. 3.) Close the sniffer if the Path is completed one time 4.) You will see a .pkt - file in your wow directory now 5.) Download and compile https://github.com/TrinityCore/WowPacketParser 6.) Go to the Releasefolder after you finished compiling 7.) Copy the .pkt-file and move the file with drag-and-drop over the WowPacketParser.exe Note: It's recommended to keep these settings <add key="DBEnabled" value="false" /> in WowPacketParser.exe.config 8.) Now you will see a .txt file in your releasefolder 9.) Download and compile https://github.com/Kittnz/WaypointCreator (Branch 6.x) 10.) Go to the release folder and open up the Waypoint Creator.exe 11.) Import the .txt-file 12.) Search for the entry in the searchfield (in this case entry: 74228) 13.) Result: - Rightclick on the table and hit: Create SQL 14.) In the SQL-Output you will now find: Use the command: .go 1923.215 -4636.423 33.2019 to see if you are on the right position 15.) Go ingame (Tc-Server) and choose a fitting creature which is near the path. In this case it's creature with GUID: 286504 - You always find the right guid if you select the creature and type: .npc info 16.) Replace the XXXXXX in SET @NPC := XXXXXX; with the GUID -> SET @NPC := 286504; 17.) Repeat this for all other Paths

As outlined in #20103, we're currently making a concerted push for blizzlike instance spawn behavior. As part of this, every instance in the 3.3.5 client needs to have all of its spawns mapped to the corresponding instance boss that causes that group to no longer spawn once defeated. Luckily, we have a tool to help with this. Extract the attached archive into your Interface/AddOns directory, then log onto a 3.3.5 core running commit fcd6fe0 (or newer). Move yourself into the instance you want to map, then invoke /spawngroup to bring up the mapper panel. Use the green plus icon to create one spawn group for each boss in the instance. If there are groups with complex conditions, like "only spawns if any of X, Y and Z are alive", create a separate group for each of them. Scroll down (shift+mouse wheel to scroll faster) and name each of the newly created groups (right-click the respective header). Names should be representative, but have only descriptive value (no need to match the boss name exactly, for example). Start assigning groups to entries and spawns in the "Unassigned" category. Pay attention to detail - not all creatures of the same entry are necessarily assigned to a specific boss. Click on an entry to expand it into a list of its spawn points. Each spawn point can be individually assigned to a group. Click on a spawn point to teleport to it. You can combine this with having the world map open to quickly map disjoint spawn points. Once you are done, click on "Export SQL" to generate a complete instance spawn group script for the instance, then post it here. Because mistakes happen, I'd like at least two, preferably three, copies of each data set, from different people. To find out which instances still need data, take a look at this issue on the tracker - contributions may be posted either there or in this thread. (PS: Feel free to take breaks. The mapper stores any mappings you've already made and will reload them when you bring the panel up again, including across sessions [assuming you log out normally - don't force kill the client.]) (PPS: Invoke /spawngroup while outside an instance at your own peril - it's probably gonna freeze your client for a bit. Lots of spawns there.)

can any one help me with this I'm getting ild/src/server/authserver/Release/authserver clang: error: no such file or directory: '/usr/local/mysql/lib/libmysqlclient_r.dylib' ** BUILD FAILED ** The following build commands failed: Ld build/src/server/authserver/Release/authserver normal x86_64 (1 failure)