Before proceeding, please make sure that you have your database set up properly.
worldserver.conf / authserver.conf (bnetserver.conf for 6.x) (you must remove .dist from worldserver.conf.dist / authserver.conf.dist / bnetserver.conf.dist files to obtain them)
Scroll down to the LoginDatabaseInfo, WorldDatabaseInfo, and CharacterDatabaseInfo config options and enter MySQL Server login information for the server to be able to connect to your database.
On a newly compiled config, you should have the following values:
It follows this structure:
The following settings must be verified:
- The hostname (127.0.0.1) can stay the same if Trinity is being installed on the same computer that you run WoW on.
Otherwise, follow the instruction in Realmlist Table if this is not the case.
- The port (3306) is the standard configured value. Depending on your settings, you must change it accordingly.
- The username and password can be variable. You can choose to either:
- Run on your root password you used when you installed MySQL Server Community Edition(e.g. 'root':'password'), which is strongly not recommend if the server is somehow public.
- create an unique login within a User Manager within your prefered database management tool (commonly identified by an icon that looks like a person or people) and give it necessary permissions (SELECT, INSERT, UPDATE, DELETE permissions are sufficient, and is much safer).
All other default options should be sufficient, but it is recommended that you take some time after your server is finished to read through the configs and see all the ways to customize your server.
If you choose NOT to run vmaps or mmaps, you must make the following changes:
- vmap.enableLOS = 1 – set this to 0
- vmap.enableHeight = 1 – set this to 0
- vmap.petLOS = 1 – set this to 0
- vmap.enableIndoorCheck = 1 – set this to 0
- mmap.enablePathFinding = 0 (default - keep this 0)
If you change your mind and decide to extract and use vmaps or mmaps later, make sure to change these values back to "1" to take advantage of them.
For most worldserver.conf setting changes, you can simply type .reload config in-game to see changes instantly without restarting the server.
You need to make sure that your authserver / bnetserver (6.x) application directs incoming connections to your realm.
- Run your chosen database management tool (ex. SQLYog or HeidiSQL, but also web-applications like Phpmyadmin for servers with php extension)*
- Open the auth database and find the realmlist table. You need to edit the
addressfield according to your needs:
- LAN IP (192.168.x.x) - If you are installing TrinityCore on a different computer from where you run WoW, but all the computers involved are on the same network (router) use that computer's Local Area Network IP.
- 127.0.0.1 - Also known as "localhost". Leave this setting alone here and in your configs if you've installed TrinityCore on the same computer you run WoW on, and only you are connecting to it.
External IP – If you want other people to connect to your server, use your external IP. Visit http://www.whatismyip.com/ to find your external IP address.
The TrinityCore Team and Owners DO NOT in any case sponsor nor support illegal public servers. If you use these projects to run an illegal public server and not for testing and learning it is your own personal choice.
Running and Connecting to Your Server
After completing all the steps listed above you can now start your server.
- Run the authserver (bnetserver on 6.x) and worldserver to run your server. Both must stay running for your server to accept connections to it.
- Tip: The authserver (bnetserver on 6.x) allows you to enter your username (email on 6.x)/password to connect to the Realm Selection screen, and the worldserver allows you to connect to the realm itself. Once you are in-game, the authserver (bnetserver on 6.x) can be safely closed if you wish.
- Open the realmlist.wtf file inside your World of Warcraft\Data folder. The IP in the realmlist.wtf file should be exactly the same as the IP address you entered in the realmlist table above.
- Change the first line to: set realmlist <IP address used in realmlist table>
- Example: set realmlist 127.0.0.1
- (Optional) If you wish to use the WoW Launcher.exe to run your client then you must change your set patchlist to the same ip/dns name as your realmlist.
- Get latest connection_patcher (from your build/RelWithDebInfo folder when compiling with tools) and apply wow.exe and/or wow64.exe on it by using the command console or drag&drop the exe files over the connection_patcher.
WoW_Patched.exe or Wow-64_Patched.exe have been created, use this from now on.
- Change Config.wtf: SET portal "<IP address used in realmlist table>"
The IP in the Config.wtf file should be exactly the same as the IP address you entered in the realmlist table above. (Example: SET portal "127.0.0.1")
NOTE YOU MUST RUN CONNECTION PATCHER ON EVERY CLIENT PC.
DO !NEVER! create an account directly into your database unless you are ABSOLUTELY SURE that you know what and how to do!
The "3" is the GM account level (higher numbers = more access), and the "-1" is the realm ID that stands for "all realms".
Open the world database in your database management tool and find the command table. This table shows a full list of GM commands, their descriptions, and the security (GM level) needed to use them. You will not find a more accurate list of current GM commands anywhere else (assuming you keep your database up-to-date). The security level for a given command identifies that THAT GM level can use the command, along with all GM levels above it. For example, if a command has a security of 2, all accounts with a GM level of 2, 3, and 4 will be able to use it. More detailed information can be found at GM Commands Page.
- Minimize your servers and run WoW (never run WoW using the Launcher unless you edited the realmlist.wtf's patchlist option above).
- Log in using the user/pass you just created.
- The Trinity realm should be selectable. Log in, create a character, and you're all done!
"Unable to open wmo_list.txt! Nothing extracted."
you need to run Mapextractor.exe before the makevmaps_simple.bat.
If you still have any problem, check:
If you still have any problem, check: