Crash when placing Logistical Transporter
Techtronik opened this issue ยท 4 comments
Issue description
I made logistical transporters and attempted to place them and it crashed the game, with subsequent crashes when I tried to load into that world. Attempted to troubleshoot by updating the mekanism mods to 7.11 and 7.12 but was unsuccessful in loading up our pack with the updated versions.
MedalTVMinecraft20250313165606-tr-edit.mp4
In case the video doesn't work, I attempted to place the logistical transporters on a vanilla oak log between 2 Easy Villager iron farms and above a Sophisticated Storage limited barrel 2. Not sure if any of those blocks could have been the cause but including what happened just in case. I've included the versions of these other mods below.
Steps to reproduce
- Make logistical transporters
- place logistical transporters
Minecraft version
1.21.1 (Latest)
NeoForge version
21.1.132
Mekanism version
10.7.10
Other relevant versions
Mekanism:
- base 10.7.10.73
- Generators 10.7.10.73
- Additions 10.7.10.73
- Tools 10.7.10.73
Other (just in case):
- Easy Villagers 1.1.23
- Sophisticated Core 1.3.2.900
- Sophisticated Storage 1.4.0.1077
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
Not sure what you mean? That's copied directly from the crash report generated by minecraft (or neoforge?). I just double checked and both that pastebin and the crash log include the same information. Here's the original file:
crash-2025-03-13_16.56.03-client.txt
And if it helps, here's the info from Crash Assistant from when I crashed trying to load into the world after the initial placement crash mentioned above:
Minecraft crashed. The logs have been uploaded to gnomebot.dev:
latest.log head / tail (~25k lines) | debug.log head / tail (~56k lines) | hs_err_pid43224.log | crash-2025-03-13_16.56.03-client.txt | KubeJS: client.log / server.log / startup.log | crash_assistant_app.log | win_event1741903300062.txt | CurseForge: skip launcher
Edit: Just noticed that crash assistant seems to have pulled the same crash log even tho it should have made another one when the subsequent crash occurred 3-4 mins later. Tho I can confirm that the original file wasn't edited further by Crash Assistant.
