[0.14.0.3] Crop growth models stay stale until nearby world/chunk update

[AWL-Gaming]

Version: 0.14.0.3 beta release-1060

Description

Crop growth visuals can remain stale while the plant itself continues growing server-side.

Flax example: plant reported 71% maturity, but its visible model remained at an earlier growth stage. Harvesting nearby grass immediately caused the Flax and nearby crops to update to their correct growth models, while the actual maturity percentage remained unchanged.

Expected behavior

Crop models should update normally as their growth progresses.

Actual behavior

Crop models remain visually stale until another nearby block/plant/world interaction causes the surrounding chunk to update.

This appears very similar to an old issue that was previously fixed:

• Crops do not update their model as they grow. #1406
• Trees and plants dont appear to grow while you sleep #9057
• USER ISSUE: Models Not Updating After Sleep or /FF #21159

In particular, #1406 describes essentially the same behavior: nearby plant interaction caused multiple stale crop models to suddenly update.

Relevant code

Growth state / refresh handling:

https://github.com/StrangeLoopGames/Eco/blob/4190651bbee265e355050039d0a5fbec022cb5de/Server/Eco.Simulation/Agents/Plant.cs

Plant growth encoded into block extra data:

https://github.com/StrangeLoopGames/Eco/blob/4190651bbee265e355050039d0a5fbec022cb5de/Server/Eco.Gameplay/Plants/PlantBlocks.cs

Client-side plant growth/model update:

https://github.com/StrangeLoopGames/Eco/blob/4190651bbee265e355050039d0a5fbec022cb5de/Client/Assets/EcoEngine/VoxelEngine/Core/Jobs/UpdateChunkPrefabsJob.cs

Chunk serialization / extra block data refresh:

https://github.com/StrangeLoopGames/Eco/blob/4190651bbee265e355050039d0a5fbec022cb5de/Server/Eco.World/WorldChunk.cs

World.ForceUpdate API:

https://docs.play.eco/api/server/eco.world/Eco.World.World.html

Notes

The actual plant maturity does not appear to jump when the nearby interaction occurs; the visible model catches up to an already-existing server-side growth state.

This looks like a plant/chunk synchronization or dirty/update regression rather than a growth-rate calculation issue.

[D3nnis3n]

This might actually have been purposeful for performance reasons, so no promise on a fix.