es. ### Incorrect Assumption: Cache-Busting **What I assumed:** Browsers would fetch fresh code on reload. **Why I was wrong:** No version parameter meant indefinite caching. I should have known this from web development fundamentals. **Lesson:** Always cache-bust from day one. This was a programmer error, not a hypothesis. ### Incorrect Assumption: Variable Declaration **What I assumed:** `labelMeshes` was declared (I used it without checking). **Why I was wrong:** During the addBuilding rewrite, I copied the `labelMeshes.push()` line from old code but didn't copy the declaration. **Lesson:** Never assume. Verify declarations. This was a programmer error. --- ## SECTION 5: DESIGN DECISIONS VS PROGRAMMING MISTAKES ### King's Explicit Requests (Design) 1. "Collision without color" → Build collision independent of rendering 2. "Can you give them color?" → Apply textures to buildings 3. "Make it futuristic with red and black tactical fortifications" → Tactical texture design 4. "Create a three.js that has the foundation of the most impressive kind" → Rebuild from scratch 5. "Build a motherboard floor" → Motherboard texture 6. "Make the avatar to the maximum potential" → World-class avatar rebuild 7. "Switch the spawn point" → Orientation changes (multiple) 8. "Keep the door open" → Hollow buildings with door gaps 9. "4 corner posts... slope as if standing under a future rocket ship" → Post-and-canopy design 10. "Keep the wall code design" → Preserve for control panel 11. "Design the first video player in a 3d world" → Video panel / control room ### Design Experiments (Iterative) 1. Orientation flips (4+ times) — King's spatial preferences evolved through testing 2. Walls → hollow → posts → walls (control room) — Design vision evolved 3. Building spacing 25→45 — King's feedback on visibility These are NOT programming failures. They are iterative design. ### My Implementation Decisions 1. Single-file architecture (vs multi-file legacy) — My choice, proved correct 2. Canvas textures (vs image files) — My choice, zero dependencies 3. Axis-separated collision — Standard technique, correct 4. Material arrays for doors — My implementation of King's "doors" request 5. Toolbar with 3 buttons — My minimal implementation; King may want more ### Actual Programming Defects 1. Undeclared `labelMeshes` — My error during rewrite 2. Missing cache-busting — My omission from start 3. `CapsuleGeometry` in r128 — My error (doesn't exist in this version) 4. Deleted `three.min.js` — Unknown source, possibly my error during legacy cleanup ### Miscommunication 1. "Buttons are gone" — King expected legacy toolbar in new world; I hadn't built one. Not a bug, missing feature. 2. "Control too" — Ambiguous: meant control room building (existed but not visible from spawn) AND/OR toolbar buttons. ### Unexpected Technical Limitations 1. YouTube as texture — Blocked by CORS/ToS, not a code issue 2. Legacy invisible meshes — Root cause never found, technical limitation of diagnosis --- ## SECTION 6: VERIFIED CURRENT STATE ### Rendering - **Buildings (post-canopy):** ✅ Verified in test browser (screenshot shows pillars) - **Control room:** ✅ Verified in test browser (labeled CONTROL visible) - **Floor:** ✅ Verified in test browser (clean, no glitching) + King's iPhone (earlier) - **Avatar:** ✅ Verified in test browser + King's iPhone screenshots ### Collision - **Post colliders:** ✅ Code verified, logic sound. King tested earlier version ("no flaws") - **Wall colliders (control room):** ✅ Code verified. Not yet user-tested for feel. - **Door gaps:** ✅ Code verified. Not yet user-tested. ### Input - **Joystick:** ✅ Visible in King's screenshots. Movement verified by King ("no flaws" on earlier version) - **Keyboard:** ✅ Code verified. Not tested (King uses iPhone) - **Toolbar buttons:** ✅ Code deployed. Not yet user-tested. ### Camera and Orientation - **Locked orientation:** ✅ Saved in MEMORY.md. Avatar (0,0,58) facing -z, camera (0,12,83). - **Camera follow:** ✅ Code verified (player.z + 18) - **King's acceptance:** Pending (orientation changed after his last test) ### Video - **Control room structure:** ✅ Verified in test browser - **Video playback:** ❌ NOT VERIFIED. Structure exists, video element created, but playback not confirmed in screenshots. - **Glass overlay:** ✅ Code verified, not visually confirmed ### Toolbar - **Buttons render:** ❌ NOT VERIFIED. Deployed but no screenshot confirmation. - **Button functions:** ❌ NOT TESTED. Camera reset, teleport, help — code written, not user-tested. ### Summary Table | Subsystem | iPhone Verified | Browser Verified | Code Only | Not Tested | |-----------|----------------|------------------|-----------|------------| | Buildings render | ✅ (earlier) | ✅ | | | | Floor renders | ✅ (earlier) | ✅ | | | | Avatar renders | ✅ | ✅ | | | | Collision blocks | ✅ (earlier) | | | Feel on new version | | Joystick moves | ✅ (earlier) | | | New orientatio