CQR incompatible with Magma servers
RaiderxD404 opened this issue · 12 comments
crash-2021-05-05_18.12.23-server (1).txt
crash-2021-05-05_17.50.50-server.txt
Crash on servers when approaching CQR mobs, or, when approaching bosses
Version: 2.5.3B
Modpack: https://www.mediafire.com/file/bk5m7p7ld0bfo8u/mods.rar/file
I have not tried
these bugs with only the mod ... but I hope it is a bug of the mod and a problem of the modifications, and if so, that the mod that is incompatible is open source and they can fix it, since it is quite annoying when I play on a server with this modpack
Issue got fixed in this Magma commit, it was caused by an unused java patch
Here's some proof if you don't believe me: https://youtu.be/LzF69bktTyc
If you want the bug fixed: Find the mod that conflicts with CQR and tell us so we can list it as incompatible. Also tell it the author of that mod so they can fix it.
could also be caused by magma, which is most likely the cause. We do not support server software other than forge.
Problem is Magma, however it ran fine with CQR v2.3.0B, you can find it on our website (NOT CURSEFORGE) or here on the github under releases
Problem is on magmas end, they either removed the "currentEntity" field from the NodeProcessor class or they added a mapping for it which is not defined in the stable_39 mappings which are used for 1.12.2 afaik and those mappings don't provide a mapping for that specific field which leads to the crash
Can't be caused by us. Must be a conflict with some other mod that loves to hijack the vanilla walkNodeProcessor which destroys our calls to fields from that
Yes, the npcs work, but a structure generated naturally with the npcs crashes immediately, sorry to explain it so badly, I did not know where to find the template
The missing field we need is added by forge. For whatever reason magma decides to not provide it. If you want it fixed: report to magma that the forge-added field „currentEntity“ in NodeProcessor is missing. This won’t be worked on.