hackersrage

Fair enough. I know this might be a bit much to ask, but is there a way to apply the patch (similar to the old patching system) where the modification kept the hash of the file the same ? Way back around the era of WAD's wowemu which started this whole thing,the wow executable needed to be patched as well, however the file signature remained in tact. Later on a few years into development, connection to certain emu servers no longer required any client side patching. I thought this was due to blizz finally allowing emu's unofficially by respecting alternate server addresses placed inside realmlist.wtf . It would first try blizz official, then failing that use the one in the realmlist.wtf file. Prior to that (in client patch required days with wowemu and such), any attempt to connect to an alternative server would result in wow overwriting the realmlist.wtf with the 'official' server. What is the current problem in the exe that prevents this ? Does it no longer roll-over to respect the specified server ? I did notice that if I attempt to use the wow.exe unmolested, i get an expediant disconnect which is slightly different than a failed credential check with blizz, so it appears that it does still respect the wtf file (new location WTF/Config.wtf). Thanks in advance :)

Had the same problem in all browsers. The issue has been corrected.

Page is now at http://www.trinitycore.info . It is back online now.

@Polaretto If you check the worldserver.conf file, you will see a couple of settings for automatically applying database patches. The steps are quite simple (even for those not compiling their own build, which I recommend they do since there is no official pre-compiled versions available) . * Download TrinityCore source (git pull { preferred method } / zip archive / whichever ... ) * Edit the worldserver.conf, and if you didn't compile your own, set the parameter for source folder to where TrinityCore source tree is. * Enable automatic database updates * Download (currently 6.02 from July 2015) latest build of the TDB * Import the auth and characters sql files into their respective databases from TrinityCore/sql/base * Import hotfixes and world from TDB sql files into their respective databases (inside the TDB download, not the TrinityCore source) * Start ./worldserver . Now as long as the settings / etc are all correct in worldserver, it will automatically merge new updates from that date forward from the sql patch files in the TrinityCore source that you downloaded in the first step. What I would suggest, is perhaps to include TDB in the sql path as part of the TrinityCore source tree. That would make things a bit easier than trying to load from different places, however there may be a logical reason for why the two projects remain segregated from each other. ################################################################################################### # UPDATE SETTINGS # # Updates.EnableDatabases # Description: A mask that describes which databases shall be updated. # # Following flags are available # DATABASE_LOGIN = 1, // Auth database # DATABASE_CHARACTER = 2, // Character database # DATABASE_WORLD = 4, // World database # DATABASE_HOTFIX = 8, // Hotfixes database # # Default: 0 - (All Disabled) # 4 - (Enable world only) # 15 - (All enabled) Updates.EnableDatabases = 15 # # Updates.SourcePath # Description: The path to your TrinityCore source directory. # If the path is left empty, built-in CMAKE_SOURCE_DIR is used. # Example: "../TrinityCore" # Default: "" Updates.SourcePath = "" # # Updates.MySqlCLIPath # Description: The path to your mysql cli binary. # If the path is left empty, built-in path from cmake is used. # Example: "C:/Program Files/MySQL/MySQL Server 5.6/bin/mysql.exe" # "mysql.exe" # "/usr/bin/mysql" # Default: "" Updates.MySqlCLIPath = "" # # Updates.AutoSetup # Description: Auto populate empty databases. # Default: 1 - (Enabled) # 0 - (Disabled) Updates.AutoSetup = 1 # # Updates.Redundancy # Description: Perform data redundancy checks through hashing # to detect changes on sql updates and reapply it. # Default: 1 - (Enabled) # 0 - (Disabled) Updates.Redundancy = 1

Sounds good brother. If you guys need an extra on the crew that's been in the scene for a while (since WAD), let me know. Currently, just working to figure where to even begin to start patching up this mess. Also, could you please let me know why this has gone the direction of patching the exe again, as if memory serves, that stopped being necessary some time ago. The patching (as usual) works great. I recall there being something about blizz allowing emu's and adding support for them by not changing the server in the wtf file (used to be realmlist.wtf, now WTF/Config.wtf ), and honoring whatever that setting was. Thanks again --- and also nice to see this project continues even though MangOS aborted.

Over the years, I noticed that Cloudflare is one of those things that either works really well -- or causes lots of headaches. Unfortunately for your forums, Cloudflare is being a real <expletive word here> and I recommend disabling it completely. The forum and community currently are both small enough it really wouldn't benefit much from the so-called caching which they provide. ISSUE #1 Following image depicts the error I am getting whenever I try to post a reply, or a new topic. http://i.imgur.com/a5N9E2r.png Additionally, it makes it appear like I am spamming the forum with multiple responses when I have only clicked submit/reply/etc ONCE. ISSUE #2 There is another issue as well with the documentation portal that has been giving a 502 bad gateway response for several days now. http://i.imgur.com/Hm8VDtx.png is what everyone is getting right now when attempting to go to http://collab.kpsn.org/display/tc/Databases+Installation ISSUE #3 Links seem to work on this site without any real problem, taking me where they appear they should be taking me -- except for pagination. When clicking on a different page # in threads having multiple pages. The page does not change. However if I right click the page #, and open in a new tab, the page displays. This could also be linked to Cloudflare as the source of this problem as I am sure your forums are working correctly. ISSUE #4 Certain Ajax commands will spin forever, such as the Create dropdown at the top. While the drop-down action works, clicking either Topic or File Download result in a process that does not terminate or give the expected result such as opening the new Topic window/page never happens. I would also blame Cloudflare for this. Cloudflare DNS is an utter pile of trash, and they always blame the website using their service as being 'down' when in fact it is their <expletive> service that is buggering everything up. It is also slower. In my tests the TTFB with Cloudflare hosted stuff was around 200 times higher than without using their DNS. I was able to trace this to major DNS issues on their end which result in the typical 'community.trinitycore.org' is down messages, when in fact your server is NOT down. (kpsn.org is, but this site is up).