Bloom Garden
A cooperative garden with persistent plant state, server-clock offset estimation, and pooled petal animations.

A cooperative garden experience where players work together to maintain a living garden and awaken the Big Bloom.
Its Multiplayer Server uses built-in Storage for plant state, a weekly leaderboard, and per-player watering limits.
Project information
Maintained by: Community · TheLivingGarden
License: MIT. Check upstream terms before reuse; code and assets may have different terms.
Explore the code
These links point to a specific source snapshot so the explanations remain useful as upstream development continues. They are learning references, not a security assessment.
Estimate the offset between server and client clocks
The clock helper keeps five offset samples, rejects large deviations, and converts server timestamps into local time. The watering client feeds it timestamps received through the scene's message definitions.
Project context: This illustrates a lightweight timing estimate; network transit time is included in the samples.
Source references:
Let temporary effects finish naturally
The petal setup and controls create a reusable pool from the scene's named Petal model, then start or settle the effect. The update phases scale petals in, let them fall and rest, and shrink them before recycling. Study this when an effect should stop spawning while existing objects complete their animation.
Project context: Placement depends on BLOOM_CENTER and the module's timing constants.
Source references:
Last updated