MrSmite

It is included in the archive linked from the guide.

@strucker First thing, that "patch.cmd" file is actually in "wow-13287-13329-Win-final.MPQ" Second, it looks like you might have the files in the wrong folders: wow-update-13329.MPQ goes in "<wow_installation>Data" wow-13287-13329-Win-final.MPQ goes in "<wow_installation>Updates" then you run this from the root of your WoW installation:

The background downloaders from the tools updaters also work. They download 14 GB of data...

Would you please READ THE GUIDE all the way through? I specifically say what to to if the BackgroundDownloader errors: I don't understand how you're having so many problems. Every complaint you have has been explicitly addressed in the guide if you'd just take the time to read it.

@cezeta If there is a step in a flowchart that you don't meet the criteria for normally you would skip that step: So if your patch has no TFIL then you move on since you can't perform that step. As for running WoW.exe, you shouldn't be doing that after every patch. Also, when you're finished applying all the patches your WoW.exe might still not work with a "134" error. This unfortunately has many sources from bad video drivers to a corrupt patch somewhere. I've just gone through the guide a fourth time and ended up with that "134" error. It's strange that 2 out of 4 times I ended up with a working client (although the dbc / map extractors still don't work with it). This whole process is a pain in the ass and seems to be "hit and miss".

The command you posted is trying to run them from "System32" Unless you put them there (but then they won't find your MPQ files) or muck around with your envrionment variables, it won't find them. Try this version of the BAT file: REM Set directory to current directory @set base_dir=%~dp0 REM Variable base_dir should already have a backslash at the end but if you get an error REM add one between the second % and the exe name %base_dir%vmap4extractor.exe md %base_dir%md vmaps %base_dir%vmap4assembler.exe Building vmaps When you double-click to run the BAT file it should find them properly.

Thanks. Ony problem with doing that is I'll end up changing it every day for all the repack kids that don't take time to follow directions. IMO there is plenty of warning already. Yes, indeed. I simply name mine based on the expansion: wow_exp02, wow_exp03... The only catch is there is only one "WoW.exe" in the registry and the updater looks for that so it matters which one you've run last as to which path gets saved.

Once again a user gets bitten by the "full DB". Despite what people tell you or what the file says, it is not a "full db" if you use it on any other core besides the one it is meant for. You absolutely need to install all the SQL found in the ".sqlUpdates" folder, starting with the one just above the revision of the DB. You didn't give your revision (no, "latest" is not a revision) but assuming your core is newer than 2012-09-16 then you need to import any SQL that is above 2012_09_16.

@cezeta You clearly didn't read the entire guide first as I instructed. It looks like you just blundered right into it without preparing... If you have the servers blocked then what's the problem? Even if Launcher.exe did run it can't download anything. First off, the tools don't need to be updated every patch, only if a patch won't apply. Second, one of the tools is from patch wow-4.3.0.15005-to-4.3.0.15050 so it will work just fine if you use it only when a patch won't apply. How is this unclear? The guide specifically says when to copy the TFIL and run "BackgroundDownloader.exe" Common sense or not, I don't think you read the guide through before starting. If you did, your issues would've been addressed. Seeing as I've received comments from others that have had success I don't think it's an issue with the guide.

@cezeta If you have a specific problem than ask about it otherwise please refrain from cluttering the topic with unconstructive posts like "it's bad, don't use it". This, as far as I know, is the most concise guide around that actually results in a proper 4.3.4.15595. PS: Launcher.exe shouldn't be a problem because blizzard's servers should already be blocked (that's emulator 101). I only wrote that in the guide because people (probably you) were unblocking the servers and running Launcher.exe on purpose.

None of the enUS torrents have enough seeders to complete. This process isn't really that difficult anyway.

Guide is finished (unless I think of something I missed). Please add comments if you get stuck and the forums will notify me or maybe someone who got it working will answer you. Good Luck! PS: If you ran Launcher.exe and it patched you to 5.x then I can't help you. You'll need to start over and remember: 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

It's working good now but FYI: I noticed that when the error is displayed it prevents me from editing my posts using Firefox (not sure about other browsers).

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 (127.0.0.1 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-4.0.0.12911 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-4.0.6.13596-to-4.0.6.13623 wow-4.3.0.15050-to-4.3.2.15211 wow-4.3.3.15354-to-4.3.4.15595 Make sure your tools are updated by checking "Launcher.exe" (right-click -> properties), the version should be 4.2.1.2756. 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/

http://www.trinitycore.info/ Under "Help and Support", choose your OS and then scroll down to "Setting Up The Server".

Got this strange error in a banner at the top of my browser today: Browser: Firefox 16 Plugins: NoScript + AdBlock (disabled on TC)

This isn't the best method to actually get the support you're looking for but since I'm feeling charitable today, I'll give you a hint: you missed applying an SQL update so one of your tables is missing a field. PS: You posted crap in English and your support was given in English. That's probably not the worst support in the world.

So I had this issue again but this time I got a notice at the top of the screen which actually contradicted the offline page: 1. I clicked on "Help and support" and got the "this website is offline" message 2. I reloaded the site and got a banner that said "This site uses Always Online so you can browse a cached version" 3. I clicked "Help and support" and got the "website is offline, there is no cached version" So if you're being charged extra for the Always Online service it isn't working properly. Also, it seems that using NoScript also causes issues if you don't allow Cloudflare.com

You've missed an SQL update. Read the wiki on how to install the DB. Since you didn't provide your OS, I'll let you figure out which link is appropriate.

Strange, I get a 30ms delay to www.trinitycore.org in a tracert (actually to cf-173-245-61-131.cloudflare.com [173.245.61.131]) but it still takes over a minute for pages to load..

Try selecting the compilers manually: Tools > Configure Select "Specify Native Compilers" Click "Next" In both the C and C++ boxes, browse to your VS install and choose "cl.exe" from the "VCbin" folder Click "Finish" I don't know if the paths would be different for VS10 but probably not. I use VS9 so this is how I have to do it because I also have VS6 installed and CMake gets confused.

Lately I've been getting a lot of "Site unreachable" errors with a webpage that says there is no cached version and a button to "Click here to try for a live version". When I click the button, the forums load. Is this a problem with Cloudflare, the forum software or maybe something in the route from me to the forums?

Yes, indeed. Those scripts are from when Trinity was actually the same as Live. Shows you how long it's been since I've actually used the "Blizzard" one. The third script I have is for when I debug because my Config.wtf is different than when I play.

MySQL bind-address You can leave the option enabled in your my.cnf but If you bind to a specific address then you need to make sure that your TrinityCore CONF files and your authserver DB all point to that address AND you also need to make sure your MySQL user account has the proper permissions to connect using that address.

Connecting using a MySQL client is not the same as the game client. There are numerous places that you need to configure the port / IP address for the server to start properly. Post your realmlist.conf, world.conf and realmlist DB (or whatever you've called them).