Closed twilight-sparkle-irl closed 1 year ago
Well that's weird.
That field gets set when loading the config, which happens on every server resource load, which (at least on Fabric) happens pretty early and surely before any mobs get to tick. Either things happen out-of-order on Quilt, or the config is failing to load for some other reason, or i was wrong about how early that was and somehow i nor noone noticed until now
config field is null beforehand (which was a lazy fix for the config being unable to refer to mobs added by mods, cause i forgor about world load events)
I am rewriting the Everything atm (and i'm tempted to go "1.19.2 is unsupported, if you want to play the latest version you should at least have conviction"), i'll include a nullcheck or default value tho
n.b for debuggers, the 1.19.2 branch has the code for this version
Yeah, I noticed you were phasing out 1.19.2 but I figured it was at least worth noting. There's probably at least one or two other people out there like me who are also a little behind on the move to latest, too.
Seems to be related to the order in which mods load (adding and removing mods affects if it happens) and I have a sizable list of mods, so it's perhaps possible that resource load takes long enough that a mob ticks in the meantime?
Edit: Not sure if load order was just fine multiple times in a row or not, but it seems simply adding if (rule == null) return fallthrough;
over here causes the issue to no longer happen with no ill effect. I don't typically log out close enough to a mob for mobs temporarily being aggressive in the worst case scenario is a problem, so I haven't noticed anything not working properly so far.
Oh, forgot to close this. This should be resolved with 2.5.
Full log: https://mclo.gs/Cqhyr5u