I was trying to make my own modpack called Spicedcraft but something unexpected happened everytime I start Minecraft... Can you help me?
Logs: https://mclo.gs/Q0A105w
1 messages · Page 1 of 1 (latest)
I was trying to make my own modpack called Spicedcraft but something unexpected happened everytime I start Minecraft... Can you help me?
Logs: https://mclo.gs/Q0A105w
Modpack:
Hello?
Is anyone here?
I don't have a crash log.
Okay?
Hello?
I need help!
Hello?
There are no crashes in any of your logs, unfortunately. Are you certain that the "crash-reports" folder (right click on instance -> "Open folder" -> navigate to "crash-reports") is empty?
If you're certain it's empty, then in the main instance folder, do you have any file that is named starting with "hs_err_pid" ?
If you do, please follow these steps carefully and make sure you do not upload the full file, only what these instructions say: <#1194471048238874754 message>
First off, this isn't pinging anyone.
u can only have 1 version. either forge. or neoforge.
1 | FORGE | DEFAULT | 2025-02-13 17:28:52 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | observable | 4.4.2 | FORGE | DEFAULT | 2024-11-30 12:21:28 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | betteradvancements | 4.2.25 | NEOFORGE | CLIENT | 2024-12-23 17:08:45 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | ae2wtlib | 15.2.3-forge | FORGE | DEFAULT | 2024-11-30 12:21:24 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | biomemakeover | 1.20.1-1.11.4 | FORGE | DEFAULT | 2024-11-30 12:21:23 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | redstonepen | 1.3.33 | NEOFORGE | DEFAULT | 2024-04-07 12:51:11 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | easymagic | 8.0.1 | FORGE | DEFAULT | 2023-07-22 21:00:40 |
[08Mar2025 17:22:14.920] [main/INFO] [Mods Optimizer/]: | biomeswevegone | 1.5.8 | FORGE | DEFAULT
all ur aether mods are also the wrong version... u got neoforge basically installed for all of them... not forge.
3rdly... this is an Error log everyone is confused on the JVM part of ur msg.
On 1.20.1 neoforge mods are generally compatible with lexforge and vice versa, so this is not accurate. Only for 1.20.2 onwards, this would be correct
There's nothing wrong with suspecting a JVM crash especially if the crash-reports folder is empty. JVM crashes will not log to that folder but may instead log in an hs_err_pid file on Windows
Taking a closer look at your log, I see that you have Create 6.0.2 in the instance. Create versions 6.0.0+ are a very new major version and many mods have yet to update to support this version of Create.
So, Create addons that aren't yet updated will cause crashes, and also non-Create-related mods that had compatibility code with Create can cause crashes.
A good start would be to try downgrading Create to version 0.5.1f, and see if it gets further.
Otherwise, the "binary search" method is a strategy to help track down mods that are causing crashes:
https://support.modrinth.com/en/articles/8792916-debugging-minecraft-crashes#h_d792d394c1
Alright, thanks.
Logs: https://mclo.gs/KRiSbqK
Minecraft Crashing without Crash Report - I need help!
Modpack:
It's most likely still going to be Create since you have the latest version of Create as well as a few Create addons.
The log doesn't contain a crash in it or any indication that something went wrong.
Unfortunately I've noticed that when Minecraft in the modrinth app crashes due to mods not updated to support latest version of Create, there may not be a crash report saved and the log will not contain the crash either.
I downgraded Create and all of its addons but all of the sudden... https://mclo.gs/eRDRhSm
You have a 1.20.4 mod in there (bundle recipe)
Oh.
Well... My modpack is f**ked up...