For the benefit of consolidating all technical support posts and questions into one place, we have created this technical support Megathread. As and when more technical queries are resolved, we will update the original post with solutions that you may try.
Please see the Epsilon Connection guide HERE.
Current Issues With Account Registration
Currently there is an issue preventing our confirmation e-mails being sent to various mail providers. If you are newly registered and have not received an email, please get in touch with the support team on Discord and be sure to take note of the username you registered with for manual activation.
1. 7.3.5 Folder Structure
Your first point of call with any technical issue is to ensure that your folder structure is correct and that you are not missing any required files. Please see below.
Avoid putting your EpsilonWoW directory on your Desktop. Use Program Files or Program Files x86.
Main Epsilon Directory
PLEASE ENSURE THAT YOUR DBFILESCLIENT FOLDER ONLY CONTAINS ITEMS.DB2 AND ITEMSPARSE.DB2 (All of these can be obtained from the starter client, Discord or from the Connection Guide) NOTE: This does not apply to the Russian or Spanish clients.
2. ERROR #132 (& #134) (0x) Fatal exception!
Ensure that drivers are up to date (This includes graphics, motherboard, and windows update. If you are unsure about what hardware you are using, download Speccy to find out: https://www.ccleaner.com/speccy/download
Ensure that Xbox DVR is disabled (This applies to Windows 10 only): https://eu.battle.net/support/en/article/92046
Temporarily disable any anti-virus (Avast is known to cause issues)
Remove all patch-related folders from main Epsilon directory such as:
Character, creature, item, world, etc.
Verify that you ONLY have the following .db2 files within your DBFilesClient folder: item.db2 and itemsparse.db2 - remove any others e.g. CHRRACES.db2, CreatureDisplayInfo.db2
You can attempt to diagnose fatal errors by checking the latest .txt files produced inside your "Errors" folder within your Epsilon directory.
3. "Connecting..." and then "You've been disconnected."
Go into your WTF folder, open your config.wtf file in a notepad editor of your choice and ensure that it says the following:
SET portal "play.epsilonwow.net"
SET textLocale "enUS"
SET audioLocale "enUS"
4. "Invalid Signature" error for Table CharSelections
Much the same as #2, this is caused by the presence of custom content in folders. Ensure that custom content is removed, and ensure that you have the correct item.db2 and itemsparse.db2 from connection guide.
5. Random Crashes, client not opening, and black screens on launch
Make sure that your EpsilonWoW folder is in a location such as C:\Games\Epsilon, Program Files or Program Files x86. Do not put it on your Desktop or in your Documents folder - especially the TinyClient.
6. TinyClient is not opening, but is showing in process list
The TinyClient does take some time to open depending on your internet speed and computer. You can verify that the process is collecting the data that it needs by opening task manager, going to processes, and ensuring that "World of Warcraft" is using CPU and Network.
7. TotalRP3 is not working
A lot of people are reporting that different versions are working. So far we've seen a 100% success rate with using version 22.214.171.124, located here
7.a Unable to Save TRP profiles/game settings
Uncheck read-only for your EpsilonWoW directory. Failing that, take ownership of your wow directory by following a guide here.
8. "kljdfkljdfkljdfkljdfkljdfkljdf" is spammed in your chatbox
You're using the 8.0.1 version of UnlimitedChatMessage. Downgrade to the 7.3.0 version. It can be downloaded here
9. "CAS system was unable to initialize"
This error is usually caused by insufficient read/write permissions. To resolve this, you first want to make sure that your Epsilon folder is in your Program Files x86 or Program Files folder. Should that not solve the issue, then you can attempt to take ownership of the EpsilonWoW folder to force these permissions. See the full guide here, or the short guide here for instructions on how to do that.
If the error contains a bunch of :404's, ensure there is no .build.info file located in your main Epsilon directory.
If you continue to get these kinds of errors, despite the above fixes, contact members of staff in the support channel in the Epsilon Discord.
10. Threading Issues
This issue is due to over-active Antivirus software blocking the Epsilon executable. Disable your antivirus temporarily prior to extracting it, then make an exception for your EpsilonWoW directory as well as the EpsilonWoW executable prior to launching it.
10.a Epsilon executable vanishes after running it
Similar to the issue above, it is caused by antivirus software. Temporarily disable your antivirus before extracting the EpsilonStarter Client, and make an exception for your Epsilon directory and executable.
Feel free to post any technical questions or resolutions below!
For further help, be sure to check out the #support channel in the Epsilon Discord.
Big thank you to @Ross, the original author of this guide.