From 19fb0a71353b15b4d200df0f3260b722880bd319 Mon Sep 17 00:00:00 2001 From: JJ Date: Sat, 21 Dec 2013 18:21:10 -0800 Subject: [PATCH] Updated PEQ Setup using XAMPP (markdown) --- PEQ-Setup-using-XAMPP.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/PEQ-Setup-using-XAMPP.md b/PEQ-Setup-using-XAMPP.md index 6b71cf0..e27cfb2 100644 --- a/PEQ-Setup-using-XAMPP.md +++ b/PEQ-Setup-using-XAMPP.md @@ -22,9 +22,11 @@ This guide (still in progress) was created to help you set up a basic PEQ server *** ##### The Walk-Thru -* **Get the server source.** In your XAMPP directory, create a folder to store your EQEmu files. I've selected c:\xampp\eqemu (from here on out identified as \eqemu or server folder). Within that folder (or other folder if you choose), create a source folder to store the EQEmu source code. Using TortoiseGit, clone the source files from https://github.com/EQEmu/Server.git into c:\xampp\eqemu\source\Server\. To do this, you can right-click inside your source folder and select "Git Clone...". +* **Create the initial directory structure.** You should use one base EQEmu folder. I've selected c:\xampp\eqemu (from here on out identified as eqemu or server root folder). In your eqemu folder, you should create folders called "logs", "quests", "Maps" (yes, capital "M"), "shared", and "source". -* **Get the dependencies.** In your \source\Server folder, you will find a folder named "dependencies". Inside, put in your boost, mysql_x86, and zlib_x86 folders/files. +* **Get the server source.** Within your \eqemu\source folder, use TortoiseGit to clone the source files from https://github.com/EQEmu/Server.git into \eqemu\source\Server\. To do this, you can right-click inside your source folder and select "Git Clone...". + +* **Get the dependencies.** In your \source\Server folder, you will find a folder named "dependencies". Put your boost, mysql_x86, and zlib_x86 folders inside the dependencies folder. * **Configure the source with CMake.** The first time you run CMake, you will need to specify where the source code is located and where to build the binaries. Use the "Browse Source" button to locate your \source\Server folder. Use the "Browse Build" button to create a \source\Build folder. It will ask you to identify your default compiler. If you installed VC++ correctly, it will identify Visual Studio 12 (confusing, but VC 2013 is VS12) as the default native compiler. Select "Finish" to start the intial check by CMake. It will check your compiler identification and search for existing dependencies. The output should look something like this: ``` @@ -67,18 +69,18 @@ Configuring done Now you can select "Generate" to create the build files. If there are no errors, you will get a "Generating done" message. -* **Build the source.** CMake should have created your \eqemu\source\Build folder. Inside, you can open your EQEmu.sln file to open VC 2013. Let the program initialize your project (i.e. scan includes and parse include files). When the program is "Ready", change the build from "Debug" to "RelWithDebInfo". It will continue to initialize your project. Select "Configuration Manager" and verify that the "Active solution configuration" is "RelWithDebInfo" and the "Active solution platform" is "Win32". In the "Build" column, check the "INSTALL" box and select "Close" (INSTALL will copy the executables to your \eqemu folder upon successful build). From the Build menu, select "Clean Solution" and verify 13 succeeded messages. Now select "Build Solution" and get a cup of coffee (or beer if you like). Once the build is complete, you should see 13 succeeded messages. +* **Build the source.** CMake should have created your \eqemu\source\Build folder. Inside, you can open your EQEmu.sln file to open VC 2013. Let the program initialize your project (i.e. scan includes and parse include files). When the program is "Ready", change the build from "Debug" to "RelWithDebInfo". It will continue to initialize your project. Select "Configuration Manager" and verify that the "Active solution configuration" is "RelWithDebInfo" and the "Active solution platform" is "Win32". In the "Build" column, check the "INSTALL" box and select "Close" (INSTALL will copy the executables to your eqemu root folder upon successful build). From the Build menu, select "Clean Solution" and verify 13 succeeded messages. Now select "Build Solution" and get a cup of coffee (or beer if you like). Once the build is complete, you should see 13 succeeded messages. -* **Get the database.** PEQ conducts a backup every day. The most up-to-date version can be found at http://peqtgc.com/releases. The file you need is peqbeta_(date-time).tar.gz. This database is usually synced with the most current EQEmu source. +* **Get the database.** PEQ conducts a backup every day. The most up-to-date version can be found at http://peqtgc.com/releases. The file you need is peqbeta_(date-time).tar.gz. This database is usually synced with the most current EQEmu source. Unzip these files into a temporary location of your choice. Move the [[eqtime.cfg]] file into your eqemu root folder. Open a command prompt at your temporary location (shift-right-click the folder and select "Open command window here". -* **Get the quests.** PEQ uses [Google Code] (http://code.google.com/p/projecteqquests) to store their quests. Currently, there is a mix and match of Perl and Lua quests. Using TortosieSVN, checkout the quests folder into your \eqemu\quests folder. Copy the plugins and lua_modules folders into your \eqemu folder. If you do not want to keep an SVN, you can download the daily quest dump from PEQ at http://peqtgc.com/releases. +* **Get the quests.** PEQ uses [Google Code] (http://code.google.com/p/projecteqquests) to store their quests. Currently, there is a mix and match of Perl and Lua quests. Using TortosieSVN, checkout the quests into your \eqemu\quests folder (make sure it isn't \eqemu\quests\quests). Copy the plugins and lua_modules folders into your eqemu root folder. If you do not want to keep an SVN, you can download the daily quest dump from PEQ at http://peqtgc.com/releases. -* **Get the maps.** Your server will use the map files from EQ for in-game calculations. Currently, maps are stored at [Google Code] (http://code.google.com/p/eqemumaps). Using TortoiseSVN, checkout the maps folder to your \eqemu\Maps folder (yes, capital "M"). +* **Get the maps.** Your server will use the map files from EQ for in-game calculations. Currently, maps are stored at [Google Code] (http://code.google.com/p/eqemumaps). Using TortoiseSVN, checkout the maps into your \eqemu\Maps folder. -* **Get the database editor.** PEQ uses [Google Code] (http://code.google.com/p/peqphpeditor/) to store the PEQ Database Editor. Using TortoiseSVN, checkout the editor into your xampp\htdocs\peqedit folder (or whatever you wish to call it). +* **Get the database editor.** PEQ uses [Google Code] (http://code.google.com/p/peqphpeditor/) to store the PEQ Database Editor. Using TortoiseSVN, checkout the editor into your \xampp\htdocs\peqedit folder (or whatever you wish to call it). -* **Move the .conf files.** In your source, you need to copy/move the .conf files to your \eqemu root folder. They are located at \source\Server\utils\patches. These files contain specific OPCODES your server needs to communicate with the clients. +* **Move the .conf files.** In your source, you need to copy/move the .conf files to your eqemu root folder. They are located at \source\Server\utils\patches. These files contain specific OPCODES your server needs to communicate with the clients. -* **Configure the server settings.** You will need to have the [[eqemu_config.xml]] file in your \eqemu root folder. Also, you can edit your server variables using the database editor. +* **Configure the server settings.** You will need to have the [[eqemu_config.xml]] file in your eqemu root folder. Also, you can edit your server variables using the database editor. * **Take it for a test run.** It is a good idea to run each command one at a time the first time you launch your server to ensure you don't have any errors. Once you are sure everything works correctly, you can use [[start.bat]] to automate your server startup.