[Bug]: odd tickrate spike every second only with werewovles installed
EnderMelody opened this issue ยท 3 comments
Minecraft Version
1.18.x
Forge Version
40.1.68
Vampirism Version
1.8.5
Werewolves Version
0.6.1
Modpack
private pack
Singleplayer/Multiplayer
Singleplayer
What happened?
having werewolves installed causes high tick times every second in certain areas. the spikes are consistent and only appear with werewolves installed. These spikes only occur in certain areas, so im not sure what is causing it, possibly conflicting with another mod? reloading the world doesnt change anything, but reloading the the world without werewolves and then re-adding the mod seems to remove what causes the lag spikes.
seed used: -1217379669675027576
Worlds tps with werewolves: Spark: https://spark.lucko.me/NlKlZ51Cl6
Same worlds tps without werewolves: Spark: https://spark.lucko.me/GgTpEI0MEG
Same worlds tps after loading the world without werewolves then adding it back in: Spark: https://spark.lucko.me/P1R8NbBzcQ
Relevant log output
log with werewolves: [2022-08-10-with.log](https://github.com/TeamLapen/Werewolves/files/9302594/2022-08-10-with.log)
debug:[debug-with.log](https://github.com/TeamLapen/Werewolves/files/9302598/debug-with.log)
log without werewolves: [latest-without.log](https://github.com/TeamLapen/Werewolves/files/9302913/latest-without.log)
debug:[debug-without.log](https://github.com/TeamLapen/Werewolves/files/9302912/debug-without.log)
log after re-adding: [latest-readd.log](https://github.com/TeamLapen/Werewolves/files/9302918/latest-readd.log)
debug: [debug-readd.log](https://github.com/TeamLapen/Werewolves/files/9302917/debug-readd.log)
Reproduce steps
- load singleplayer world with the modpack.
- depending on the area, you will see server tickrate lag spikes
Other relevant mods
No response
There is no need to create multiple issues
sorry, my github broke and posted it multiple times
I found the start of an erroring chunk and marked before and after entering it and consistently lagged only when in that area so it is defiantly something persistent and in a specific area. Checking the debug logs shows that there is nothing reported in them so im really not sure what's causing the problem, only that removing werewovles fixes it every time.