Ticking entity crash from arrows when ranged mob effect config is changed
Treeways opened this issue ยท 4 comments
When updating files in kubejs/data/apotheosis/affixes/ranged/mob_effect/*, any arrows shot after the change will eventually cause a null entity ticking error.
Changing this config on a previously generated world is extremely dangerous, and causes world corruption. The server crashes on boot once this crash happens the first time.
I modified the caps on some effects, and removed others. Here's the full diff: 1.19...Treeway7:Apotheosis:1.19
(There are no JSON errors in these files.)
At first glance that looks like user error. You would need to show the files you have changed and how they differ from the originals.
I also pushed the other data I've modified so far here on a different branch: 1.19...Treeway7:Apotheosis:full-changes
Removing the arrow mob effect files fixes the bug.
My best guess is that the condition-false statements are messing with the already summoned arrows, but I haven't done any testing to confirm this.
Based on the diffs the error comes from in-flight arrows retaining affixes where you reduced the rarity scope, which then crashes.
The condition-false ones aren't crashing.
You can just perform your changes, enable RemoveErroringEntities in the forge config, and then all "broken" arrows will be cleared (no new ones may be introduced).