pa/eqemu-server
2
0
Fork 0
mirror of https://github.com/EQEmu/Server.git synced 2026-04-08 22:32:26 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated PEQ Setup using XAMPP (markdown)

JJ 2013-12-21 17:53:51 -08:00
parent 706766d99a
commit cc5050c5cb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
PEQ-Setup-using-XAMPP.md

@ -70,6 +70,6 @@ Configuring done
* **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 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 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 .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.
* **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.