Seems like a newer version of this mod has introduced a conflict with Secretmapper's Accelerating Zombies, I used to use them together without problems but now they cause infinite error spam once sprinters are activated. Did brute force testing to narrow it down and it still happens with only these two mods active. Not sure if it's just that that mod needs an update or if anything can be done on your end to mitigate. I'll also note this on the SAZ workshop page but the mod hasn't been updated since 2022 so IDK how active the author still is. Stack trace:
STACK TRACE
-----------------------------------------
function: handleUpdateAccZ -- file: AcceleratingZombies.lua line # 72 | MOD: Secretmapper's Accelerating Zombies
LOG : General , 1711225171183>
LOG : General , 1711225171183> -----------------------------------------
STACK TRACE
-----------------------------------------
function: handleUpdateAccZ -- file: AcceleratingZombies.lua line # 72 | MOD: Secretmapper's Accelerating Zombies
LOG : General , 1711225171183> __mul not defined for operands in handleUpdateAccZ
ERROR: General , 1711225171183> ExceptionLogger.logException> Exception thrown java.lang.RuntimeException: __mul not defined for operands in handleUpdateAccZ at KahluaUtil.fail line:82.
ERROR: General , 1711225171183> DebugLogStream.printException> Stack trace:
java.lang.RuntimeException: __mul not defined for operands in handleUpdateAccZ
at se.krka.kahlua.vm.KahluaUtil.fail(KahluaUtil.java:82)
at se.krka.kahlua.vm.KahluaThread.luaMainloop(KahluaThread.java:676)
at se.krka.kahlua.vm.KahluaThread.call(KahluaThread.java:163)
at se.krka.kahlua.vm.KahluaThread.pcall(KahluaThread.java:1980)
at se.krka.kahlua.vm.KahluaThread.pcallvoid(KahluaThread.java:1812)
at se.krka.kahlua.integration.LuaCaller.pcallvoid(LuaCaller.java:66)
at se.krka.kahlua.integration.LuaCaller.protectedCallVoid(LuaCaller.java:139)
at zombie.Lua.Event.trigger(Event.java:64)
at zombie.Lua.LuaEventManager.triggerEvent(LuaEventManager.java:92)
at zombie.characters.IsoZombie.updateInternal(IsoZombie.java:2342)
at zombie.util.lambda.Invokers$Params1$CallbackStackItem.run(Invokers.java:37)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:71)
at zombie.core.profiling.AbstractPerformanceProfileProbe.lambda$invokeAndMeasure$0(AbstractPerformanceProfileProbe.java:83)
at zombie.util.lambda.Stacks$Params3$CallbackStackItem.invoke(Stacks.java:230)
at zombie.util.lambda.Stacks$GenericStack.invokeAndRelease(Stacks.java:26)
at zombie.util.Lambda.capture(Lambda.java:130)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:81)
at zombie.characters.IsoZombie.update(IsoZombie.java:2219)
at zombie.MovingObjectUpdateSchedulerUpdateBucket.update(MovingObjectUpdateSchedulerUpdateBucket.java:79)
at zombie.MovingObjectUpdateScheduler.update(MovingObjectUpdateScheduler.java:162)
at zombie.iso.IsoCell.ProcessObjects(IsoCell.java:2955)
at zombie.iso.IsoCell.updateInternal(IsoCell.java:5750)
at zombie.util.lambda.Invokers$Params1$CallbackStackItem.run(Invokers.java:37)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:71)
at zombie.core.profiling.AbstractPerformanceProfileProbe.lambda$invokeAndMeasure$0(AbstractPerformanceProfileProbe.java:83)
at zombie.util.lambda.Stacks$Params3$CallbackStackItem.invoke(Stacks.java:230)
at zombie.util.lambda.Stacks$GenericStack.invokeAndRelease(Stacks.java:26)
at zombie.util.Lambda.capture(Lambda.java:130)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:81)
at zombie.iso.IsoCell.update(IsoCell.java:5696)
at zombie.iso.IsoWorld.updateInternal(IsoWorld.java:3499)
at zombie.util.lambda.Invokers$Params1$CallbackStackItem.run(Invokers.java:37)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:71)
at zombie.core.profiling.AbstractPerformanceProfileProbe.lambda$invokeAndMeasure$0(AbstractPerformanceProfileProbe.java:83)
at zombie.util.lambda.Stacks$Params3$CallbackStackItem.invoke(Stacks.java:230)
at zombie.util.lambda.Stacks$GenericStack.invokeAndRelease(Stacks.java:26)
at zombie.util.Lambda.capture(Lambda.java:130)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:81)
at zombie.iso.IsoWorld.update(IsoWorld.java:3427)
at zombie.gameStates.IngameState.updateInternal(IngameState.java:1617)
at zombie.gameStates.IngameState.update(IngameState.java:1333)
at zombie.gameStates.GameStateMachine.update(GameStateMachine.java:101)
at zombie.GameWindow.logic(GameWindow.java:298)
at zombie.core.profiling.AbstractPerformanceProfileProbe.invokeAndMeasure(AbstractPerformanceProfileProbe.java:71)
at zombie.GameWindow.frameStep(GameWindow.java:765)
at zombie.GameWindow.run_ez(GameWindow.java:681)
at zombie.GameWindow.mainThread(GameWindow.java:495)
at java.base/java.lang.Thread.run(Unknown Source)
Seems like a newer version of this mod has introduced a conflict with Secretmapper's Accelerating Zombies, I used to use them together without problems but now they cause infinite error spam once sprinters are activated. Did brute force testing to narrow it down and it still happens with only these two mods active. Not sure if it's just that that mod needs an update or if anything can be done on your end to mitigate. I'll also note this on the SAZ workshop page but the mod hasn't been updated since 2022 so IDK how active the author still is. Stack trace: