Closed Kingdomall closed 1 year ago
The previous version was built for beta versions of forge's 1.20.1 builds and it made breaking changes that was out of my control, causing these very issues.
The latest version actually addresses this error specifically and shouldn't happen again since it was built against a stable recommended forge build.
Give 1.1.5b3 a shot and then report back if it continues.
I did test it on 1.1.5b3, as I already stated. in fact I backtracked into 1.1.5.b2 to see if the bug existed on a previous version. I clarified this. Same crash and issue.
fortunately it looks like using a recommended forge version (47.1.0) fixes the crash and spawning issue. Thank you for pointing that out. I recall distinctly that you used to code purely on latest builds, so it didn't even cross my mind.
I learned a little bit earlier today after I wrote my comment that Forge is currently going chaos mode in response to the NeoForge split and drama. Something I did not expect in a million years from Lex of all people.
I apologize for the confusion there and unfortunately there isn't a whole lot I can do about the current state and situation of Forge. It is unfortunately a fast collapsing platform and it's becoming increasingly difficult to develop on it.
For now, I recommend pretty much everyone to just use the recommended forge build and developers to build against it as well.
This still affects the 1.19.4 version thats released and recommended. Any chance an update with the fix for this could be released?
using /summon dragonmounts:dragon, using a spawn egg, or hatching an egg will not result in the hatching of a dragon, and sometimes even a serverside crash. Here is the log: FYI: on this crash it shows that I am using the previous version. I guarantee you, the exact same crash happens on the latest version of this mod too. Don't know how this happens. https://mclo.gs/S5GJOLs