sc0rich

ok thanks

Oh, okay. wait, then how do I access the configurations? do you know where do I go? how I edit .cfg and .toml files? cause I just found it

is that recent? like, not even forge has a config...

debug.log I know it's not an error message. that's why I didn't type that it was an error message. If you felt like I implied it, I didn't mean to imply that. I assume that's the launcher running a part of its program as intended and I screwed up somewhere. Presumably, as far as the latest Java 8. But that's not the problem. I've had Java 8 update 281 since late January, so before I even downloaded mods for 1.16.4. Like, I've ran 1.12.2, 1.10.2 and 1.7.10 all with forge and associated mods w/o problem. It's only been within the last couple of weeks I've had problems. Like I said, the mods play fine, but I can't get into the config files. Which as mentioned above are in fact not the "Secure mod features." FWIW the launcher itself keeps warning me that "This installation has been modified and might not support the latest player features." (no shit, sherlock) I didn't care before cause those player features are chat based and I'm playing singleplayer. But again, this may not have anything to do with anything. Is there perhaps something in the logs that re-enables configs? For mods that I know have them, because I played earlier releases. edit: tried the java update method on the minecraft Gamepedia site (/Tutorials/Update_Java) - same problem as, just now it says "signiture: Unsigned. Trust: none." So obviously, what I did was the wrong way. now I need help figuring out the right way to make MC run Java 8 - 281. I can make a copy installation with default java executable to restore the file in question to a state before I messed the java update part up. crafttweaker.log latest.log

I installed forge as per normal, latest 1.16.4 (though I got this error with the recommended as well), then proceeded to download and place the mod jars in the mods folder. Then I get this: "secure mod features disabled update jdk" And I can't go into any of the mod's config settings. the only mod that I can configure is the API "Cloth Config v4 API" Now, I've seen this prompt asked about in older threads, but those in the know seem to be tight-lipped about it, insisting that this does not stop the mods from working, that I should just ignore the prompt and ultimately that this is a good thing. While, yes, I can use every mod installed in the mods folder, there are some functionalities to the mod that I'm locked out of because of this JDK thing. I know I can't recompile base minecraft for the latest Java Developer's Kit, nor is that any of our responsibilities. I just want to know it there's a workaround for letting someone get into their configs in 1.16.4 using forge 35.1.37.