0 of 0
About this mod
Plugin that provides advanced inZOI support for Mod Organizer 2
- Requirements
- Permissions and credits
- Changelogs
Installing the Plugin
- Download and install Mod Organizer 2 (MO2) from the GitHub repository
- Place the file inzoi.py into {MO2 install dir}/plugins/basic_games/games/
- Launch MO2 after installing the plugin
- Create a global instance for inZOI and select a dedicated directory for storing your mod downloads and installations
- You will want to ensure the mod you're installing has the correct directory structure. For example, most mods should be mapped as follows: BlueClient/<ModContent>
- 3DPrinter mods must be mapped as follows: My3DPrinter/<ModContent>
- AIMotion mods must be mapped as follows: MyAIMotions/<ModContent>
- If you need to adjust a mod's directory structure you can right-click the <inzoi> directory, select "Create Directory", name it as required for the mod type, then move the mod files into the new folder
- The plugin provides some automatic handling/packaging for .pak, .ucas and .utoc mods and some mods within sub-directories, so you may not need to re-package all mods.
- Compatible with 3DPrinter, AIMotion and MySites mods VIA two methods. Symlink creation when the mod is enabled, or symlink creation on game launch. (The default method is symlink creation on launch.)
- 3DPrinter/AIMotion/MySites symlinks on Launch: (This method is slightly cleaner as the symlinks are removed when you close the game but your 3DPrinter mods will be inaccessible without launching inZOI VIA MO2)
- 3DPrinter/AIMotion/MySites symlinks on Enable: (You can enable this setting in MO2 > Plugin Settings > inZOI Support Plugin > set Deploy Symlinks on launch to false. With this setting changed 3DPrinter, AIMotion and MySites mods will get symlinked when they're enabled. Deploying them from the mod data directory to the appropriate folder in %USERPROFILE%/Documents/inZOI this means even if you run inZOI without MO2 your 3DPrinter/AIMotion/MySites mods will be accessible. Symlinks are removed ONLY after disabling the 3DPrinter mod) - Automatic handling for some incorrectly packaged 3DPrinter mods and renames the mod folder to match the .GLB file's MD5 hash if it does not already.
- Automatic handling for some incorrectly packaged AIMotion mods
- Automatic handling for some incorrectly packaged MySites mods
- Automatic handling for some incorrectly packaged .pak, .ucas and .utoc mods. They will get structured to live in: {inZOI game dir}/BlueClient/Content/Paks/~mods/
- Second level sub-directory handling for some incorrectly packaged mods.
- MO2 will let you know if the mod is incorrectly packaged even after install, so you can do something about it.
- Automatic cleanup of the following files in the root of a mod directory: *.txt, *.md, README, icon.png, license, LICENCE, manifest.json, *.dll.mdb, *.pdb. None of these files should be required and will be purged to save you space.
- Ensures UE4SS dwmapi.dll is correctly placed in {inZOI game dir}/BlueClient/Binaries/Win64
- Automatic configuration of force load library settings, ensuring dwmapi.dll is injected into inZOI-Win64-Shipping.exe
- Symlink handling for dsound.dll and bitfix folder of inZOI Mod Enabler. (The dsound.dll cannot be injected VIA force load library settings, so this was a necessary solution.)