You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2020. It is now read-only.
I have multiple versions of Minecraft installed on my client. They all have their own Forge installed. I usually keep my mods in separate folders (mods/1.1x/ for example) so no crush happen when launching different versions of Minecraft.
But it seems that Rift does not support loading mods from sub-folder under mods, e.g. mods/1.13/. If I put my 1.13 mods directly under mods/ then my other version like 1.12 or 1.11 will crash while launching.
I like the idea that Forge allows having different versions of mods to be stored under different folders. Could you implement the same functionality with Rift please? It would be wonderful. Thank you!
The text was updated successfully, but these errors were encountered:
#65 I just created a pull request for this. Please take a look :)
This PR will let Rift try to load mods from mods/1.13-Rift/ folder first. If empty, it will then load mods directly from mods/ just like the old days.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have multiple versions of Minecraft installed on my client. They all have their own Forge installed. I usually keep my mods in separate folders (
mods/1.1x/
for example) so no crush happen when launching different versions of Minecraft.But it seems that Rift does not support loading mods from sub-folder under
mods
, e.g.mods/1.13/
. If I put my 1.13 mods directly undermods/
then my other version like 1.12 or 1.11 will crash while launching.I like the idea that Forge allows having different versions of mods to be stored under different folders. Could you implement the same functionality with Rift please? It would be wonderful. Thank you!
The text was updated successfully, but these errors were encountered: