Closed aft2d closed 1 month ago
This appears to be a somewhat unfortunate issue related to Connector that requires the server (and client for that matter) to be run twice to generate files.
As we can't currently upload /.connector/ processed jars to Curseforge, my best recommendation is to simply run the server script twice the first time you download.
This may be preventable by migrating to NeoForge, I’ll look into that for a future update
Hi, I'm trying to talk one of my worlds from a previous version and put it into the latest 1.20 version, and the game crashes whenever I try to open it. I even tried creating a new world altogether and the same thing happened. any recommendations?
btw im getting an error code 6 if thats helpful :)
Error codes do not help or provide any useful information. Please provide your latest.log file, or check the crash reports folder. Also send a hs_err_pid file if one generated.
Going to leave this open, please do not submit your own personal issues unless you have information related to Connector crashing on first run with new versions of Forge.
At the moment, we’re primarily blocked from switching to Neoforge by Better Combat, which only has crucial bugs fixed on its Forge 47.2.0+ versions.
It looks like Connector no longer crashes when generating files - should no longer be an issue next update!
when will the next update be available?
Describe the Bug
The server pack of Medieval MC [FORGE] - MMC4 v26 is unable to start.
Reproduction Steps
Screenshots and Videos
Log File: https://mclo.gs/oijVGEa Console Output: https://mclo.gs/qDVJndb The actual stacktrace is only visible in the console output.
Crash Report or Log
No response
Operating System
ManjaroLinux
Minecraft Version
1.20
Modloader
Forge
Modpack Version
Medieval MC [FORGE] - MMC4 v26
Optifine
No
Other Mods
No.