Describe the Bug

Hi, I have found a bug with the cart assembler it has happened on create mod versions 1.16.5 - 1.17.1_v4.0 I am not sure which version of 1.16.5 because I had uninstalled that version many months ago, in fact, that bug had broken mine and my friend's modded server. So, the bug is that when you place down a cart assembler, put some sort of cart in it, connect any blocks to it, and then activate it with some sort of redstone power source it crashes the game. I am not sure why it does that, I am not a coder. I am just reporting the bug. I do know though it isn't just me, my friend uses the same mod and has the same issue.

Reproduction Steps

1. Place rail and cart assembler
2. Place cart in the cart assembler and attach some blocks to the cart assembler
3. Activate it with a redstone power source
4. Happens on versions 1.16.5_v I am not sure - 1.17.1_v4.0
5. Minecraft go die
   ...

Expected Result

Minecraft client crashes

Screenshots and Videos

There can be as many blocks as you want but a minimum of one attached to the assembler and it can be any block

Crash Report or Log

It didn't give me a crash report

Operating System

Windows 10

Mod Version

0.4.0

Minecraft Version

1.17.1

Forge Version

37.1.1

Other Mods

I had a lot of mods running, 129 to be exact. It won't allow me to add the zip file i made to show all the mods for some reason.

Additional Context

It is annoying. If you use a lever to activate it, the world is lost if you don't have backup. Please help.

If you don't have a crash, can you upload the log? Not sure which launcher you're using, so: Crash the game again, re-open it, go to options, resource packs, open pack folder, go one folder up, then into logs, and upload the most recent .log.gz file (such as 2022-01-18-1.log.gz). Without a log the mod developers can't know what's going wrong.

If you don't have a crash, can you upload the log? Not sure which launcher you're using, so: Crash the game again, re-open it, go to options, resource packs, open pack folder, go one folder up, then into logs, and upload the most recent .log.gz file (such as 2022-01-18-1.log.gz). Without a log the mod developers can't know what's going wrong.

I always use the new default Minecraft client (The one released in 2020), whether playing vanilla Minecraft or modded. The crash is very odd as it does not create a crash report folder nor create a crash report file. Here are the log.gz files that are created along with the text docs also made incase needed.
debug.log
latest.log
debug-1.log.gz
2022-01-18-1.log.gz

The text docs I am sure are to do with the launcher starting not with the actual game, but I wouldn't know I am not much into that sort of stuff.

I have no idea what the .gz files are for because they are gibberish, but there they are.

That is the error code and message that displays when the client crashes in case that is useful.

Let me correct a mistake I made in the original post about the issue, it does not happen in 1.16 versions anymore the developers must have fixed it for that version.

If you need anything else, please let me know!

That is odd. I'm playing version 1.17.1 with latest versions of Forge and mods, too.
Flywheel is the library that allows Create to do some of the fancy rendering things it does.

I was hoping the logs might have contained some information but I can't find anything that sticks out, myself. Apologies for not being able to help. I would've recommended a third-party world editor to the remove the broken entity to save your world from the crash-loop, but my recommendation does not support editing entities yet.

For the developers, a modpack link or mod list would be useful, if they wanted to try and reproduce the issue so they can fix it.

To resolve the issue on your end, all I can think of is just remove mods until it works again, perhaps graphics related ones if you have any. Then keep the offending mod out while adding the other ones back in. Do this on a backup, so you can apply the final mod-removal on the "real" world once, without potential losses of blocks, items or entities.

If you know exactly which mod causes this issue in conjunction with Create, that would also be very useful information.

All the developers need to reproduce the issue is version 1.17.1 minecraft. the Latest version of forge, not recommended version. the only and latest version of create 1.17.1 and the only latest version of the flywheel mod. and then follow the steps I have said in the original post to recreate it. Optifine was not in the mod pack when I tested anything.

Unfortunately, I am quite sure it is the create mod doing it, or the flywheel mod that must be in the mods folder with it, but I highly doubt that because I don't think the flywheel has anything to do with the cart assembler. The screenshot I sent above that was of the cart assembler was in its own test installation of Minecraft with no more mods than Create mod or fly wheel.

I am sure none of the mods are in conflict I was easily able to test this because I ran into the problem before on 1.16.5 versions, but they seem to have fixed it there. We have fixed the issue on my friend's server by just downgrading to 1.16.5 because almost all the mods have a version there, the only sad part is that the world corrupted so we had to make a new one. It was ok though it was a war server we were going to lose our progress anyways plus we weren't even that far in.

Sadly I don't think create 1.17.1 is going to be fixed because there has only ever been one version released for the create mod and flywheel mod and that was on dec 9th 2021, more than a month ago. I am not surprised though because even though 1.17.1 was a somewhat large update it was kind of short so mod developers didn't focus on it. So, we are planning to stick to 1.16.5 until 1.18+ is on a more solid base.

I was hoping the logs might have contained some information but I can't find anything that sticks out, myself. Apologies for not being able to help. I would've recommended a third-party world editor to the remove the broken entity to save your world from the crash-loop, but my recommendation does not support editing entities yet.

For the developers, a modpack link or mod list would be useful, if they wanted to try and reproduce the issue so they can fix it.

To resolve the issue on your end, all I can think of is just remove mods until it works again, perhaps graphics related ones if you have any. Then keep the offending mod out while adding the other ones back in. Do this on a backup, so you can apply the final mod-removal on the "real" world once, without potential losses of blocks, items or entities.

If you know exactly which mod causes this issue in conjunction with Create, that would also be very useful information.

It is odd, and I had not realized that is what flywheel does. And also, I know the file didn't corrupt because I tested on 2 different computers, and each time reinstalled both Forge and create + flywheel the crash happened every time. Hopefully, it will be fixed soon, and sorry I am not much help on information stuff about this, I am not much into this sort of thing.

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.