Jump to content
TrinityCore

Leaderboard


Popular Content

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

  1. 9 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
  2. 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.)
  3. 6 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
  4. 4 points
  5. 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
  6. 3 points
    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!
  7. 3 points
    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
  8. 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)
  9. 2 points
    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
  10. 2 points
    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
  11. 2 points
    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.
  12. 2 points
    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.
  13. 2 points
    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.
  14. 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.
  15. 2 points
    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
  16. 2 points
    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.
  17. 2 points
    If you read the message carfully, you'll see that it's just a warning and no build error. Kind regards, Carbenium
  18. 2 points
    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.
  19. 2 points
    Well, to start things off, here's my version of the spawn dump for everyone's favorite raid instance: naxxdump.sql
  20. 2 points
    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.
  21. 2 points
    More: http://thehackernews.com/2017/07/gsoap-iot-device-hacking.html
  22. 2 points
    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.
  23. 2 points
    .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.
  24. 2 points
    @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.
  25. 2 points
    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.
  26. 2 points
    " has for gossips broken maybe 7.2.0 fuckup. "
  27. 2 points
    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
  28. 2 points
  29. 2 points
    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
  30. 2 points
    authservers are compatible (up to wod, old auth code removed from client) if you just add the neccessary build info https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/authserver/Authentication/AuthCodes.cpp
  31. 2 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!
  32. 2 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.
  33. 1 point
    For most exploits, that you are likely to encounter, people have some knowledge of and they are likely created as issues for them. So back in the day when you had a repack, you could have made an issue for that specific version and then made an issue/defect to that effect. Examples: https://github.com/TrinityCore/TrinityCore/issues?utf8=✓&q=label%3ASub-Exploit
  34. 1 point
    Links to a thread that links to a site that charges money
  35. 1 point
    @asio2890 what are your .conf settings? [hide your password] Your database looks fine, assuming your are on 3.3.5a. (you could also try setting your ip address rather than 127.0.0.1). But your worldserver.conf settings may be the issue.
  36. 1 point
    We can always add them and submit a PR Not sure how many items that may need to be excluded.
  37. 1 point
    run nload while all 9 players are playing and tell me if Incoming or Outgoing is spiking. This is a test on my server with 8 people playing who volunteered Your outgoing should be less Avg: 27.46 kBit/s Your Incoming should be less Avg: 12.59 kBit/s Does this happen when only you play by yourself? If you are getting spikes only with other players, then there is other activity going on. Possible that one of the players is DDOS'ing your network?
  38. 1 point
    Are the profile Locations supposed to be truncated together? For example: I deliberately placed a colon : and a space so the location is not truncated.
  39. 1 point
    Do you know how many problems this makes when you are setting up more than one server and using one database for all that is not only asking for problems but makes my head hurt even thinking about it. lol
  40. 1 point
    Hi, I do not understand much english, I do not know if I understand correctly what you want. Do you need to manually set the boost path in cmake? In that case, you must have the "advanced" box active, it's up, beside the add button
  41. 1 point
    Just follow the wiki step by step sticking to the version you want, and in any case, do not mix both versions. (Start over all the times you need, eventually you'll learn to do it easily without the wiki)
  42. 1 point
    I'm having the same issue.
  43. 1 point
    You can close or delete this I got the server working thanks so much for everybody's help
  44. 1 point
    Did you try clicking repair and fixing that exact item? Try going to your windows control pane -> programs and features -> click git extensions and see if there is an add button. don't uninstall it, just see about an option to add the basic linux commands to your windows. The (sh) error is the shell script. It may be installed, just that git extensions can't find it. Personally I recommend going full Linux, then you wont have that issue
  45. 1 point
    if you compile on release mode you don't have those files.
  46. 1 point
    Yes, but you still need to add your second realm to the authserver.conf so it'll know it's available. Fill it in just like you did for the first one, only this time use the info for your second realm.
  47. 1 point
    Hello all, I'm currently attempting to install 3.3.5a server. Everything is peachy so far, however I have ran into a snag, my authserver.exe seem to refuse to run and I'm not sure what issue is because I've ran it though debug several times and I don't really see any crashing issues. Just bunch of stuff missing custom NPCs and whatnot missing, I don't think those would be causing the issue. So do any of you have any idea why this might be happening (oh and all of my ports are open) also.. My worldserver seem to be running perfectly fine. Just authserver is having a bitch fit. I'm new to these forums sorry if I posted it in wrong place. Edit: Did more tinkering, like reuploading trinityauth table and running it though debug again (for umpteenth time) still no luck. I would provide screenshots but there is literally no errors.
  48. 1 point
    you cannot use 7.1.5 extractor on 3.3.5a client.
  49. 1 point
    Wouldn't hurt. Nuke and pave.
  50. 1 point
    You should not change db2 files, otherwise your kernel will simply not run. If core not have this hotfixes support, need implement in core and you can change in hotfixes databases.
×