Inspirations

Inspirations

25M Downloads

1.20.1 Crash on startup when inspirations is added (also there's no 1.20.1 template)

caniplzjustlogin4godsakesthistakesforev opened this issue ยท 8 comments

commented

Games Crash only occurs when adding inspirations, game works fine with mantel.
Other mods present, probably a compatibility issue.
crash-2025-08-19_10.48.59-client.txt

commented

Your crash report has a ton of things that are suspect. Notably, you have connector, which breaks forge mods, and you have a lot of mods with mixins into the block state registry. Reproduce this issue with a smaller mod list so we can figure out which mod you have installed is breaking it.

commented

This crash looks to be a cascading error, where the actual error causing this is not present in the crash log, and happened much earlier.

Can you share the full latest.log file (from the logs folder) rather than the crash report, as the crash report doesn't seem to have enough information.

commented

I had a similar bug - not sure if its the only issue but both Supplimentaries and Inspirations include changes to the vanilla cauldron and it gives a crash that looks like this. If you disable inspirations cauldron changes in the config the crash stops.

Correction: Its the Amendments mod; which is a spinoff of the supplimentaries mod.

crash-2025-08-31_00.40.03-client.txt

commented

@estradus could you provide the full log file? The crash report is not incredibly helpful in this crash.

commented

The fact that it crashes if both mods are trying to change the same feature is not surprising. I've seen at least one mod with cauldron features that are nearly identical to mine that causes that, there is no reason to enable both even if it didn't crash, and there is no logical solution other than it crashing, so thats not something I can fix.

Checked the crash report, looks like the same issue I recall. Whatever mod you have that is modifying the cauldron is doing so in an illegal way: mods should never add new block state properties to vanilla blocks as that can lead to save corruption. Forge is thinking my mod is trying to change block states when the reality is my mod is keeping them the same and your other mod is changing it. Either disable that mods feature or mine, no other way around it (even without the crash you can't have both our features active I'd wager)

commented

@estradus could you provide the full log file? The crash report is not incredibly helpful in this crash.

Ye sure thing.

2025-08-31-2.log.gz

It is a lot of similar features for sure; not sure that compatability is really in the cards so much as narrowing down what the problem is compared to the giant pile of mods they had.

Both this and amendments have a similar vibe of vanilla+ so it does make sense there would be overlap.

commented

Ye sure thing.

2025-08-31-2.log.gz

That is an old log archive that doesn't have the crash in it. Make the crash happen then there will be a file called latest or latest.log that has a log of the crash.

commented

My apolgies; just coming back from a minecraft haitus. Here. Its short!

latest.log