OvGME shares some concepts with JSGME, but be careful !
How OvGME cohabit with JSGME ?
Bad ! so to say, the prudent answer is that OvGME does not cohabit at all with JSGME.
OvGME uses its own logic, its own configuration files with its own backup format, and
don't care about JSGME.
Do i risk to corrupt the JSGME configuration using OvGME ?
No, but in fact Yes ! OvGME does not interfere with JSGME configuration and backup
structures, and JSGME does not interfere with OvGME, both software act independently
HOWEVER:
This imply that OvGME ignores what JSGME does, and vice versa. For example, if you
enable a mod using OvGME, JSGME will not see it as enabled (and vice versa). This
situation can creates many confusion in backup since JSGME can create backup of files
modified by OvGME without knowing it (and vice versa) and then finally you can loose
the original files.
The safe rules are:
- A mod already enabled with JSGME must not be enabled again using OvGME.
- A mod already enabled with OvGME must not be enabled again using JSGME.
- A mod enabled with OvGME must be disabled using OvGME.
- A mod enabled with JSGME must be disabled using JSGME.
The true safe rule is:
- Don't use both JSGME and OvGME for the same root folder (game or software).
How do i switch from JSGME to OvGME and vice versa for a root folder (game or software) ?
If you choose to use OvGME for a root folder where you already use JSGME:
- Launch your JSGME instance for this root folder.
- In JSGME, Disable ALL mods.
- You can now quit JSGME.
- In OvGME, Add a Config and specify the proper mods folder, the one previously used by JSGME for example.
- You can now delete the "!BACKUP" and "!INSTLOGS" hidden folders in mods folder.
- You also can now delete the "JSGME.ini" files in root folder and mods folder.
If you choose to use JSGME for a game where you already use OvGME:
- Launch OvGME and select the proper configuration.
- In OvGME, Disable ALL mods.
- In OvGME, Remove the configuration.
- You can now quit OvGME and install JSGME safely.