-
-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Tip
All file paths mentioned in this FAQ are relative to your game folder, i.e. BepInEx/LogOutput.log = [game folder]/BepInEx/LogOutput.log, where [game folder] is the path to the folder containing the game's executable (e.g. Chained Echoes.exe).
Steam users can find this folder by right-clicking the game in their Steam library and selecting Manage -> Browse local files.
BepInEx is a general purpose framework for Unity modding. This is a BepInEx pack for Chained Echoes, preconfigured and ready to use.
Important
At present, Steam users must switch to the kickstarteralphabacker beta branch to use this BepInEx pack!
Aside from the console window opening up on Windows and some Linux systems, this pack doesn't make any noticeable changes in-game by itself. This pack simply loads BepInEx plugins and patchers, and it is up to them to make changes to your game!
So, if you haven't yet actually installed any mods, BepInEx is probably working fine. Especially if you see the console window opening up, otherwise you can verify this by checking the LogOutput.log file which should have been generated in your BepInEx folder.
If BepInEx itself seems to be working, but you have installed mods which aren't working, see the below sections:
First things first, make sure you actually installed the mods to the right place. Refer to the Installing mods section of the README for details.
If none of your mods are working, first try restarting your computer. Genuinely, sometimes things just go wonky with computers and a reboot will fix it.
Otherwise, refer to the below section: Some of my BepInEx plugins aren't working!
Issues with BepInEx plugins are usually going to be either an installation issue caused by a mod manager, some manager of PEBCAK issue, or a bug with the plugin itself.
This BepInEx pack includes Tobeys Plugin Doctor for BepInEx 5, a utility to help with troubleshooting common problems with BepInEx plugins.
If simply prints a report of all found issues in the logs for you to read over, advising you on how to handle them.
To access the report, simply load the file BepInEx/LogOutput.log in the text-editor of your choice, and search for PLUGIN DOCTOR REPORT (with Ctrl+F where available).
If the report advises you to consult with the developer of a plugin, you should go to wherever you downloaded that plugin from and find a means to contact them there, e.g. the posts or bugs tab on Nexus Mods, the issues or discussions page on GitHub, et cetera. Failing that you can reach out to the wider modding community (see below).
If the report advises you to consult with the modding community, at this time there is not a well-known discord server for me to recomend. In the meantime, you can make use of the posts tab of this pack on Nexus Mods, or the disvussions section of this pack's GitHub repository.
Tough luck. I won't be helping you with that. If you have problems running mods on a pirated copy of a game, 99% of the time it's the pirated copy that's the problem, not the mods.
Mods operate under the assumption that the game is in a specific state, has specific code which does specific things that they can rely on. If these assumptions are proven false, then their mod is not going to be able to function correctly.
Pirated copies of games frequently break these assumptions, and therefore frequently break mods. If you're getting bugs when running a pirated copy of a game, the most likely solution is to run a legitimate copy of the game. No developer is going to want to help you until you try that first, because otherwise you're just wasting their time.
Feel free to post a comment on the posts tab of this pack on Nexus Mods describing your issue, and I'll try to help you out. But be forewarned: if you're just going to ask a question which could have been answered by reading the instructions or this FAQ, there's a good chance you'll get a snarky response.