-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mod menu not showing up when loaded into mods folder 1.21.1 #768
Comments
Still not working and I have tried everything I can think of.............. |
@MarkHarrisMedia In case you haven't resolved it yet, this can apparently happen if you are using the Microsoft launcher and have an
|
i'm also having this problem, and i don't have an installations folder in my minecraft folder. i do have a versions folder, would that work? i just have no way to interact with mod options even a little bit, for any mod, and no button for mod menu. |
Can either of you provide logs? That might turn up something useful. |
This seems to happen to me when I use the installed Iris+Sodium launcher vs when I just use the fabric launcher with Iris as a .jav mod file. The log shows everything loading up with fabric, but when I use the Iris launcher a lot of stuff is missing, plus modmenu from the loading section. It might be an Iris launcher issue. Keep in mind by launcher I mean the game type you choose from the basic/main minecraft launcher menu. I assume Iris and Sodium are loading still so long as they are in the mod folder and the log shows them. |
@gomicat Those are profiles, the launcher is the app. You're correct in that the Iris installer by default creates a profile intended only to load Iris and Sodium, so in order to use other mods you need to use a profile created by the Fabric installer. |
Mod menu not showing up when loaded into mods folder 1.21.1
Some of my mods wont work because of this, such as xaeros world map or minimap that apparently rely on mod menu?
I am running vanilla 1.21.1 minecraft with fabric
The text was updated successfully, but these errors were encountered: