Chained Echoes Support

Description

This extension adds support for Chained Echoes to Vortex Mod Manager, enabling you to easily automate installation of mods for Chained Echoes without having to worry about where the files are supposed to go, etc.

At this time, only BepInEx plugins & patchers are supported.

If you are making a different kind of mod and would like it to be supported by this extension, please leave a comment on the posts tab with a link to your mod page so that I can take a look at how you are packaging the mod and how you expect users to install it manually, so that I can then have Vortex automate this process.

How to install

This extension requires Vortex >= 1. 7. 5. To install, click the Vortex button at the top of the page to open this extension within Vortex, and then click Install.

You can also manually install it by downloading the main file and dragging it into the "drop zone" labelled Drop File(s) in the Extensions tab at the bottom right.

Afterwards, restart Vortex and you can begin installing supported Chained Echoes mods with Vortex.

How to make my mod compatible with this extension?

This extension currently makes use of the modtype-bepinex extension officially provided by Nexus Mods to install BepInEx plugins & patchers.

For compatibility, your package should not contain a BepInEx folder.

Patcher assemblies must be packaged within a patchers folder for the extension to recognise the assemblies as patchers.

Plugin assemblies may be packaged within a plugins folder, but it is not necessary - the extension will automatically assume assemblies that are not packaged within a patchers folder are plugins.

In either case, assemblies may be packaged within a subfolder named after the mod, which is useful if your mod generates or is shipped with extra files, to keep the folder tidy and prevent mods overwriting each other.

Don't forget to set your latest main file as your main Vortex file, and make sure that the Remove the 'Download with manager' button option is unticked!

Packaging Examples

BepInEx plugins

- MyBepInExPlugin.dll

- MyBepInExPlugin.dll

- My BepInEx Plugin

- MyBepInExPlugin.dll

- My BepInEx Plugin

- MyBepInExPlugin.dll

- README.txt

BepInEx patchers

- MyBepInExPatcher.dll

- My BepInEx Patcher

- MyBepInExPatcher.dll

- README.txt

BepInEx plugin/patcher combos

- MyBepInExPatcher.dll

- MyBepInExPlugin.dll

- My Mod Name

- MyBepInExPatcher.dll

- My Mod Name

- MyBepInExPlugin.dll

My mod is being installed strangely!

If you have followed the packaging examples above and your mod is still being incorrectly installed by this extension, please file a report on the bugs tab with a link to your mod page and I'll take a look and see if I can get it fixed.

Why can't I package my mod with a BepInEx folder?

At this time, the modtype-bepinex extension developed by Nexus Mods staff (which this extension utilises) expects BepInEx plugins & patchers to be packaged without a BepInEx folder. I have seen examples where plugins which are packaged within a BepInEx\plugins fo