JunoJR Learning
Skip to learning content
← Choose a project

🌴 Self-paced family project · 6 missions

Jelly Jungle: Become a 3D World Architect

Build a five-island 3D world together: steer a pink jelly, collect five crystals, recover at the blue checkpoint and add a spring you can explain and test.

No installation, payment, child account, or AI key to begin in the browser. Later authored missions use guardian access. Full project extensions may need additional tools.

What you will make

Original five-island starter inspired by the family Jelly Jungle astra-version project

  • Distinguish creation assistance from runtime rules.
  • Construct a world from shared coordinate data.
  • Implement a spring with feedback.
  • Verify recovery, collection, reachability, and graphics separately.

Settle in together

Laptop or desktop, keyboard, and a browser with WebGL. Internet is needed to load the 3D tools. A phone can read along; graphics support varies.

Allow about 10 minutes to get ready. Six missions in order. Try one or two 5–12 minute activities, take a break, and resume at the next activity. Plan several short sittings per mission; the full 75–90 minute lesson remains the detailed reference. End each sitting with a saved copy and one sentence: next time we will… Times are estimates awaiting family pilots.

  • For ages 9–12, work beside a parent on a computer with a keyboard. A phone can read the guide and watch; use a computer for editing. Older learners may try the full lesson's stretch task after the core checks.
  • Open the first mission's browser workspace and press Run before installing anything. No payment, child account, or AI key is needed for that introduction. If the runtime reports unavailable, keep your files, read its error, and use the course-specific fallback below with adult help.
  • Before ANY local trace, model test or build, use this course’s full reference handoff: Save and Export backup, retain the JSON backup, extract the matching ZIP into a new folder, copy every current source file with transfer-workspace.mjs, and run verify-workspace.mjs with your actual edited value from that extracted folder. JSON is a source backup, not an executable ZIP; Import backup does not update disk files. Keep results beside the exact source version tested. If you skip transfer, label downloaded checks baseline-only.
  • The browser introduction uses the real JavaScript/Three.js teaching world. It needs a WebGL-capable browser; no AI service runs the game. If the 3D runtime is unavailable, note the error and keep the route drawing while the parent prepares the download.
  • For the downloaded /lab-starters/jelly-jungle-3d.zip, follow README.md: parent-prepared Node 20.19+ or 22.12+, npm install, npm test, npm run dev, then the localhost URL printed by Vite. Package installation needs internet. Double-clicking index.html does not resolve the modules. Use npm run build and npm run preview for the later built demo.
  • Read model.js (ISLANDS, RULES, createState, step), main.js (controls, camera, drawing) and index.html (instructions). Keep style.css and tests/model.test.js with the project. All required art is made from shapes; no generated mesh or paid asset is needed.
  • WASD/arrows move; Space gives up to three jumps before landing. P pauses and R restarts. Blue saves recovery; gold finishes only with all five unique crystals. Falling keeps crystals; Restart clears the run. The displayed checkpoint number is the saved index plus one.
  • Keep the original starter unchanged as a reference. Export a working copy before a risky edit or reset. Work and the optional progress checklist stay on this device; an export is your portable backup. A checked box records your own report, not a verified assessment.
  • Use invented names, notes and records. The parent handles accounts, optional AI and sharing. Predict together, let the child make one choice, change one thing, test it, then explain what happened. An assistant is optional; the supplied code and a partner work too.
Parent help, saving & device setup →

Two people, different jobs

Child · driver & designer
Draw the route, choose one change, play the same experiment twice and show which rule made the result happen. You can dictate edits while your parent types.
Parent · thinking partner
Keep a working copy, read errors aloud and help locate model.js versus main.js. Ask for a prediction before taking the keyboard; let the child choose the world change and explain its result.

A path you can pause

These are complete missions, not one-sitting deadlines. Each family guide breaks the work into small activities. Return to the last activity you chose to remember.

  1. MISSION 1 · PUBLIC FIRST MISSION

    Plan your first floating world

    Run a five-island 3D world and define one improvement you can explain.

    Full mission plan: 90 minutes · split across activities

  2. MISSION 2 · GUARDIAN ACCESS

    Build with coordinates and predictable state

    Change shared world data and trace a deterministic simulation.

    Full mission plan: 90 minutes · split across activities

  3. MISSION 3 · GUARDIAN ACCESS

    Make movement feel intentional

    Tune one movement value and test interruptions across control methods.

    Full mission plan: 90 minutes · split across activities

  4. MISSION 4 · GUARDIAN ACCESS

    Grow a spring island

    Add a spring launch with matching feedback and testable rules.

    Full mission plan: 90 minutes · split across activities

  5. MISSION 5 · GUARDIAN ACCESS

    Test beyond the happy path

    Verify recovery and a complete route, separating model evidence from browser evidence.

    Full mission plan: 90 minutes · split across activities

  6. MISSION 6 · GUARDIAN ACCESS

    Present your world as an architect

    Demonstrate the complete world and defend the decisions that made it playable.

    Full mission plan: 90 minutes · split across activities

Leave a trail for next time

The optional mission checklist remembers your place in this browser. Workspace files have their own save controls; export them for a portable backup. Write down one change, one test observation, and the activity you want to try next.

Download the original starter for the full local project ↓
About this family pilot

Authored from family project evidence with an original teaching starter. Classroom timing and the actual learner devices need a facilitator rehearsal; this draft is not classroom validated.

Complete course plan · extended setup, camp & project evidence

Begin in the browser workspace with no installation. The original tools and prerequisites below apply to the full downloaded project and its extensions. Native mobile tools and physical hardware are separate adult-prepared steps. Portfolio themes describe your project; no credential is automatically awarded.

Build a procedural 3D adventure with an adult-operated Astra-style creation assistant, then verify its world, controls, and spring island.

Full course platforms: Web browser with WebGL · Keyboard and touch · Ages 9-10, 11-13, 14-16

Your project

Original five-island starter inspired by the family Jelly Jungle astra-version project

  • Distinguish creation assistance from runtime rules.
  • Construct a world from shared coordinate data.
  • Implement a spring with feedback.
  • Verify recovery, collection, reachability, and graphics separately.

Before you begin

  • Comfort editing a JavaScript object; Bounce Lab or equivalent helps.
  • An adult can prepare Node 20.19+ or 22.12+ and a WebGL browser.

Materials

  • Computer with WebGL browser
  • Prepared Node runtime and editor
  • Paper for coordinate mapping

Your tools

Jelly Jungle starter
Complete original procedural 3D game and model tests.
Download /lab-starters/jelly-jungle-3d.zip; run npm install, npm test, and npm run dev.
Three.js and Vite
Render and develop locally.
Three.js 0.180.0 matches source; classroom Vite 7.3.6 replaces source 7.1.7 after verified development-server advisories. Installation needs internet.
Adult-operated AI or JR Playground
Brainstorm and review one bounded change at a time.
An adult operates the assistant; gameplay does not require an AI service or learner account.

Learn online

Six weekly 90-minute sessions: 10 minutes to predict, 15 to explain, 40 to build, 15 to test, and 10 to reflect.

Plan around 90 minutes per session; pause and revisit at your own pace.

Adult support: A facilitator prepares tools and operates AI through JR Playground or an adult-managed assistant. Learners make choices, edit, and verify; no personal AI account is required.

Build at camp

Five days with 180 planned minutes per day, including project work and group activities. The course outline does not reserve a camp place.

  1. Day 1: Day 1 — Brief and working model

    • Complete the first two lessons in paired studios.
    • Alternate driver and navigator and take a movement break between studios.
  2. Day 2: Day 2 — Controls

    • Players compare two control variants and report observations rather than visual preference.
    • Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
  3. Day 3: Day 3 — One meaningful feature

    • Act out the landing gate: only descending contact triggers the spring card.
    • Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
  4. Day 4: Day 4 — Failure detectives

    • Trade worlds and return one reproducible model observation plus one visual observation.
    • Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
  5. Day 5: Day 5 — Future Architects showcase

    • Host a World Architects gallery with playing, route-map, and design-question stations.
    • Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
Facilitator preparation
  • The same six outcomes apply online and at camp; additional camp studio time supplies practice, not extra required content.
  • Choose guided, independent, or stretch tasks by confidence. Ages 9–10 often pair with an adult; ages 11–13 own bounded changes; ages 14–16 can justify and test architecture choices.
  • Prepare starters before class. Keep family repositories and personal data out of student workspaces.

Show what you built

Deliver a small playable game for a chosen player, demonstrate a tested improvement, and explain its input, state, rules, output, and one design tradeoff.

Purpose
A brief names the player, loop, finish, and one idea left for later.
Working system
A fresh run reaches the intended finish; recovery and restart match the specification.
Evidence
A record contains normal, boundary, failure, and repeated-after-fix checks with device details.
Architect explanation
The learner explains a changed rule, a tradeoff, and how an AI suggestion was checked.

Portfolio theme: 3D World Architect

Use the rubric with a guardian or mentor and record your evidence in your builder notebook.

Build with care

  • Use fictional player names and original shapes; no child photos, contacts, passwords, or API keys belong in the starter.
  • An adult operates external AI and manages any public sharing; verify each suggested change with a prediction and check.
  • Take movement breaks and offer partner-operated controls when needed.

Inspired by our projects

Jelly Jungle 3D — astra-version
User-reported Astra-assisted creation; inspected source demonstrates Three.js geometry, fixed-step physics, procedural assets, and separate art responsibilities. No Astra runtime integration is claimed.