Wrestling Empire Mod User Guide
Disclaimer
When using mods, you should be aware that it can lead to unexpected game behaviour. The
potential risks include, but are not limited to:
- Software Issues: Potential for game instability, crashes, or unanticipated behaviour.
- Save Data Concerns: Game save data could get corrupted or lost.
- Content Variations: Mods may introduce content that might be deemed
inappropriate, offensive, or divergent from the game's original intent.
- Potential Threats: There's always a risk, albeit small, of harmful software like
malware or viruses when downloading and installing mods. Note that while Steam
(and Thunderstore) conduct antivirus checks on mods, no system is entirely infallible.
Always exercise caution regardless of the source.
No accountability is taken for any issues that arise due to the use of mods. Any loss,
damage, or malfunction resulting from mod usage is the responsibility of the user.
If you encounter bugs or issues while using mods, it's important to remember that these
might be directly related to the modifications and not the base game. Before reporting any
issues, please disable all mods and verify if the problem persists in the unmodified game
and save file.
Please do not report issues with modding to the game’s developer. Either report them
directly to the developer of the mod, or in the Steam Workshop discussions section.
Installing Mods
The recommended way to install mods is through the Steam Workshop:
https://steamcommunity.com/app/1620340/workshop/
Steam Workshop mods are automatically installed after clicking the “subscribe” button
without need for any manual steps.
Making Backups
It is strongly recommended to create a backup of your save file before running any mods, as
mods could potentially cause save files to break. To create a backup, navigate to
%USERPROFILE%\AppData\LocalLow\MDickie\Wrestling Empire (e.g. using the File
Explorer address bar or the Run dialogue which can be opened by pressing Win + R), then
move the Save.bytes file to any safe location.
Please note that WECCL splits the modded save file into ModdedSave.bytes starting from
version 1.7, so it’ll be separate from the vanilla save file, Save.bytes.
WECCL also creates backups automatically. However, it’s not recommended to use these as
anything except a last resort.
Manual Installation
It is possible to install mods manually from external modding websites such as
Thunderstore:
https://thunderstore.io/c/wrestling-empire/
It is recommended to run the game once with mods enabled so that the necessary folders
for this can be created.
To install mods manually, click the “(manual) download” button on the modding website,
extract the downloaded zip file and copy the contents of “plugins” into
Wrestling Empire\BepInEx\plugins\Manual (placing them in “plugins” works too but is
discouraged). “Wrestling Empire” is the game’s root folder, which can be found by
right-clicking the game and selecting “Browse local files”.
Custom Content
For adding your own content (e.g. costumes, themes, and characters), please refer to the
“Content Mods” section of the Mod Creator Guide.
Mod Compatibility
Please keep in mind that updates might cause mods to be incompatible. If you are worried
about your save file being messed up, it may be advisable to wait a few days after an update
for WECCL to be considered stable.
Modded saves with custom content are not compatible with the base game. Also note that
removing mods while some of its content is still assigned to characters in-game may cause
issues as well.
Configuration
Some code mods may have settings that can be changed to modify its behavior. You can
edit this directly from the game’s options. Alternatively, the configuration files can be found in
Wrestling Empire\BepInEx\config, and can be edited through any text editor.
Troubleshooting
Mods don’t work at all!
First, make sure you’re running the game from the modded executable as written in
“Running Modded”. If this is the case, try reading the console log that shows up after the
game launches to see if anything is off (Alt + Tab or Alt + Enter if in fullscreen). Mods that
load correctly should say “Loading [mod name]” without any errors afterwards.
If the game recently updated, chances are that most mods haven’t been updated yet.
An error (red text) appears on screen or in the console.
Try reading the error to see if you recognize one of the following:
TypeLoadException: Could not resolve/load type (…):
This means you’re using a mod that’s incompatible with the game version you’re using.
Make sure the game and mod (mentioned above the error) are up-to-date, and if they are,
remove the mod until an update is released.
In case this happens for a Steam Workshop mod, please report it to the mod author.
IndexOutOfRangeException Index was outside the bounds of the array:
If the stack trace says “at SaveData.(...)”, this means the save data is broken. The best thing
to do if this happens is loading a backup. If not, it could mean anything. If it actually causes
problems, reporting it to the mod author is recommended.
If none of the above messages apply and the error has a visible effect, you should try
determining the mod responsible for it and reporting it to the mod author if possible.
