Hardening of some sort needed in DelayedActionSystem (plant growth can cause NPE crashes?) #2473
Open
2 of 7 tasks
Labels
Good First Issue
Good for learners that are new to Terasology
Multiplayer
Affects aspects not visible in Singleplayer mode only
Type: Bug
Issues reporting and PRs fixing problems
During multiplayer event the server crashed a minute after @rzats had himself crashed out via Terasology/JoshariasSurvival#14 shortly after I crashed out via #2361
I suspect something about the blueberry bush growth stages from JoshariasSurvival, which is based off SimpleFarming which in turn uses the DelayManager system from the engine. If I were to wager a guess there was an immature blueberry bush in a chunk one of us had been in that had its growth tick in a way that was no longer valid with no players left on the server.
Crash happened in
DelayedActionSystem
and while the log doesn't identify exactly what the scheduled action was I think a fair bet would be a blueberry bush. That in turn is defined inBlueberrySeed.prefab
from JoshariasSurvival, which has aPlantDefinitionComponent
that still has a bit of logic and other fanciness despite being a Component (old code I suspect). The related logic system isFarmingAuthoritySystem
which is what in turn uses the DelayManager.So some things to consider looking at:
DelayedActionSystem
to where it has error handling for encountering invalid scheduled actions (expect that invalid tasks could be created somehow)PlantDefinitionComponent
also from SimpleFarming to follow code guidelines (no logic in Components, keep them basic)Error log below (server side):
The text was updated successfully, but these errors were encountered: