Jump to content
TrinityCore

Leaderboard

Popular Content

Showing content with the highest reputation since 03/21/17 in all areas

  1. 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
    8 points
  2. 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.)
    8 points
  3. 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
    7 points
  4. Feel free to participate on TC Github and share your and your team of developers knowledge.
    4 points
  5. Will NOT be updated anymore. Source code https://github.com/Shauren/WSTC
    4 points
  6. 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/
    3 points
  7. 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
    3 points
  8. TDB 735.00 & TDB 335.64 released.
    3 points
  9. Hello TrinityCore community! I do know that TrinityCore is provided with an anticheat program but how good is the anticheat system? Once I had a repack, it was an old one from TrinityCore, but still I was able 2 hack myself without my anticheat-program detected anything. Also I would like 2 thank @CDawg and @HannibalRoG for their patience when they helped me in my last topic. I can now say that my server is up and running and I was able 2 have 10 people online without any laggs at all!
    3 points
  10. 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
    3 points
  11. Is it true that now for the use of Sniffer on 7.3 - Blizzard begin to block accounts? So you are silent that there is no information about the update on the new build? *before release 7.3 Blizzard renewed the license agreement. http://eu.blizzard.com/en-gb/company/legal/eula
    3 points
  12. 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.
    2 points
  13. 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
    2 points
  14. 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
    2 points
  15. 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
    2 points
  16. 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
    2 points
  17. Here, have mine https://paste2.org/PMN1IWYK
    2 points
  18. Let me first be clear on one thing: I do really appreciate this project, its history and developers and all the efforts that have been made with time to make it so great during all those years. But currently WoW development is slowly dying, and I feel a big change is needed in order to bring back that entusiasm that is no longer here. The current state of the project has some major pain points: - CONTENT. All the content after WOTLK is not stable or complete, so it doesn't add much value to keep what we currently have on master branch; - CONTRIBUTORS. We have less and less contributors, there is no much hope to see the master branch fully playable in future - CODE. The code is full of anti patterns (huge class files, spaghetti code, etc...). This is mostly due to the fact that the codebase has been modified for years and years by many different people. Because of that, it is really complicated for newcomers or less experienced programmers to be able to contribute; - TESTS. There are no tests. At all. No unit test, no integration tests, etc... It is nearly impossible to be sure that you don't break something whenever you make a change in the code; - API/TOOLING. There were some attempts on providing tools for TC (which I really appreciate), however most of them rely on accessing the DB directly OR using external PHP APIs that are not standardized by the project and tend to break easily with time (e.g. when the DB structure changes). Ideally the application server itself should expose the API, or the API project should be part of the official project and be maintained with it; All those reasons, together with the fact that C++ is an old language and there are better modern alternatives make me wonder: why don't we start a new project from scratch, using a modern language? (for example Rust - see this post). So we can use the experience gained during all those years of WoW development to create something that works better, is more developer-friendly and can attract more contributors. I write this post to see if this can be of interest for any of you, please let me know what you think.
    2 points
  19. I'm guessing no one knows apart from those who have managed to fix the issue themselves. However @Aokromes i did find this. struct EuropaTicketConfig { bool TicketsEnabled = false; bool BugsEnabled = false; bool ComplaintsEnabled = false; bool SuggestionsEnabled = false; Would changing the value from false to true yield any results? bool TicketsEnabled =true; Regards, Xedara
    2 points
  20. You could have just asked for it. The reason I didn't throw it up on a gist or dropbox public site was due to people pinging me outside of TC and bugging me for updates and filling up my email/discord channel for the armory. The web app layer is not 100% working. So no... my 1400+ posts have never been about an "every man for himself" attitude. Next time, *your* approach could be, "Hey CDawg, why not share it publicly?"
    2 points
  21. Got it. It caused a 6 month roll back on the characters database but it's fixed. I had to manually run the updates.Before anyone asks of course I was backing up the databases, but the most recent ones were corrupted by this issue and I just happened to have an older local copy I could work with.
    2 points
  22. Hi, I want to use Warden, to detect weather a player is using PQR. First I decompiled PQR and found out that the programm injects some LUA code into the client. If I use /run print(SOME_PQR_VARIABLE) before starting PQR the output will is nil as expected. If I use /run print(SOME_PQR_VARIABLE) after starting PQR the output will is a value/adress/none depends on what I print. In the Warden.h there is this Check LUA_STR_CHECK = 0x8B, // 139: byte luaNameIndex (check to ensure LUA string isn't used I created a warden_ckeck in the DB with: INSERT INTO `warden_checks` (`id`, `type`, `data`, `str`, `address`, `length`, `result`, `comment`) VALUES (1, 139, '', 'SOME_PQR_VARIABLE', 0, 0, '', ''); Unfortunately the client always returns 1. No matter if PQR is injected or not. And this is my Problem. Either way this type of Warden check is not properly implemented yet or I do something wrong with the SQL statement. injected_pqr_code.lua
    2 points
  23. I just have to say that this project is amazing. I am having SO much fun. Thank you, everyone who contributed to it. It took me a couple of days to get everything put together, on my spare debian machine, but it works like a champ (even with older hardware).
    2 points
  24. c++14. (we warned MONTHS before release and make definitively unsupported MONTHS after release)
    2 points
  25. It did, i have been able to work on the core all day without the issue reappearing
    2 points
  26. I have heard of this issue on 7.2.5 but not 3.3.5a are you sure you are not using anything custom and everything is from a fresh start including your core files just checking because everything seems to be working like it should for me including 4.3.4
    2 points
  27. Meh.. Not really explosive. Just defending the fact that people consistently "demand" things from the community and devs. Sometimes they offer money and when they don't get an answer they are the ones that explode. If you knew me, I'm a very very laid back guy
    2 points
  28. Honestly, I think it will be a positive outcome. @Ibeatdungeon, you have to take into consideration, that most players expect the hard grind, including the lack of new features such as, LFD, LFR, old quests you have to look up on "Thottbot", like back in the days. Blizz is (hopefully) giving the players that same feel. The population may slowly fade. But,... you will still have loyalists that just pay. Remember, it isn't about the content.. It's about the community that develops around it. Not to mention, people that have never experienced classic will bitch about missing features that they are accustomed to today's wow. But they will be slammed down by the loyalists to keep it the way it is. Blizz will have to launch a new client with new graphics, etc. It all depends on the outcome and I'm excited to see that very outcome play out.
    2 points
  29. It should be pretty obvious. Just show him how it's configured for "master" https://github.com/TrinityCore/TrinityCore/blob/master/src/server/bnetserver/bnetserver.conf.dist#L76 Rather than complain, then show both options.
    2 points
  30. Original poster https://www.lifewire.com/what-does-o-p-stand-for-2483372 http://www.urbandictionary.com/define.php?term=op http://lmgtfy.com/?q=what+is+op+on+forums A repack is where you wont get support. It's a pre-comiled server package for people that are incompetent on building their own server. You get no updates, you can't fix core problems, and most of the time they are extremely outdated with so many bugs locked into a pre-compiled core that you have to deal with. @Chrisseria2520 You said it best... You just explained that you had a negative experience with a repack (one of the largest) You had a guy that was able to cheat and hack your "repack" and there wasn't a single thing that you could do, due to someone else that created the server in a package nad not able to add special detection and core functions within a repack. Look... People are lazy, i'm not saying you are. But don't let one small issue you run into block you from giving up. It's very very while worth it to compile your own server. Not only can you make custom modifications and keep your package up to date, but you will learn a lot from it and have the confidence to tell your friends that you may be able to fix a certain issue - since you will get support.
    2 points
  31. 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.
    2 points
  32. To answer your question. Yes it isnt a problem to install both libraries. But please notice that you are using an unsupported version of trinitycore
    2 points
  33. While the guide isnt perfect, it still captures the most important parts and is good enough for the job. Some of the issues you listed sound like user errors. You are clearly presented a way to create a new user in the mysql installer. If you did not have this view, then you are possibly using some other way of installing MySQL that was unexpected or the installer may have changed over time. https://i.imgur.com/ceQRzfk.png https://i.imgur.com/81Rq8Lz.png You are clearly instructed to leave the subdirectory field empty. Then it will not create a subdirectory. Seems you missed this? https://i.imgur.com/XgRZZjT.png The issue was possibly that you had the wrong boost version installed (did not use the provided links to download or accidentally downloaded wrong version) or that you did not restart CMake between attempting to do things like installing boost and configuring - which is mentioned in the guide. It is also possible that the system variables require a relog in windows or restarting the whole machine to take effect - this is not mentioned in the guide. Without the errors and the state of the machine it is hard to tell afterwards what your issue was. It is possible you installed wrong version of openssl accidentally. Unsure if some unconventional location may also be a reason. Most dependency errors during compile I have seen are caused by users installing wrong dependencies. For example 32 bit library when they compile 64 bit. This mostly happens for MySQL and Boost. Another problem has been the new boost and visual studio versions that required the boost finding script to be changed, but I have not checked if that was corrected already - it may have required some manual fixing. For the issues that you somehow solved it would require seeing the errors and possibly what you have installed and how you have set up the environment to figure out. This is why it is hard to imagine what could have been wrong. Even a small mistake can lead to nothing working and it could be that your system is different in some way from the majority of other systems (new versions of software etc.). So if you cannot solve the problems you should post the error messages and environment data, like what bit version you are compiling, and ask for help. In case you are getting errors there is also a troubleshooting section that has some guides for handling specific errors you may encounter: https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130044/Troubleshooting+articles In the beginning the guide encourages you to search the forums and ask for help if you cannot find what you need. - There is even a support channel you can ask help live on irc. Anyone is free to edit the wiki, which means that after figuring out what is missing from the guide you can add it in. That being said this software is probably not being built for the average joe to use. Some knowledge about the used software and programming as well as problem solving is likely expected. It should also be expected that a new user will have problems configuring a project of this size and with this many dependencies - even with a perfect guide. New issues keep rising all the time as used libraries and software is being developed by third parties as well as TC.
    2 points
  34. If you read the message carfully, you'll see that it's just a warning and no build error. Kind regards, Carbenium
    2 points
  35. WDBXEditor was created by barncastle to be compatible with every revision . Personally, it is my favorite, especially when you need to dissect from different revisions with the project that I have been working on.
    2 points
  36. Well, to start things off, here's my version of the spawn dump for everyone's favorite raid instance: naxxdump.sql
    2 points
  37. I have been following this tutorial http://www.model-changing.net/tutorials/article/107-legion-big-tutorials/ to add some new items. I have added like 2 new items but my current problem is that I can't add any stats to the item.
    2 points
  38. More: http://thehackernews.com/2017/07/gsoap-iot-device-hacking.html
    2 points
  39. Bnet server for 4.3.4 is not done or working yet but auth server is working of course and for the realmlist in the database for realm looping make sure it is set to your main IP and not localhost or 127.0.0.1 but instead the main IP. Also make sure in the wow directory you have under realmlist.wtf file the main IP address as well.
    2 points
  40. .debug bg = Toggle debug mode for battlegrounds. In debug mode GM can start battleground with single player. Or if in your case if you want to do a true 1 vs 1. You can temporarily modify world.battleground_template with min players per team to 1 for that particular battleground. https://trinitycore.atlassian.net/wiki/display/tc/battleground_template#battleground_template-MinPlayersPerTeam 1. .reload battleground_template 2. level 80+ alliance queue up for that BG. 3. level 80+ horde queue for the same BG.
    2 points
  41. @Halebawa I think I see your issue, when skimming across the images. more clearly. Your Trinity Realm in the DB needs to be set to 8085. It's at 3724. Port 3724 is your authserver. You mentioned you added a second realm, was that also at 3724? That needs to be 8086 or another port configured. Let me know.
    2 points
  42. It's crashing (closing) immediately due to a configuration issue. In Windows, use cmd.exe to navigate your worldserver.exe path and run worldserver from the terminal via command line and dont double click binary to execute. That will prevent the window from closing. Also, everything should be 127.0.0.1. and not worry about your firewall. Windows whitelists 127.0.0.1 automatically. You should use that for your realmlist.wtf and your DB settings. Once you get an exact error message from the console (without it auto closing), report back what the issue is and we can help get you set up.
    2 points
  43. " has for gossips broken maybe 7.2.0 fuckup. "
    2 points
  44. This is similar, but known: https://github.com/TrinityCore/TrinityCore/issues/19527 You have to keep in mind that 7.x is still new and the devs+community are collecting as much data as possible. Even for pre-existing npc's wil have a different menu, quest, or text than the previous version. The short answer is, don't compare 335a and master
    2 points
  45. Really? Does this look like the repack support forums? You want support or help, start here... https://trinitycore.atlassian.net/wiki/display/tc/Core+Installation
    2 points
×
×
  • Create New...