ALife WorldsPrivate alpha ↗
← ALife Worlds

PRIVATE ALPHA · RELEASE ROADMAP

What’s working.
What comes next.

A clear record of the current world and the work still ahead.

Current baseline

World 1.1.1 is deployed to the existing connected world destinations. Plugin 0.2.2 is the qualified runtime baseline; 0.2.3 is the documentation and roadmap update. This page adds no new world behavior.

The runtime correction gives corresponding worlds stable initial scenery placement and shared visual identities across local and sanitized website views. It uses one measured scene budget for planning and painting. Source checks, production builds and live-feed checks passed; matching browser geometry and visual alignment remain unverified.

The world-owning chat’s title now follows the recorded world version, with an actual rename and readback required for release completion. Plugin, world and hosting versions are tracked separately.

The public world shows a sanitized view of real observed activity and recorded progress. Cosmetic Interact mode makes no AI calls and cannot edit project work. View disables scenery interactions. Owner-private access and eligible local controls remain separate.

Requested world changes

These are selected changes and retained requirements. A saved rule, a source check or a passing feed check does not mean every visual state has been accepted.

Next correction: visible requests for your input

Fix the reported missing attention animation while an agent is waiting for a real answer or approval. A still-pending request must remain visible without inventing fresh work. The ant should leave its bed, stand in clear room space, face you, wave both front legs and jump beneath a yellow warning triangle. Special Forces must remain visible when its combat animation is paused. Real replies and resumed work clear the indication; ordinary idle, blockers and stale activity do not create it.

Quiet room names and seamless soil

Move room names into the lower, lighter floor patches using consistent readable white text for every role. Keep full accessible names, responsive sizing, disabled-action reasons and one selected-room detail panel. Preserve the irregular, separated rooms and safe routes. Remove the actual horizontal seam between the mound and underground soil while retaining the darker depth gradient and ground transition.

One coherent woodland and six-stage sprint tree

Build the selected connected pixel-art tree states: seed, sprout, sapling, young, mature and complete. Keep the real sprint tree in the left foreground; growth follows accepted progress, with exact details available on inspection. Watering and elapsed time earn no progress.

Replace the broken-looking background pines and carry the selected style through the sky, clouds, layered mountains and forest, warm-window houses, distant road and people, water, reeds, rocks, grass and soil. Keep coherent day, sunset, night and sunrise lighting, seasons, rain streaks and winter snow. Investigate white or broken trees, stray rain effects and tags whose ant bodies disappear. Custom worlds retain their own art.

Grounded movement, clear layers and safe water routes

Confirm that ants walk around full pond footprints, intact rocks, gems and unintended rooms; collect water from a reachable dry shore and carry it to the actual sprint tree. Keep connected room exits and shaft routes. Verify forward diagonal and horizontal gait, distance-based delivery pacing, dangling drag poses, outdoor gravity and safe catch-up after a drag.

Keep distant people and planted feet behind the nearer pines and hill, with a separate foreground layer. Preserve grass plucking and regrowth, replacement gems, addressed M-envelope delivery and eligible dirt footprints. Scenery trips never manufacture task progress.

World version and immersive fullscreen

Add the actual served world version beside permitted sprint progress in the normal information row below the world. Fullscreen should show only the world, hide the entire footer and surrounding page content, fill the viewport without stretching ants, and use black for unavoidable uncovered areas. Native fullscreen and the supported full-window fallback need an accessible exit that restores layout, focus, scrolling and mode. The existing fullscreen button does not by itself satisfy this newer request.

Special Forces and first-responder scenes

Preserve and qualify the three spaced soldier ants defending the exterior hill during actual Special Forces work. Verify the four initial wasps, at least four health per wasp, aimed weapons, multiple-hit combat, distinct defeats, bounded replacements and return after real resolution. These soldiers are cosmetic companions, not additional native agents.

Retain genuine blocker fires, Agent Support alarms and medical/garage props, fire-truck hose response, and retirement ghost, grave, corpse, flies and ambulance CPR scenes. No animation resolves a blocker, revives or retires a real agent. Idle and unavailable activity must remain truthful.

Mining, scenery, sound and motion

Retain stable two-to-eight-hit rocks and gems. Gems keep their size until the final break and accumulate chip lines; rocks may progressively chip and shrink. Broken debris becomes walkable. Keep local dirt puffs, tree leaves, larger one-to-five-hit flies, fleeing fireflies, parallax clouds and scenery reactions within motion limits.

Keep the bundled CC0 lo-fi music and UI, grass, water and mining sounds. Every load starts muted; one Sound control enables audio and reveals its volume slider. Mute hides the slider and immediately silences all sound. Pause, hidden-page and reduced-motion guards remain. Earlier scoped listening feedback is retained; current device and rare-state checks are separate.

Projects, fit, privacy and controls

Keep the world full-width and first, followed by the sprint board, current tasks and recorded handoffs, collapsed responsibilities and the collapsible epic/sprint plan. Progress stays canonical. Public mode permits page scrolling below the fitted world; Private and View fit one screen and remove operational sections from layout. View keeps safe names and disables mining, drag, hops and operational actions.

Project selection must resolve the exact selected world and use its folder name. Show all keeps each world contained in its own planet, with one centered planet when appropriate. Preserve public cosmetic Interact, owner-only private access, saved publication preferences and existing custom art.

Separate capabilities still to build

Real agent messages and Wake Up, Unblock and Retire requests need a supported, verified native connector. A real queued-message room phone also needs an actual pending-message signal. These capabilities remain unavailable; disabled controls must explain why. No fake message queues or successful sends are shown. Selected import, delete and copy/clone workflows need their own integration and qualification.

Steps toward a public release

  1. Finish startup and command qualification. Verify fresh three-core setup, safe reuse, the first Director title, the submitted Building world state, launcher behavior and supported rule commands in an isolated project.
  2. Deliver the selected world changes in order. Publish this checklist first, fix the attention defect next, then work through room labels and soil, the woodland and tree, navigation checks, fullscreen and remaining visual states. Keep original criteria and recoverable releases.
  3. Complete website and package readiness. Keep setup instructions, links, versions and limits accurate. Verify actual screenshots and a demo, clean installation and the reviewed final package. The custom domain’s outer redesign still needs its existing hosting upload; its world viewer already uses the current hosted world.
  4. Review public repository content and history. Check private data, secrets, licenses, art provenance and recovery before changing visibility. Public source and download access are not available yet.
  5. Complete review preparation. Confirm the eligible plugin route, publisher and organization details, required permissions, listing, examples, reviewer access and demonstration. Privacy, terms and support pages are live; publishing those pages is not legal approval or submission approval.

Native messaging, broader customization, unselected legacy imports, extra skins and broad cleanup are separate scoped work. Their presence on a backlog does not make them universal blockers for the read-only core.

What is still unverified

The latest pass closed at the owner’s request without browser verification. Actual cross-surface geometry, owner-authenticated private browsing, physical mobile behavior, current listening and the full set of rare world states remain unverified. Source tests and HTTP readbacks are recorded separately.

Earlier feedback confirmed a limited subset of visible ants, readable names and sound controls. It is not whole-world acceptance or proof for a newer wrapper. Animation, mining, watering and combat never count as accepted work.

There is no public release date or complete-release claim. Check this roadmap as the remaining work is implemented and verified.