Minecraft Version

1.18.2

Forge Version

40.1.0

Mantle Version

1.18.2-1.9.20

Tinkers' Construct Version

1.18.2-3.5.0.17

Describe your issue

Upon launching with T-Construct either enabled or disabled, the game crashes and issues an "Error:1" code. The pack I've developed works with Mantle installed, but for some reason it causes an issue if T-Construct exists in the pack at all.

Mods are listed below as well.
Performance Enhancer mods are: Radium and Radon.

Crash Report

No response

Other mods

Tried reproducing with just Tinkers?

I will go do that now (Edit: Just tested with just Tinker's. Crash still occours.)

Performance Enchancers

Other (specify under other mods)

Searched for known issues?

Checked pinned issues, Searched open issues, Searched closed issues

Since you say it crashes but provide no crash log there is not much we can do.

Ah! I have found the issue! Version of Forge is outdated for T-Construct. Updating the version to see if that solves it.

Doing my best to figure out a way to pull the crashlog from GD Launcher.

2022-05-09-7.log.gz
Managed to get the log of the crash!

Unless I am missing something, that isn't a log, I opened it in Notepad++ and it is a bunch of gibberish.

And to add to this: My game works just fine with pretty much the same mods.

Try using the latest version of Forge instead of the recommended.

That is a log in a compressed file format @Dreki1984, its the format mojang uses for logs once its no longer latest.

@RedstoneFox that log has no mention of Tinkers' Construct, all I see is an exception in maxhenkel.gravestone. Clear out your logs folder, then run the game and give me the latest.log. Alternatively, switch to the vanilla launcher and copy over your mod list, its likely your launcher is messing with the logs

Here is a copy of the latest log with just TC and Mantle Installed
latest.log

That log has surprisingly little information. Got a debug.log file? You could also try running on the latest forge. build 40.1.19 instead of 40.1.16

Here's the debug with 40.1.19 and latest log.
debug.log
latest.log

That debug.log still lacks any information that tells me why its not working. I could produce the exact same sort of log by starting the game then quitting once I reach title screen.

Please verify whether this issue happens on the same forge version without tinkers. Also test without both tinkers and mantle. Get the same two logs for each.

This is getting odd... The maxhenkel.gravestone and maxhenkel.corpse shouldn't show up as I don't have those mods installed at all.

Here's the latest log after clearing out the old ones.
latest.log

Log from the Curseforge launcher
latest.log

Currently about to test from the Vanilla/Curseforge launchers to see if there is any difference.

Debug and latest log from the vanilla launcher
debug.log
latest.log

To add on, same as before ^^ settings wis
latest.log
This is the only information the log displays with it open as minecraft prepares. Possible an issue with Mantle?

What makes you think its a Mantle issue? You are randomly guessing problems instead of taking time to debug.

Most of the logs tell me you have a class not found error with the mods I mentioned above. Some mention a class not found error with a different mod class (snownee.snow or me.jellysquid.mods.sodium). Your last one (BlackStarG5s) has Optifine, which is bad, but most don't have Optifine. In general though, none of them have a clear error.

So, rather than randomly blaming mods, lets narrow down the problem. I know Tinkers' Construct works in large modpacks, its actively being used on the ForgeCraft server and in Darkosto's in dev Journey 2 the Core pack, and neither is having issues. This means one of your mods is causing problems. So lets narrow down the issue:

• You claim you tested with only Tinkers' Construct. If that is true, give me a log with only tinkers construct, all this mixin spam is not helping read the log and we dont use mixins.
• If you cannot get a crash with only tinkers, narrow down the minimal mod list to make this happen.

We can do more debugging once you find me a minimal mod list then get me a log or crash report with a minimal list.

I'll do my best to limit down the modlist to what causes it to crash.

Same as well, Sorry for for my random assumption I don't code java anymore haha lost a lot of skill in it :). I'll start by comparing my mod list with yours RedstoneFox to see if we have any mods in common

@RedstoneFox DUDE LMFAO I JUST READ YOUR LOG
USE 40.1.16 forge loader
Currently using 40.1.19 (No issues yet)

The crash is when launching Minecraft itself, not to do with messing around in a world. I'm gonna spend a few hours and try slowly adding in mods to test and see which mod might be causing the crash.

@KnightMiner I have discovered the issue. When Create and Tinker's is installed together it crashes upon launch and gives me a repeatable "Error: Uncaught Fatal Exception code: 1".

Wait... no, now it's working nicely...

I finally managed to pull open and pull the console logs directly from GD Launcher. I threw Tinker's and Mantle into a duplicate of the pack I've been working on and this is the word spaghetti it throws back at me
Launcher console Error thingy.txt
.

Issue has been narrowed down to Pehkui. Will be bringing it to that dev's attention. Sorry for the hold up fellows.