Popular Content

Showing content with the highest reputation since 12/27/10 in all areas

  1. 52 points
    Two new full world database has been upload to Github Releases. TDB 720.00 (2017/04/18) was released for the master branch (previous release TDB 703.00 from 2016/10/17). TDB 335.63 (2017/04/18) was released for the 3.3.5 branch (previous release TDB 335.62 from 2016/10/17). 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. Import databases with the command mysql --default-character-set=utf8 -uUSERNAME -pPASSWORD DATABASENAME < FILENAME
  2. 25 points
    I guess I can speak for all TrinityCore team about this. We, and surely you people, noticed that there are people always asking the same questions... They are either too lazy to search the forum, don't know how to use it, or lastly... they don't want to search. So, before you ask a question, search on the forum for an answer. If you don't find it, search again. If you still can't find it... search again! (i know... I'm repeating myself!) And then if you don't find it, open a new thread. So, when you open a thread, remember... post a proper topic title (I will start to close all threads with topic titles like "help me" or "server help", etc...), if you are too lazy to use a proper topic title, I will be too lazy to answer to your questions. After that, in the problem description, explain what is happening, and how it should happen. Give us the most info you can... You can even copy/paste those question's and answer them on your topic: - What is your O.S. version? - What is your core version? (There is no "last version", on somedays we can do more than 1 commit, so post your correct core version) - Where did you grab it? - Did you compiled yourself? - Do you have all dependency's correctly installed? - What are their versions? (Same as the core, each linux flavour (by example) has his owns versions. So even if you are on windows, tell us the versions) - Did you Follow our wiki? - Did you correctly updated the databases? - What is your MySQL Server version? (There is no "latest version") - What is your MySQL Client Version? (There is no "latest version", and i mean the library's) - Is your MySQL correctly configured and running? - What is your MySQL client? (SQLyog? MySQL command line? etc.. NOTE: please, don't use navicat) - Did you opened the necessary ports? - Do you have any custom patches in the core? Which ones? Did you try without them? - What is your wow client version? Did you extracted the necessary files from it? And lastly... Post your conf files and realmd table in necessary cases. Note: If many of you start answering those questions when you find a problem, in most of cases, you'll find the answer by yourselves and spare us wasting time answering the same questions. And also, you won't find us to critics or narcizists. Note2: I will start to change the Warning level acording to the number of rules you guy's break. Seem that way you'll think twice!
  3. 20 points
    Since TrinityCore moved to git, I think this commands will be useful for all users. If you have some interesting commands, tricks or solutions for non-standard tasks - please, share. Download sources: git clone git://github.com/TrinityCore/TrinityCore.gitDownload sources in custom folder: git clone git://github.com/TrinityCore/TrinityCore.git <folder_name>Update sources for up-to-date version: git pull origin masterShow all branches (local + remote): git branch -aDownload sources from specific branch: git clone git://github.com/TrinityCore/TrinityCore.git git checkout -b <branch> origin/<remote_branch>Create new branch: git branch <branch>Show current branch: git branchSwitch branch: git checkout <branch>Show modifications - usually used when you commit something to your repo: git statusShow differences between two branches: git diff <branch_1>..<branch_2> git diff master..<branch> git diff <branch> (diff with master)Create patch from modified sources: git diff > <patch_name>.patchCreate patch from different branches: git diff master <branch> -p > <patch_name>.patch git diff master <branch> > <patch_name>.patchCreate patch from different commits: git diff <commit_hash_1> <commit_hash_2> > <patch_name>.patch git diff 719ffeb414c97e09469b 52cd2cbd7eb62648ae13 > <patch_name>.patchApply patch to sources: git apply < <patch_name>.patchApply patch to sources with creating of new files: patch -p1 < <patch_name>.patchRevert applied patch: patch -p1 -R < <patch_name>.patchAdd all modifications to sources: git add *Add single modifications to sources: git add <file_name>Create commit: git commit -a -m "<description>"Create commit with author: git commit --author="name <[email protected]>" -m "<description>"Show log changes: git log git log --format=onelineAdvanced log view: git log --oneline --author/commiter=<author> git log --since/after/before/until=<date> git log --pretty=format:<string> git log --summary git log --stat git log --helpRevert all changes in source code: git reset --hardRemove all except original source files: git clean -f -x -dSwitch to master branch: git checkout masterDelete specific branch: git branch <branch> -DDownload specific revision of sources (for example 10 revisions below): git clone git://github.com/TrinityCore/TrinityCore.git cd ./TrinityCore git checkout master git reset HEAD~10Switch to specific revision 1. Find commit's hash for specific revision: git log --grep=Core/DBLayer2. Find needed commit's hash. Like this one: ... commit 70a45be1594c43e09f7103c910f11a0476f88b52 ...3. Revert to specific revision with creation of new branch "DBLayer": git checkout -b DBLayer 70a45be1594c43e09f7103c910f11a0476f88b52Undo last push to your remote repository: git push -f origin HEAD^:masteror git rebase -i origin/<branch>~1 git rebase --abort git push origin +<branch> vim -> delete everything and type: noopGet all commits from specific one like patch files: git format-patch --full-index 52499b03ea8c86ab536c2025c3629b8883f591f2Get cherry-pick patch from remote repository: git log --reverse --pretty=tformat:'git cherry-pick %h # %s' | grep "\[patch"Merge remote branch to your repository: git clone [email protected]:<username>/TrinityCore.git <folder_name> cd ./<folder_name> git remote add -f -t master -m master upstream <remote_repository> git merge upstream/masterDownload remote fork to local repository: git remote add upstream git://github.com/<username>/TrinityCore.git git fetch upstream git checkout -b <branch> upstream/<remote_branch> git pull upstream <remote_branch> Credits goes to ru-mangos community, google and github help topics =]
  4. 19 points
    This sniffer is closed source, don't ask for new sniffer versions making new threads or on irc, new versions will be released when I have time. The sniffs are only available for TC developers and official contributors because they contain private data. Sniffer only works with LIVE realms and the build number stated on title/key file. How to use it: Put it on your wow directory. Start wow.exe. Start attach_sniffer. login. OR Start Wow-64.exe Use attach_sniffer_64 login. If you want to force WoW to start in 32-bit only mode use Wow.exe -noautolaunch64bit Upload your sniff compresed with zip, rar, 7z or some linux format to some non-anoying file hosting (for example zippyshare, mega, anything without captchas or wait times). Post your sniff at http://www.trinitycore.org/f/forum/13-wdbadbsniffs/ only devs will see your sniff there. Note: When updating sniffer you need to overwrite all old files. Edit by ShinDarth: In order to run the sniffer under GNU/Linux or Mac OS X you have to use the Windows client (Wow.exe) and open it using wine (get the latest version). Note: if you have the Mac OS X client already, you can just download the *.exe and *.dll files of the Windows client and add them to your Mac client folder. Instructions: - open a terminal window and run: wine Wow.exe -noautolaunch64bit Script for wine (save in the same directory as wstc) #!/bin/bash WSTC_COMMAND=$(grep -E -o 'WSTC.exe .*\.wstc' ./attach_sniffer.cmd) set -x wine $WSTC_COMMAND WSTC_7.2.5.24742_Release.zip WSTC-64_7.2.5.24742_Release.zip
  5. 13 points
    Requirements: Msysgit can either by acquired directly from git for windows or using the "SetupComplete" package from GitExtensions. Msysgit version required: 1.7+ Minimum required TC rev: b2404c1a26d9 (10997) Setup options: During the setup wizard you will encounter the following screen: Make sure your git executable is added to the PATH variable by choosing one of the green marked options. Fixes "Missing or outdated git - did you forget to install a recent version?"
  6. 13 points
    It's been almost 10 years that I'm into WoW Emulation, I can still remember the first times when I was 15 playing with the old MaNGOS. At that time I knew almost nothing about the world of programming. Now I'm 24, I work as software engineer and I'm proud of the many things that I learned thanks to the WoW emulation, that helped me a lot. A while ago I decided to make my Computer Science Master's Degree thesis about "Open Source Server Applications for MMORPG" which is about MaNGOS and TrinityCore, and the PvP statistics system that I've created for those applications. The degree was a big success and I scored the maximum grade! That is me (on the left) the day of the degree, during the speech about the thesis: I'm glad to be part of this community built by passionate people willing to share their skills with others, I always appreciated the spirit of the open source behind the WoW emulation projects and I'm writing this just to thank you all guys, for having created this awesome atmosphere during all these years!
  7. 9 points
    Core : Source Repo : https://github.com/T...ore/TrinityCore Git Pull : https://github.com/T...TrinityCore.git Database : Full DBs : https://github.com/TrinityCore/TrinityCore/releases Source Repo: same as core Issue Tracker : https://github.com/TrinityCore/TrinityCore/issues Wiki / How-tos : http://www.trinitycore.info IRC: Network : irc.rizon.net General/Support channel : #trinity IRC Clients: Windows users: http://www.mirc.com IceChat http://www.icechat.net/ *nix users: (use one of the following) emerge irssi apt-get install irssi yum install irssi pacman -S irssi pkg_add -r irssi Any operating system: webchat (online IRC client) Twitter : http://twitter.com/TrinityMMo
  8. 7 points
    I think we need a tool to allow scripters and db devs to research sniffs in a better and easier way. The tool needs to be multiplatform and license must be AGPL. The idea is you load the parsed sniff into the tool, (it needs to open huge txt files, over 1 GB on size) then: - 1st dropdown will allow the dev to select what he wants to research (for example: creature, gameobject, vehicle, npc_text, poi, waypoints...) - 2nd dropdown will list the IDs of the creatures/gameobjects/vehicles you have selected (allows multiple selections). - 3rd dropdown will list the GUIDs of the creatures/gameobjects of the ID(s) you have selected (allows multiple selections). When you select the GUID(s) under the dropdowns, you will get the coords for a creature/gameobject or creature using the npc_text or the quest of a poi. And under that, on the left, you will have the timing(s) where sniffer found the selected object. When selecting it on the right, we will see the actions performed by the object at that time. In case of waypoints allow to load maps and draw the route of the creature.
  9. 7 points
    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.)
  10. 7 points
    I see that the number of pinned posts in the 'Help and Support' section is getting large. My original thought was to try to move some of the "How To" posts to the wiki but I can't create new pages. So I figured I'd suggest instead that all posts that are guides or "How To" posts be moved to a subsection of "Help and Support" called "Guides". I know it may seem like more micromanagement for your mods but having a separate guides forum would: Allow the "How To" posts to be easily browsed (especially when they become "unpinned") Free up the pinned list for its original intended purpose: important notices Prevent the first page of "Help and Support" from being nothing but pinned posts Encourage more people to write guides (maybe) Anyway, just a thought after the success of the "solved" section which seems to have cut down on duplicate questions. Edit: I see you could actually free up pinned slots in several forums that have guides in them. In fact some guides I didn't even know whe had
  11. 6 points
    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. == 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: around 3:30 AM CEST 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 Jessie 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 Jessie stable (with updates). It is in your best interest to read the entire instruction first before installing! Install a server with Debian Jessie 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/ custom 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 master: apt-get install trinitycore-server-master 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 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! == 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 trinitycore-database3.3.5 -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?
  12. 6 points
    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
  13. 6 points
    How to Setup Debugging & Enable 'edit And Continue' in Visual Studio aka: How to Setup Debugging & Enable 'edit And Continue' in Visual Studio 2008 Update 2014-9-27: Updated the guide to remove ace.dll requirement due to BOOST support added in rev 3ba49277d NOTICE: For now you need to disable linker option /SAFESEH or it will ignore the /EDITANDCONTINUE option that gets set when you change the PDB type. To do this: Make sure you are on DEBUG configuration Right click on a project (eg: authserver) and select Properties Expand the Linker category Click on Advanced Scroll down to Image Has Safe Exception Handlers Set it to NO Click Apply Repeat for all other projects in the solution. If a project doesn't have a Linker category, skip it Update History: Some people have reported that this does not work for 64 bit applications. I struggled with this for a bit and now that I figured it out, I thought I'd pass it along The Guide: Before you start, compile the solution in Debug mode at least once to get 'ace.dll' and then copy all the following (required) DLLs to any folder, you will point Visual Studio to this later: ace.dll - Not required for sources after rev 3ba49277d due to BOOST support libeay32.dll libmysql.dll ssleay32.dll * Note: 32-bit names listed, 64-bit names will most likely be different (you should know what to look for) Step 1: Seting up the projects Step 2: Setting up the debug executable info Step 3: Enable 'edit and continue' (and other 'Debugging' menu settings) That's it. Now when you choose 'Debug -> Start Debugging (F5)', Visual Studio will launch both the authserver and worldserver and when you break execution and make changes, the 'apply code changes' will be available allowing you to 'edit and continue' instead of having to stop and recompile. Note: There are some cases you can't use 'edit and continue' Supported Code Changes Precompiled Header Limitations For more information, see here Edit and Continue (Visual C++) Some people have reported that this does not work for 64 bit applications.
  14. 5 points
    Here's a few more. PS: Either you contribute, or you're not helping. Pushing "Like" on the post isn't gonna do anything. azjolnerub.sql theeye.sql magtheridon.sql gruul.sql ragefire.sql utgardekeep.sql
  15. 5 points
    Hey all, I wanted to write down a guide about preparing your linux server to be able to work as a gdb log tracer + restarter I have been using it for around 2 years with no problem what-so-ever (other than the performance if having a compiled server with full debug flags on) What is GDB? GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed. What is Restater? Restarter allows your core to crash, fall, get stuck and come back every time without anyone touching or doing anything manualy. For this guide you acknowledge that you have basic knowledge in operating linux systems and using ssh as a cli 1. First, lets make sure your Freeze Detector is set up corretly by editing the worldserver.conf file in `etc` Find MaxCoreStuckTime and set it to 120 ( MaxCoreStuckTime = 120 ) This will tell the server that if this demon is stuck for 2 minutes the core will crash automaticly leaving the restarter at work.. 2. Make sure you have sendmail installed sendmail is a cli program that allows sending emails without any pre-setup etc Try: /usr/sbin/sendmail -f [email protected] [email protected] or sendmail -f [email protected] [email protected] If you get an email from [email protected] this means it works, if you dont -> Follow the sendmail installation guide which i found very helpful 3. Go to your `bin` folder (where the worldserver bins are installed at) create a new file - for the perpuse of the test call it `commands` (nano commands) put the following code in the file: run -c ../etc/worldserver.conf bt bt full info thread thread apply all backtrace full quit Make sure that if you are using another path or other server config name, you have to alter it in the file. The rest, leave as is, its for the backtrace report to work. 4. Create crashes folder under bin mkdir Crashes the C is capsulated 5. creatre a new file, this file will be used as our restarter, mine is called gdbres.sh (nano gdbres.sh) In the file, put the following code: while : do gdb -x=commands -batch ./worldserver > temp tail -c 60000 temp | sed 1i"Subject: Crash Log" | /usr/sbin/sendmail -f [email protected] [email protected] tail -c 60000 temp | sed 1i"Subject: Crash Log" | /usr/sbin/sendmail -f [email protected] [email protected] mv temp Crashes/log$(date +\%Y-\%m-\%d-\%H-\%M-\%S).log done tail takes the last part of your `temp` file and sends it via mail, the -c 60000 chooses to take 60kb worth of text (which is the aprox gdb crash log filesize) and just send it trough sed li = the subject of that email the last command mv temp /Crashes/blabla moves the temp file to your crash log folder, if you dont have a crash folder it wont move the file and you wont have any log keepting so make sure you created the folder.. 6. Alter the files to be able to execute: chmod +x commands chmod +x gdbres.sh 7. Starting the restarter is an easy job, personaly i use screen if you are using screen do the following: screen -A -dmS world ./gdbres.sh This will start it in a new demon screen and you can forget about starting the core on your own for a while if you are using simple cli commands you can use ./gdbres.sh && to make it start and forget about it Notes: Turning the restarter off gave me lots of problems when i wanted to close it, I started using webmin to be able to close it via their "Running programs" Positive: To update core to tip etc, you can make install then just crash it. you dont have to fully shutdown the core only ctrl+c in the screen folder or shut it down via ingame and it will come back online using the restarter Sometimes the gdb log comes back bigger than 60k, you can always go back to the Crashes folder and take the full crash.. Its usualy not bigger trough To be able to debug your core with full debug flags you will have to use -DCMAKE_BUILD_TYPE=Debug to include additional debug-code in core in the cmake proccess as stated in the linux compile guide
  16. 5 points
    This tutorial aims to simplify the compilation of TrinityCore on Mac OS X by using Homebrew, the missing package manager for OS X, to install TrinityCore dependencies, in order to keep things simple. 1) Install Homebrew For those who don't have Homebrew installed, you can easily install it typing: ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" 2) Install Xcode and Command Line Tools Install XCode using the App Store, then type: xcodeselect --install 3) Install dependencies brew update brew install mysql openssl readline cmake boost zlib brew link zlib --force 4) Getting sources Move to the folder where you want to place the TrinityCore sources, then type: git clone https://github.com/TrinityCore/TrinityCore.git cd TrinityCore If ( and ONLY if ) you want to compile 3.3.5 type: git checkout 3.3.5 Create build folder: mkdir build cd build 5) Generate the XCode project files IMPORTANT: replace /Users/username/tc-server of the following command with the path where you want to install the TrinityCore server. then type: cmake ../ -GXcode \ -DMYSQL_ADD_INCLUDE_PATH=/usr/local/include \ -DMYSQL_LIBRARY=/usr/local/mysql/lib/libmysqlclient_r.dylib \ -DREADLINE_INCLUDE_DIR=/usr/local/opt/readline/include \ -DREADLINE_LIBRARY=/usr/local/opt/readline/lib/libreadline.dylib \ -DBOOST_INCLUDEDIR=/usr/local/include \ -DBOOST_LIBRARYDIR=/usr/local/lib \ -DOPENSSL_INCLUDE_DIR=/usr/local/opt/openssl/include \ -DOPENSSL_SSL_LIBRARIES=/usr/local/opt/openssl/lib/libssl.dylib \ -DOPENSSL_CRYPTO_LIBRARIES=/usr/local/opt/openssl/lib/libcrypto.dylib \ -DZMQ_LIBRARY=/usr/local/opt/zeromq/lib/libzmq.dylib \ -DZMQ_INCLUDE_DIR=/usr/local/opt/zeromq/include \ -DZLIB_ROOT=/usr/local/Cellar/zlib/1.2.8 \ -DCMAKE_INSTALL_PREFIX=/Users/username/tc-server \ -DWITH_WARNINGS=1 6) Building the binaries Type the following to build the binaries: xcodebuild -target install -config Release I have tested this tutorial both for branch 3.3.5 and 6.x using a MacBook Pro Retina 15" running: - a fresh Mac OS X 10.9.5 (Mavericks) - a fresh Mac OS X 10.10.3 (Yosemite) - Mac OS X 10.11.3 (El Capitan) and it worked fine, give me your feedback.
  17. 5 points
    Hello A small presentation: I’m Yehonal an old dev of wowemu ( by WAD ) and original MaNGOS. Founder of Mangos Zero and dev of TrinityZero. Introduction: Recently i’ve proposed to trinitycore a new structure that allows to separate core functionalities using a modular architecture. This structure allows you to use this project as a real MMO framework. In few words you can choose to: Download only the framework and develop your MMO application Download the platform, based on framework above, to implement an application that supports wow client, or just download the entire server application. Download other modules that extend application above ( For example: AHBot, Duel Reset and other custom things ) This kind of approach allows to enlarge the project audience and possibilities. Unfortunately it hasn’t been accepted The Project: http://www.azerothcore.org I’m here to present you a new Project , called AzerothCore. It’s based on Sunwell Core and of-course TrinityCore and Mangos , but completely restructured to allow: Modules creation: as said , you’re currently able to create/install modules that extends core functionalities without touch any line of core code. So you can have installable extensions that don’t require patches, such as: Duel Reset, Transmog etc. You can also easily publish yours that can be pinned by our staff and included in our official extensions list. More info: here Doing Versioning right: We have various stable and supported versions. Instead master branch is always in development. We have an API that will only change between major revisions and you don’t have to take care about compatibility updating your minor versions More info: here Create something that just work: We’ve based our project on Sunwell Core because they fixed 90% of game contents. Yes, they made a lot of hack fix, but we’re working on code enhancement. However we’re not hack-aware and we won’t be: if we’ve to release a major revision, it must work at least as the previous one and must be stable. So we can accept patches with hack fix and fix in a cleaner way in master branch instead. Fully Open-Source and Free Tools We’ve based our infastructure on github and all its service to guarantee you open and reliable services. We’re also working on a webserver that will contain a demo of all our supported applications. Such as Shin’s tools and a limited game server for demo/testing purpose only. What do you think about this? Help us to develop this great project!
  18. 5 points
    Well I did not know in what forum to post this so I thought this one would be the correct one. I just wish to say a big THANK YOU! to the TC team, and others who support it and are contributing. Me and my friends recently got tired of playing on retail and wanted to go on a little nostalgia trip with WotLK and while we could have played on other private servers, we thought of seeing if we could make our own, thus we found TC and decided to try it out to see if it's possible. Well after the informative guide here: https://trinitycore.atlassian.net/wiki/display/tc/TrinityCore+Home , we managed to successfully make it. So, we currently are playing and so far everything works normally (with very little very minor bugs found). We wanted to create this thread to just say thanks to the TC for the making of this project and others who contributed to it. We would contribute ourselves, but we barely know any programming/coding. Thanks and good luck in the future.
  19. 5 points
    2014-01-24 Clarify the "before you start" section to account for clients copied to new machines Clarify how to check the Launcher version Clarify when to run backgrounddownloader.exe Fixed some typos, missed some typos and probably even made more typos Update history: I've put the guide in the spoiler below since it involves a LOT of downloading (approx. 20 to 25 GB), I thought I'd caution you first so you can decide if you want to find alternate means. Step 3: Install the patches IMPORTANT: I can't stress this enough NEVER run Launcher.exe IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too This set of instructions should work for all the patches you've downloaded regardless of what instructions they came with. Take a minute to read them before you start and keep them handy for reference. Patches uploaded by other people might be a bit confusing. Take a look at the "_instructions.txt" file in one of my patch archives for help. Before you start: If you have more than one installation make sure you run WoW.exe once to get the proper installation path in the registry or the patch might try to modify the wrong installation. If you've copied your wow client to a new computer, make sure you run WoW.exe once to get the proper installation path in the registry or the patch won't be able to find your installation Pre-Patching Make a backup of your 3.3.5a client Copy "base-Win" to the "Data" folder Edit realmlist.wtf change "realmlist" and "patchlist" to point anywhere but the official servers ( is a good choice for now) Edit or create launcher.wtf in the "WTF" folder Make sure the contents are the following: Note: Check this file after each patch, some patches may delete or change it. Replace it if they do Apply the patches in order * Note: If you have a Cata DVD then use that and skip wow-3.3.x-to- Extract the patch archive to a temporary folder Copy the patch contents to the appropriate folders in your WoW installation If the patch contains an EXE, copy everything to the "Updates" folder These (and only these) types of patches can be deleted when finished If the patch contains a "wow-patch.MPQ" and a bunch of MPQ files, copy "wow-patch.MPQ" to the WoW root (overwriting) and copy the other MPQs to their appropriate folders (usually same folder structure as the archive) If the patch contains a bunch of MPQ files without a "wow-patch.MPQ", put them in the appropriate folders (usually same folder structure as the archive) Important: If this type of patch does not contan a "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision) then you will need to download the collection at the top of the guide and extract it. Place this in the "Updates" folder. Apply the patch See Notes section below if you get errors trying to apply the patch If the patch contained an EXE, run the EXE If the patch contained an update script (my uploads), run the script If you have the "wow-patch.MPQ", just run "Blizzard Updater.exe" If you have a file such as "wow-0-xxxxx-Win-final.MPQ" (where xxxxx matches the patch revision), run this from your WoW root: Run "BackgroundDownloader.exe" to see if there is additional patch info only after the following patches: wow- wow- wow- Make sure your tools are updated by checking "Launcher.exe" (right-click -> properties), the version should be Run the tools updater if it isn't (don't run the launcher) Copy the MFIL / TFIL from the collection you downloaded to the WoW root Overwrite any that came with the patches Run "backgrounddownloader.exe" The first two will download approx. 7 GB, the last approx. 4 GB When finished, run WoW.exe (not Launcher.exe) Follow the guide for setting up a server (make sure to compile the tools) Edit "realmlist.wtf" and point "realmlist" and "patchlist" to your server's IP Patch WoW.exe This is required or you won't be able to log out, every NPC will be "Unknown" plus a host of other problems Run WoW.exe (not Launcher.exe) Allow it to connect to Blizzard's servers to check for additional data Log in, create a character and enter the world If it is downloading, there will be an arrow over the system menu button. This uses a slow UDP pulse so it may take several days. Just leave the client running. The final client size after patching and optimizations performed when WoW.exe is first run is approx. 15.7 GB (confirmed by +CDawg who collaborated on the process) Notes: If at any time you have trouble installing a patch, you may need to do one or more of the following Copy "base-Win" to the "Data" folder (this file sometimes gets corrupt) and try repatching Update the tools (BackgroundDownloader, Blizzard Updater) Oh, did I mention: IMPORTANT: I can't stress this enough NEVER run Launcher.exe Oh, did I mention: IMPORTANT: I guess I have to remind people to block Blizzard's servers in their WTF too ---------------------------------- End of Guide ---------------------------------- Forum Mods: You can close the following threads since they will be obsolete http://www.trinityco...tion-available/ http://www.trinityco...2-10-23-334-pm/ http://www.trinityco...patches-where/
  20. 5 points
    TortoiseGIT guide moved back into its own topic for easier seaching / discussion until I can put it on the wiki. It shouldn't have been merged into the middle of a discussion about the commandline.
  21. 4 points
  22. 4 points
    A lot of people have asked how to debug so I made this short guide on how to set up debugging. This will not explain the basics of debugging. You can google those or play around with the debugger to learn. There are guides for Linux and Windows. (though linux is not as detailed) 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. 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 First off we go with the 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/ 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. - Compile the server with the cmake flag -DCMAKE_BUILD_TYPE=Debug - 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
  23. 4 points
    Please read and understand the following : What we require when you file an issue : VERY IMPORTANT, WHY THERE IS NO LATEST: on github after 1 month we can't known the date the issue was posted, and because that we can't known the revision Never ever test things with GM accounts - Update your core before reporting a bug, the bug of ancient cores can be fixed on newer cores. - Add which revision of Trinitycore you're running on (this is the CORE revision, not your client version) - Add which database, and what revision, you run on. Remember, you can get the most updated TDB from Downloads · TrinityCore/TrinityCore · GitHub - Add a list of which modifications that has been done to the core (if any) if those modifications aren't public available you must share the code if you/we see that they can be reason of bug, if you don't use a clean core and you don't share the code if it afects the bug or the files of the bug (crash) the ticket will be closed. - Supply links, spell ids, full spell names, npc ids, npc guids, npc names, gameobject ids, gameobject names detailed, we don't must guess what mob/instance/spell you are talking about. addon to help you with ids: http://www.curse.com/addons/wow/spellid#t1:other-downloads get 3.3.5a version. Example CORE revision number : b1e2cdb905d6a92edeb505eff968d26c453b252b (LAST is not a valid number), there are 40 Time Zones from UTC−12 to UTC+14, we don't known on what Time Zone you live, for me Today is 31 of July, for someone on Honolulu it's 30 of July. Read Howto properly install git on Windows. - Help and Support - TrinityCore if you can't get something like TrinityCore Hash: c4818f189216+ (Win32, Release (little-endian)) (worldserver-daemon) when you use server info on console. Example DB revision number : TDB 335.51 The above is VERY important, so add this when reporting! Any ticket without this info will be closed without notice.
  24. 4 points
    Database install errors Please note that the software called Navicat is NOT supported due to issues with how it handles SQL-files with "/* */"-style comments. We advise all users to stay well clear of this program unless they really are looking for issues. TCE00001 My core don't starts i get: [1146] Table 'world.updates_include' doesn't existYour database structure is not up to date. Please make sure you've executed allqueries in the sql/updates folders. Maybe you are updating one very ancient core and missed some sql, easy way is drop all your trinitycore databases (auth, character, hotfixes, world) and leave core to import the databases if you don't care about data. Another way can be create temporally the needed databases and allow core to import the sql files, then export the updates and updates_include tables from those databases and import them to your production core (be sure you have updated your databases to max before import the updates tables to your production core). REMEMBER: core needs one user with create table/alter table/drop table permisions. TCE00002 My core don't starts i get: 2012-07-11 16:47:10 ERROR: DatabasePool world NOT opened. There were errors opening the MySQL connections. Check your SQLDriverLogFile for specific errors. 2012-07-11 16:47:10 ERROR: Cannot connect to world database;3306;trinity;trinity;world Unknown column 'level' in 'field list' 2012-07-03 23:01:12 ERROR: E:TrinitysrcserversharedDatabaseMySQLConnection.cpp:531 in MySQLConnection::_HandleMySQLErrno FATAL ERROR: Your database structure is not up to date. Please make sure you've executed all queries in the sql/updates folders. This means DB structure was changed, you need to apply the sql files found at sql/updates (this also can mean you have updated your db structure but you forgot to install the updated core) If you use the most updated master branch and you don't have custom things DROP your world database and get the most updated TDB from GET TDB then apply the sql files found at sql/updates. If you can't or you don't want to drop your world database or droping world database don't fixes your problem enable SQLDriverLogFile on your worldserver.conf file. If you get those errors whatever you are trying on world database, use http://www.trinitycore.org/f/topic/43-windowslinux-combine-sql-updates/ to create a 2 files instalation system to be sure you don't miss any sql file. Under Linux you can use rgrep <insert here the missing column name> sql/updates/*.sql to see what file you miss. Under Windows you can use notepad++ or ultraedit 32 to search the file you miss. Anyway if you have world db structure problems, we sugest you to DROP world db and import TDB + updates again, because maybe you have missed some. TCE00003 My server don't starts, i get: >> Loaded 0 trinity strings. DB table `trinity_string` is empty. This is because you forgot to import world database or you have enabled autoupdater but missed to put world database on the worldserver directory or imported travis world database instead proper database. If you get "unknown column" or "unknown table" error it can be because 10 reasons: 1) You have cloned master repository (3.3.5a) and installed TDB, but you forgot to apply the files present on sql/updates/world you need to run those to properly start core. 2) You have updated your database, but you forgot to update your binary files, you usually can't run older cores with newer databases. 3) You have updated your core, but you forgot to update your database, you usually can't run older databases with newer cores. MOST COMMON CASE 4) You have download 4.3.4/6.x databases, but you cloned 3.3.5a repository you can't use 6.x/4.3.4 databases with 3.3.5a core. NOTICE use one very high range to avoid to get your spawns/scripts deleted when a new TDB is released unless you drop the full DB when updating. NOTICE2: if you don't drop your world database you will end with double spawns. 8) You are trying to use a custom patch and you forgot to apply the sql files for it or they don't exist. 9) You are trying to use one sql for another project or deprecated sql files. 10) You are trying to apply the same update 2 times.
  25. 3 points
    Since we are targeting C++14 compilers, GCC 4.9 and Visual Studio 2015 will become unsupported 1 month after the release of Debian 9. We give this warning to allow people to ready their systems with enough time to update (it's very likely Debian 9 will be shipped on 2nd quarter 2017). (Visual Studio 2017 release date is March 7)
  26. 3 points
    Very interesting video I've been looking at for the last 10 minutes, still a lot more to watch. Thx dfighter for sharing it "How to Protect Your Open Source Project From Poisonous People"
  27. 3 points
    TDB 720.00 & TDB 335.63 released.
  28. 3 points
    And another new purple, Ariel- https://community.trinitycore.org/profile/22941-ariel/
  29. 3 points
    5 years later, yes, it's possible. https://trinitycore.atlassian.net/wiki/display/tc/Using+the+script+hotswapping+system
  30. 3 points
    TDB 6.04 & TDB 335.61 released.
  31. 3 points
    I 100% agree with that. I won't lie, my children and I play on it from time to time, but we also both LOVE creating new things in the code. I don't think I would ever have the patience (or desire) to run a public server. Learning how to write changes and learn how different changes affect the client and overall game play. Because of what my kids are learning with (First Mangos and now) Trinity core... One of them now wants to be a video game designer when he grows up. Couldn't ask for a better educational purpose than that. He will be able to walk into a college level class and explain EXACTLY how a database / client / server game works.
  32. 3 points
    Nex4T, It takes more work to do things properly... In all things.
  33. 3 points
    Here is the thing - even if you do not update your client to latest retail patch, clients CASC handling defaults to online mode and tries to open online file index (which clearly is current blizzard patch 6.2.2). To force the client to use local casc index you have to launch it with "-uid wow_####" command line arg (replace #### with your locale)
  34. 3 points
    I would like to request an archive of the Wiki for the tables related to 335 for those who wish to continue using / developing that branch. Once table structures change for 6.x, it will be difficult to maintain a 335 repo if the reference material is updated to the new structure without archiving the old structure. Thanks!
  35. 3 points
    Hi everyone! We're looking for new developers to assist with enhancing TrinityCore with proper SOAP/REST-based webservice-support - there's no pay, but a lot of glory! People that wants to get involved will get : *) a free copy of the TrinityCore sourcecode (available on GitHub, all yours for the picking!) *) opportunities to swear at the other devs in our IRC developers-channel (who doesn't want to do this?) *) lots of gray hair (unless hairless, like me) *) your code inside one of the most fun codebases to work on What we're aiming for: *) To actually start using the gSoap-library we've got in the sourcetree for something else than just being a mediator between executeCommand and prettified XML output. *) Exposing more functions to the public than is currently done - we have _1_ (one) function active per today - we're really awesome-sauce aren't we? Some minor, but important, requirements: *) You need to know how to code in C++. *) You need to understand how SOAP/REST works. *) You need to have a keen eye for details to avoid doing the same funny/silly/scary/whatever mistakes that the rest of us do all the time... If YOU want to assist in creating this, please give us a note here on the forums, or on IRC for those of you wandering by there!
  36. 3 points
    as you might be able to see above there is a new custom search box on the forums, if you cant see it its because of your adblock, please consider removing our site from adblock as I promise we have no ads on the site, none, zero, zilch so you wont be bombarded by ads if you whitelist TC . this search box is a combination box that parses all of the TC sites / sections and gives a singular search location for everything at once. You get: the wiki the forums the sourcecode on github the issues on github pull requests on github doxygen docs irc logs from #trinity on rizon you can refine your search to specific sections using tabs at top of the results : the results are labeled and show full URL. search away and let me know how it goes for you it is being improved over time so there might be changes.
  37. 3 points
    Let's stick to the facts here. OP is oblivious on how to proceed in order to get his server working because he either a) doesn't understand a word of English and could not understand the error message in the console even if his life depended on it, or b.) is too ignorant or uninitiating to consult MySQL package instructions or google for upgrade directions. These possible causes may have deeper rooted issues such as clinical retardism, lazy parenting or, indeed, sir was an avid repack user in the past. Please convince me why the fuck we should judge and not deal with the facts at face value - ignorance is bliss. This is a learning project after all, and we should not deprive one of the chance of learning because of his alledged past. If you feel the need to bash someone, fine. But base your conclusions on facts for which you have probable cause, and keep your witchhunt theories to yourself. You know what's been here even before that? Cancer. I guess we should defend and worship cancer too. Paradox, you need to stop getting your panties up in a bunch. They're soaking wet from menstrual blood and they're leaving a rotten stench within the community.
  38. 3 points
    Pinned. I, for one, didn't like the merge, I think each guide must be in a separate topic as long as they cover separate aspects of a problem.
  39. 3 points
    should be fixed, confluence was going mental.
  40. 3 points
    Well there was the post where I directed some idiot running a public server to Paradox for information pn TC's dev support plan. np though. I'll catch the next idiot
  41. 3 points
    For a second there, I thought you were talking about rbac, and I got this hilarious picture in my head of a player that can move any direction but forward, because each direction has its own rbac permission, and his forward moving permission was revoked
  42. 3 points
    +delro +rkm +MrSmite testing testing a simple +username[/CODE] Caps DONT matter.
  43. 3 points
    A crash a day keeps the mem leak away. ™
  44. 3 points
    Ok, I expect you will be able to provide the build farm capable of fully testing TC on all supported host OSes, then? Windows, various Linux builds, and OSX would be great. Just post up here where the devs can remote into to test every build change first. Thanks for being such a supporter!
  45. 3 points
    Who ever this gregarious person is, I don't know what it is you think I have done to you, since you are too cowardly to confront me directly, but, stop negative repping me for no reason.
  46. 2 points
    If you follow all steep here https://www.trinitycore.info/ you must be able to run the server without major problems, assuming you have an unmodified client and using the tools compiled with the server. Just follow the instructions and you will not have problems.
  47. 2 points
    Hi all! I've created a script that will generate a data package for your server and added the instructions on how to use it in the post. I've just added it to my build environment, so it will be ready for use tomorrow! Cheers!
  48. 2 points
    I believe this is the latest TrinityCore 4.3.4 branch before it was dropped: https://github.com/Nickelangelo/TrinityCore/tree/4.3.4 You can find latest DB that was released: https://github.com/Nickelangelo/TrinityCore/releases/tag/TDB434.09 I just found out this: https://github.com/TrinityCoreLegacy/TrinityCore/commits/4.3.4
  49. 2 points
    Fixed: https://github.com/TrinityCore/TrinityCore/commit/51287930cb147cace9308713d0affddbf38df4d8
  50. 2 points
    lol, that's better than banning