Frequently-Asked Questions

1. Where do I go to create my OpenDAoC player account?

To create a game account follow the instructions here: How to register

2. I've forgotten my account name and/or password. What do I do?**

If you have linked your game account to Discord, just access the Account Manager and change your password from there.

If you haven't already, don't panic! We can help you with that. Create an account on Discord and join our server.

After that, you should see all online/available team members at the top-right corner of the Discord app. Simply message one of us directly with your issue and we will help get access to your account.

Please note that you will be expected to know and provide some information regarding your account, such as account name (if you haven't forgotten it) and the names/levels of some characters associated with the account.

3. Can I play OpenDAoC on Linux/Ubuntu/Mac operating systems (OS)?

Sure! For Linux/Ubuntu, you can use Wine or CrossOver as compatibility layers to simulate a Windows environment and run DAoC. Or, if you're using MacOS, you can use CrossOver. Simply download and patch DAoC and then do the same with our installer.

4. Can I use the same instance of DAoC for another freeshard than OpenDAoC?

While it may be possible, we do not recommend using the same DAoC directory for multiple freeshards, or the DAoC Live server. We recommend having an individual folder dedicated to each freeshard/server, as there may be conflicting file sets and overwrite some files.

5. I'm getting strange exceptions/errors when I run OpenDAoCLauncher.exe. What is going on?

The most common reason for exceptions to occur is that you aren't running the executable as an administrator. Right-click on the Launcher app and then select Run as Administrator.

6. Why do I need to launch OpenDAoCLauncher.exe as an Administrator? Pretty sus.

This is triggered as a result of DAoC being installed in a protected path, like Program Files. To get around this issue, you can move your DAoC folder to a secondary partition/disk/directory, whereupon you no longer need to run the launcher as an Admin. Otherwise, you must run OpenDAoCLauncher.exe as an administrator (right-click on the .exe and select Run as Administrator.


If you encounter issues that prevent you from accessing the OpenDAoC server, please go through the following questions/scenarios. It may be one or a combination of factors preventing access to OpenDAoC, so please review the following questions. Before you request assistance from the team on Discord or post on our forums, answer these questions by yourself, or be prepared to answer these questions when you solicit help.

1. What is your operating system (OS)?

We typically assume players are using Windows, but if you're a diehard Linux/Ubuntu or MacOS advocate, you can use compatibility software like Wine/CrossOver. If you're using Linux/MacOS, then we know that these sometimes cause issues with running the OpenDAoCLauncher.exe application. You may need to install some additional common language/development tools like .NET Framework 3.5 and 4.8. If you still encounter errors when running the OpenDAoC Launcher, you can circumvent this by using DOL Portal in place of OpenDAoCLauncher.exe.

IMPORTANT: Make sure your antivirus (AV) is off--both third-party and anything built-in with your OS--as these oftentimes believe there's a virus in the files. Otherwise, you should add our files as exceptions to both the AV and Firewall, which is described further in a section below.*

2. Is this your first/only installation of DAoC on this computer?

If you're getting things running for the first time with DAoC, you'll want to make sure you have .NET Framework 3.5 installed. This is a general requirement, as this will otherwise prevent the game from launching at all.

3. Do these necessary OpenDAoC files exist in your DAoC directory?

The following files must be present to confirm OpenDAoC is patched, your antivirus isn't deleting files, and you've installed OpenDAoC to the correct folder:

  • OpenDAoCLauncher.exe
  • connect.exe
  • game1127.dll

If any of these are missing, then you should check to make sure OpenDAoC is fully installed/patched in your DAoC directory and that your AV (third-party or OS built-in) has not quarantined/deleted/blocked the files.

4. Are you running OpenDAoCLauncher.exe as an administrator?

If you are not running the OpenDAoC Launcher with sudo or administrator privileges enforced, then this may prevent the launcher from loading fully. With Windows, you need only right-click on the OpenDAoCLauncher.exe executable and then select Run as Administrator.

5. If you also play on another DAoC freeshard, are you using separate installations of DAoC?

If you play on multiple DAoC freeshards, you should avoid one instance of DAoC. You cannot access multiple servers from the same DAoC directory as most every freeshard replaces core client-side data with their own unique file sets, which may conflict strongly between freeshards or even the DAoC Live server. With freeshards in general, it is a recommended practice to always keep separate installations of the game for each server you access.

6. If you were using a third-party AV and uninstalled/disabled it before installing OpenDAoC, did you also disable/turn off your OS's built-in AV?

There's a chance that your operating system's built-in antivirus (AV) or firewall intercepted/quarantined/blocked Atlas-specific files. Check your Windows/Ubuntu/MacOS AV and Firewall to make sure these are offline. Or, you may add certain files as exceptions to your AV/firewall (see the next question below).

7. Have you added key OpenDAoC files as exceptions to your AV and Firewall?

Whether you're using a third-party antivirus/firewall app or tools built into your operating system, we recommend that you add the following files as exceptions:

  • OpenDAoCLauncher.exe
  • camelot.exe
  • game1127.dll

Adding game1127.dll specifically is a highly-recommended practice, as this also has the effect of drastically reducing load screen times when traveling between regions in DAoC.