Notice something wrong, missing, or inadequate? Feel free to edit pages yourself and make use of discussion pages.
Wiki content is created, maintained, and administrated by players. Learn how you can help!

Difference between revisions of "Installation Guide (Steam)"

From SoDWiki
Jump to navigationJump to search
Line 32: Line 32:
 
#if you have errors try updating your .Net Framework and DirectX
 
#if you have errors try updating your .Net Framework and DirectX
 
{{bug| there is a known memory leak bug in the client that can cause a crash(usually while logging in or zoning) when memory usage of the client exceeds 1.8GB this can be mitigated by always using a fresh instance of the client when swapping toons. if it becomes a significant issue can try asking in discord for the third party patch which increases the memory limit before a crash. This problem cannot be solved by the team here in an official patch because it requires modification of a binary they don't have the rights to edit to fix}}
 
{{bug| there is a known memory leak bug in the client that can cause a crash(usually while logging in or zoning) when memory usage of the client exceeds 1.8GB this can be mitigated by always using a fresh instance of the client when swapping toons. if it becomes a significant issue can try asking in discord for the third party patch which increases the memory limit before a crash. This problem cannot be solved by the team here in an official patch because it requires modification of a binary they don't have the rights to edit to fix}}
{{bug| another bug is when logging in sometimes it will seem like it is taking forever to login. if the "Log In" button doesn't look pressed in hit the enter key which will clear the dialog and click the login button with your mouse}}
+
{{bug| another bug is when logging in sometimes it will seem like it is taking forever to login. if the "Log In" button doesn't look pressed in. hit the enter key which will clear the dialog and click the login button with your mouse}}

Revision as of 09:32, 8 August 2021

Shards of Dalaya is the longest continuously running emulated EverQuest server, featuring completely reimagined lore and a number of custom mechanics not present in the parent game. To make a character of your own and set foot on your adventure, follow the steps outlined below.

Community Discord

If you have any questions after reading this starting guide, or just want to hang out, be sure to join us on Shards of Dalaya's official Discord server .

Install the Game via Steam (Windows)

Note: Players familiar with Steam may choose to stray from the steps outlined below. Do so only if you are confident in your technical abilities.

To install EverQuest using Steam, do the following:

  1. Visit the official Steam website:
  2. Create a Steam account if you don't already have one by clicking on login and then Join Steam. (Steam accounts are free.)
    Steam Guide 1.png

    Steam Guide 2.png

  3. After creating an account, download the Steam installer from the website by clicking on the green Install Steam button.
    Steam Guide 3.png

  4. Open the Steam installer to install Steam.
  5. Open Steam and log in to your Steam account.
    Note: Use the account name and password you created in Step 2.
  6. Type EverQuest into the search bar.
    Steam Guide 4.png

  7. Click on the EverQuest game (dated Dec 13, 2012) and click on the green Play Game button to add the game to library.
    Steam Guide 5.png

    Steam Guide 6.png

  8. Click on the Library tab at the top.
    Steam Guide 7.png

  9. Double click on EverQuest Free-to-Play in your library list and download the game.
    Note: There is no need to run/patch EverQuest once Steam finishes installing the game. This will cause errors when trying to run SoD!
  10. When the game has finished downloading, right-click EverQuest Free-to-Play in the library list and select Properties.
    Steam Guide 8.png

  11. Under the Local Files tab, click on Browse Local Files.
    Note: This will open the folder that EverQuest has been installed to.

    Steam Guide 9.png

  12. Click the "Up" arrow to the left of the file address bar.
    Steam Guide 10.png

    Note: This allows you to view the EverQuest F2P folder.
  13. Right-click on the EverQuest F2P folder and select Copy (recommended) or Cut (if your hard drive is low on storage space).
  14. Navigate to wherever you want to place the folder, such as C: > Program Files (x86), and Paste (CTRL + V) the folder there.
Note: Suggest not putting it in a Windows created directory as suggested above to avoid potential file permission issues(this is an old game and windows has gotten more strict over the years, will likely be fine but it reduces the number of things to check if an error happens) and please don't place in your user folder if you have any errors that need to be resolved your installation directory will likely be included in the information required to solve the problem revealing your windows user name. The desktop is in your user folder
  1. Open the Shards of Dalaya patcher (SoD 2.5 Patcher.exe).
    Note: If you do not already have the SoD patcher, it can be downloaded here. The patcher may be placed on the desktop for easy access.
  2. Within the patcher, check the Repatch All box, then click on the Browse... button to direct the patcher at your newly installed, newly moved EverQuest F2P folder.
    Note: Refer to Step 14 as needed; the patcher must be directed to the location you chose for your EverQuest F2P folder.

    Steam Guide 11.png

  3. Click Patch and Run to update to Shards of Dalaya's files.
  4. After patching, enter the game!
    Note: If you haven't already created your Shards of Dalaya account(s), do so here.
  5. if you have errors try updating your .Net Framework and DirectX
Bug Bug!
there is a known memory leak bug in the client that can cause a crash(usually while logging in or zoning) when memory usage of the client exceeds 1.8GB this can be mitigated by always using a fresh instance of the client when swapping toons. if it becomes a significant issue can try asking in discord for the third party patch which increases the memory limit before a crash. This problem cannot be solved by the team here in an official patch because it requires modification of a binary they don't have the rights to edit to fix


Bug Bug!
another bug is when logging in sometimes it will seem like it is taking forever to login. if the "Log In" button doesn't look pressed in. hit the enter key which will clear the dialog and click the login button with your mouse