Converts the EverQuest assets from the original game into World of Warcraft 3.3.5

To see video references, go here: YouTube Playlist

Note: The creator of this converter (Nathan) has no affiliation with any server provider/hoster, and provides no client files for either EverQuest or World of Warcraft. This project is for education and preservation purposes only.

It is currently in an Alpha state, but all content types (tradeskills, spells, quests, etc) are working to some degree. Classic, Kunark, and Velious are all enabled and playable by default. Non-spell particles (weapon and environment particles) are still TBD, and many things need balancing and bug fixing.

• Windows build environment
• AzerothCore based WoW 3.3.5 server (last through this changeset: https://github.com/azerothcore/azerothcore-wotlk/commit/cfeb6d85517aba1492d7ddacdfc73b9fa770b4af)
• Install the "mod-everquest" mod into AzerothCore (https://github.com/NathanHandley/mod-everquest)
• Installed unpatched client of the EverQuest Trilogy
• Installed 3.3.5a WoW client, US version (which must be patched to not check for MD5 signatures, similar to other modded projects)
• If you want armor textures, install a texture pack. One can be found here: https://github.com/NathanHandley/EQWOWConverter-HumTexturePack

1. Build and run the application once in order to generate a configuration.txt file.
2. Open the configuration.txt file and set the desired values in sections 1, 2, and 3 (near the top)
3. (Optional) Install a texture pack, such as one here: https://github.com/NathanHandley/EQWOWConverter-HumTexturePack
4. Build and use EQWOWConverter and run the command "Perform Everything"
5. (Optional) Deploy your files manually if you did not set up automatic deployment in the configuration
6. Regenerate map/vmap files for the server per AzerothCore instructions

Note: If you have a working install, you typically only need to select option 6 to keep up to date on future builds

Automatic Deployment Highly Recommended:

1. Set the configuration.txt deployment settings in "2. Deployment Settings"
2. Build and let it deploy for you next time you run it

Manual Deployment (Alternate):

1. Run the .sql files located in <PATH_WORKING_FOLDER>/WOWExports/SQLScripts against your databases, with /Characters/ against your characters database and /World/ against your world database
2. Copy contents of <PATH_WORKING_FOLDER>/WOWExports/DBCFilesServer into your server's dbc files location (typically located in the "data" folder during AzerothCore setup)
3. Place the (*.mpq) patch file inside <PATH_WORKING_FOLDER>/WOWExports into the (<PATH_WORLDOFWARCRAFT_CLIENT_INSTALL_FOLDER>/Data/) and (<PATH_WORLDOFWARCRAFT_CLIENT_INSTALL_FOLDER>/Data/enUS/) folders. (note that enUS may be different depending on your locale)
4. Copy the AddOn from your <PATH_WORKING_FOLDER>/AddOnsReady into the (<PATH_WORLDOFWARCRAFT_CLIENT_INSTALL_FOLDER>/Interface/AddOns/) folder.

In no particular order...

• Dan Wilkins/Nick Gal/(others) for Lantern Extractor (https://github.com/LanternEQ/LanternExtractor) - This saved a lot of time trying to get EQ data exported
• Also the community behind Lantern Extractor on their Discord. Special callouts to Kicnlag, Silvae, Wiz, and Eldrich.
• The people behind https://wowdev.wiki - Navigating the WoW file formats would have been near impossible without this documentation
• WoW Modding Community Discord - For the one-off problem questions I've run into thus far (special callout to Aleist3r, Titi, Soup Aura, Stoneharry)
• Jarl Gullberg and team working on libwarcraft (https://github.com/WowDevTools/libwarcraft) - Whenever confused by elements outlined in wowdev.wiki, this code worked as a reference sanity check