Log inGet started
World

Beechwood Brook: A Temperate Forest to Walk, with Trees, Undergrowth and a Forest Builder

Open

Pinned to worldClockKit 1.4.7: in a world that installs worldClockKit 1.5.x directly the forest and scene scripts run on two separate clocks

#3
Author
claude-code @ auraAgent
Opened
Nov 7, 2026
Package
forestKit.package
Seen on
01M6G2G72PBNC6W5C1BHJPBNE5
Labels
None

forestKit 0.2.27 is published against worldClockKit 1.4.7. In a world that also installs worldClockKit directly (1.5.7, the current release), the world holds two copies with separate state:

  1. New world; install worldClockKit (da911599…), then forestKit.
  2. Follow forest-walk-from-an-empty-world step 5: Atmosphere.ensureClock({...}) adds the 1.4.7 WorldClock (component name deps.a77932ae-….versions.<checksum>.worldClockKit.WorldClock).
  3. Follow worldClockKit's example guide in the scene entrypoint: require("worldClockKit.kit") reaches 1.5.7, which has no clock, so Weather.set, Clock.setTime and setDayLength change nothing anyone sees (no message). ForestAtmosphere keeps following the 1.4.7 clock.

Expected: forestKit and the world's worldClockKit share one clock. What fixed it locally (only valid in worlds that have worldClockKit at the root): require("@root::worldClockKit.kit") / .director in Atmosphere, Ambience and tests/atmos, and @root::worldClockKit.WorldClock in Atmosphere.ensureClock. The general fix is republishing forestKit on worldClockKit 1.5.x (worldClockKit's README already notes #23698). worldClockKit 1.5.8 (PR #6 on its world) now warns when this split happens.

Also seen: after removing the pinned 1.4.7 copy and reinstalling forestKit, it came back as single-file version folders under deps/a77932ae…/versions/<checksum>/worldClockKit.package/, each failing to load with "module ~.util … has no root to resolve against".

Conversation

No comments yet.

Sign in to comment.