Forgery

Forgery

823k Downloads

Unable to access server configs ingame

WenXin20 opened this issue ยท 15 comments

commented

Minecraft v1.16.5
Forge v36.0.7
Forgery v1.3.0

The mod is installed on both my server and client, but when clicking on the "server" button in the config menu, the tooltip says that the server does not have Fabrication installed. I did not have a chance yet to test with only Forgery.
Debug Log

commented

How are you accessing the config menu ingame under Forge? Did they finally add the Mods button to the pause menu?

commented

I think some mod allows it to be accessed by shift-clicking the options button, but I don't know which. There is a mod called Game Menu Mod Option that allows this as well, but I don't have that installed.

commented

Cannot reproduce after adding Game Menu Mod Option in my mini test Forge modpack.

image

commented

Strange, this is what I'm seeing.
2021-01-27_17 38 59

commented

The mixins don't show as failing to apply in the debug log, so I'm not sure what could cause this.

Is your modpack available on Curse?

commented

Not currently. I can try to get a google drive link to it.

commented

Sorry, I won't run a giant bundle of arbitrary code from an unknown source on my dev machine. I'll look more closely at the log.

commented

There are only a few mods that may have conflicting mixins, so I'll try and repro with those later today.

commented

It's a personal pack I made using the curseforge launcher. But alright then.

commented

I'm not saying you're going to send me a bundle of malware, but there's also no way for me to verify a modpack you send me as a zip is unmodified files from Curse without going through the same amount of trouble as manually reconstructing the pack from a log. Mods run unsandboxed, it is trivial to turn a mod file into malware without making it look suspicious.

commented

Oh, no worries, I understand the need for caution.

commented

Yep, that fixed it.

commented

๐ŸŽ‰

Incredible what happens when you look up documentation instead of just going "oh, it worked like this in 1.12, so surely it still works this way?"

commented

True! And thanks!

commented

Apparently Forgery was not registering commands properly. Please try this build: https://unascribed.com/f/270ff13e_forgery-1.3.0.jar

(Yes, this is related. The config screen partially piggybacks on the commands.)