# ULTIMATE REALITY SANDBOX — BUILD THE DREAM Build an extra...

Prompt

# ULTIMATE REALITY SANDBOX — BUILD THE DREAM Build an extraordinary interactive science sandbox where the player feels like they have been handed a miniature universe and can ask: **“WHAT IF…?”** Then discover the answer by experimentation. This is NOT a small demo, chemistry quiz, recipe game, crafting system, or fake visual simulator. The core philosophy is: **EMERGENCE > RECIPES** **EXPERIMENTATION > INSTRUCTIONS** **SYSTEMS > SCRIPTS** **CAUSALITY > VISUAL TRICKS** **DISCOVERY > ARBITRARY PROGRESSION** **PLAY > MEMORIZATION** Study and combine the strongest ideas from Alembic, The Powder Toy, falling-sand simulations, chemistry/lab simulators, physics sandboxes, engineering simulators, factory games, electronics simulators, fluid/thermal systems, molecular/material simulations and modern game UI. Go substantially beyond them. ## 1. USE EXISTING TECHNOLOGY Do NOT blindly reinvent excellent technology. Research mature legal/open-source/appropriate engines, libraries, datasets, simulation systems, rendering systems, UI frameworks, procedural systems and existing code. Reuse, integrate and improve strong foundations when appropriate. Do not copy proprietary code/assets. Choose whatever technology produces the best actual game: Web/HTML/WebGPU/JS/TS/WASM/C++/Godot/other engine/hybrid. Do not sacrifice the vision just to force HTML. **MAKE THE GAME.** ## 2. SCIENTIFIC REALISM Aim for scientifically grounded, internally consistent approximations. Do not pretend to simulate every particle or perfectly reproduce quantum mechanics. Use real scientific information wherever appropriate: all elements, atomic numbers/masses, isotopes, density, melting/boiling points, phases, heat capacity, conductivity, electronegativity, ionization energy, potentials, solubility, optical/magnetic/mechanical properties, compounds, reactions, energetics, gas behavior and material properties. Research facts instead of hallucinating them. When exact simulation is impossible, use a defensible approximation. Never present a simplified model as exact reality. ## 3. 118 ELEMENTS + MATTER Include **all 118 elements, Hydrogen → Oganesson**. Elements must have meaningful differences, not just different colors. The periodic table should be an interactive scientific tool. Let players inspect, hold, heat, cool, mix, electrify, compress, expose to radiation and otherwise experiment with materials. Matter should visibly behave: solid/liquid/gas, melting, freezing, boiling, evaporation, condensation, sublimation, deposition, thermal expansion, density changes, buoyancy, diffusion, dissolution, precipitation, crystallization, combustion, oxidation/reduction, corrosion, electrochemistry, phase separation, alloying, gas mixing and heat/electrical transfer. The player should OBSERVE phenomena rather than receiving “reaction occurred” messages. ## 4. EMERGENT CHEMISTRY Do not make chemistry merely: **A + B = C** Use underlying conditions wherever practical: temperature, pressure, concentration, phase, environment, contact/surface area, catalysts, redox conditions, energy, solubility, compatibility, equilibrium, reaction rate, activation barriers and available pathways. Use deterministic reaction data where scientifically necessary, but make the overall experience feel emergent and discoverable. Create a persistent scientific Codex/notebook recording discovered elements, compounds, reactions, phenomena, conditions, measurements and optional explanations. Do not spoil discoveries unnecessarily. ## 5. REAL LABORATORY Create functional laboratory equipment: beakers, flasks, test tubes, graduated containers, pipettes, droppers, funnels, thermometers, scales, pressure gauges, vacuum chambers, heaters/burners, crucibles, condensers, distillation equipment, electrodes, batteries, power supplies, wires, switches, pumps, valves, filters, mixers, centrifuges, grinders, presses, reaction vessels, storage, microscopes and spectroscopy-style analysis where practical. These are NOT decorations. Their physical behavior affects the simulation. ## 6. ONE CONNECTED PHYSICS SYSTEM Chemistry and physics must interact in the same world. ### Mechanics Gravity, acceleration, momentum, collision, friction, elasticity, mass, torque, rotation, structural failure, pressure forces, buoyancy. ### Thermodynamics Temperature, heat, conduction, convection, radiation, heat capacity, phase changes, thermal equilibrium, expansion, compression, energy conversion. ### Fluids Liquids, gases, pressure, flow, viscosity, density, buoyancy, pipes, pumps, valves, pressure vessels and turbulence-like behavior where practical. ### Electricity Voltage, current, resistance, capacitance, inductance where practical, electrical heating, conduction, batteries, generators, circuits, switches, motors and sensors. ### Magnetism Magnetic fields/materials, electromagnets, induction, motors, generators. ### Optics/Waves Light, reflection, refraction, absorption, emission, lenses, mirrors, color, wavelength behavior and sound/waves where practical. ### Nuclear Where technically feasible: isotopes, radioactive decay, alpha/beta/gamma radiation, neutrons, shielding, moderation, fission, chain reactions and radioactive heat. ## 7. MATERIAL SCIENCE Make materials behave like real materials, not blocks. Support metals, ceramics, glass, polymers, crystals, composites, powders, liquids, gases, semiconductors, conductors, insulators, magnetic and porous materials. Where practical materials can deform, fracture, break, melt, conduct, expand, contract, react, corrode, dissolve, crystallize and change phase. ## 8. ENGINEERING Let players build real machines: pumps, engines, turbines, generators, motors, compressors, heat exchangers, distillation columns, reactors, batteries, electrical grids, factories, automated laboratories, conveyors, furnaces, cooling systems, pressure systems and power plants. Machines must obey the same world. Energy comes from somewhere. Pressure matters. Heat must go somewhere. Structures can fail. Cooling can fail. Pipes can rupture. Machines can stop. Avoid magical behavior. ## 9. ELECTRONICS + ROBOTICS Make electronics deep: wires, switches, resistors, capacitors, inductive components, diodes, LEDs, transistors, sensors, logic gates, timers, motors, generators, batteries, power supplies, analog and digital signals. Allow construction of calculators, computers, control systems, scientific instruments and automated factories. Where feasible provide programmable controllers/computers. Robotics must use the SAME world: wheeled robots, robotic arms, cameras, sensors, actuators, autonomous systems and automated laboratories. Robots must physically interact with the actual environment. ## 10. MULTI-SCALE UNIVERSE Support coherent levels: **WORLD:** terrain, labs, factories, machines **MATERIAL:** solids, liquids, gases, powders, mixtures **CHEMICAL:** molecules, compounds, ions, reactions **MICRO:** structures/interactions **ATOMIC:** atoms/nuclei/electrons where practical Let the player zoom between scales and feel like they are investigating deeper layers of reality. Do not brute-force every particle everywhere. Use intelligent abstraction while preserving consistency. ## 11. INFINITE EXPERIMENTATION Do not design around a finite list of “things you can do.” Systems must combine: chemistry + electricity chemistry + heat chemistry + pressure electricity + magnetism heat + fluids fluids + machines machines + chemistry materials + engineering nuclear + heat sensors + robotics robotics + chemistry automation + factories energy + environment Everything appropriate should interact. Example emergent chain: **reaction → heat → phase change → pressure → rupture → escaping fluid → turbine → generator → electricity → pump → new material enters reactor → new reaction** The player should think: **“HOLY SHIT, I ACCIDENTALLY BUILT A MACHINE.”** That feeling is a primary goal. ## 12. PHYSICAL FAILURE Never replace physical failure with generic errors when the simulation can explain it. Overpressure → rupture Overheating → melting/failure Electrical overload → heating/failure Unstable chemistry → runaway behavior Weak structure → collapse Insufficient energy → machine stops Bad cooling → temperature rises Failures should teach through consequences. Never fake physics, chemistry or fluids just to create impressive screenshots. ## 13. PREMIUM VISUALS + UI The game must look exceptional. NOT: generic AI-slop UI, meaningless glowing blue panels, random gradients, fake scientific terminology, decorative graphs, fake quantum effects, random holograms or meaningless complexity. Every visual should have a purpose. Materials should look believable: fire like fire, steam like steam, water like water, molten materials hot, metals metallic, glass transparent, crystals distinct from powders, gases appropriately represented. Create a beautiful futuristic scientific laboratory with excellent typography, hierarchy, spacing, icons, transitions, controls, search, filtering, favorites, recent materials, Codex, measurement tools and live graphs. The interface should feel like a premium scientific instrument, not a corporate dashboard. ## 14. LIVE SCIENTIFIC DATA Let players inspect relevant quantities: temperature, pressure, mass, density, volume, velocity, energy, charge, current, voltage, concentration, composition, phase, conductivity and reaction state. Provide probes, measurements, live graphs and optional scientific overlays: temperature, pressure, velocity vectors, electric field, magnetic field, concentration, density, radiation, stress, heat flow, current flow and particle/molecule visualization. ## 15. MODES **PURE SANDBOX:** almost no guidance **LEARNING:** optional hints and explanations **CHALLENGE:** scientific objectives **EXPERIMENT:** structured experiments **ENGINEERING:** machine/system building **CREATIVE:** unlimited resources Challenges can involve batteries, mixture separation, distillation, purification, alloys, cooling loops, power generation, chemical plants, sensors and robots, but sandbox freedom must NEVER be restricted. ## 16. GAME FEEL It must still be a GAME. Pouring should feel satisfying. Heating should look satisfying. Breaking things should be spectacular. Building machines should feel rewarding. Discovery should create curiosity. Failure should often be interesting. Unexpected results should be exciting. Support pause, slow motion, normal speed, fast forward and frame stepping. Use dynamic audio for fluids, bubbling, pressure releases, electrical arcs, motors, pumps, impacts, steam and machinery. Use physically motivated VFX: sparks, smoke, steam, condensation, flames, glowing materials, dust, splashes, fragments, radiation visualization and electrical arcs. Effects should reinforce simulation rather than hide weak simulation. ## 17. SAVE + SCIENTIFIC HISTORY Save complete experiments including materials, positions, temperatures, pressures, machines, circuits, reactions, automation, environment and configuration. Reload as faithfully as possible. Maintain a scientific notebook of experiments, discoveries, materials, reactions, measurements, machines, successes and failures. ## 18. BIOLOGY / FUTURE EXPANSION Architect for future systems such as biology, cells, membranes, enzymes, metabolism, microorganisms, plants, ecosystems, geology, astronomy, advanced electronics, robotics and additional simulation scales. Future systems should integrate into the same world rather than becoming disconnected minigames. ## 19. PERFORMANCE WITHOUT KILLING DEPTH Expect massive complexity. Use adaptive resolution, multiple simulation levels, spatial partitioning, sleeping/inactive systems, selective high-detail simulation, GPU acceleration, background computation and other intelligent optimization. Do NOT solve performance problems by simply deleting the interesting systems. ## 20. DEVELOPMENT METHOD Do NOT write a giant pile of code and assume it works. Use: **BUILD → RUN → TEST → OBSERVE → CRITIQUE → FIX → IMPROVE → REPEAT** After every meaningful milestone: * actually run the game * interact with it * test normal use * test weird use * try to break it * inspect physics * inspect visuals * inspect UI * inspect performance * fix the largest weaknesses Test extreme temperatures, pressures, mixtures, tiny/huge quantities, long machine chains, feedback loops, electrical overloads, structural failures, unusual materials and strange geometries. Start with a compelling vertical slice, but build the architecture toward the complete vision. The first playable slice should demonstrate as much of this core as realistically possible: real materials, temperature, gravity, phases, fluids, chemistry, electricity, measurement, interaction, beautiful rendering, save/load and unrestricted experimentation. ## 21. PRIORITIES When forced to choose: 1. Simulation quality 2. Emergent interactions 3. Scientific plausibility 4. Player freedom 5. Visual quality 6. Usability 7. Performance 8. Content quantity 9. Progression 10. Cosmetic extras Prefer **50 deeply interconnected systems** over 5,000 disconnected buttons. ## 22. FINAL QUALITY BAR Do not stop at: “it compiles” “it launches” “there is a UI” “there are 118 buttons” “there are particles” “there are explosions” “there are recipes” The result should genuinely feel like: **“I HAVE BEEN GIVEN A TINY UNIVERSE AND I CAN EXPERIMENT WITH IT.”** Not a chemistry quiz. Not a recipe list. Not a collection of animations. A **PLAYABLE UNIVERSE OF INTERACTING RULES.** ## FINAL COMMAND Research strong existing foundations. Reuse excellent legal/appropriate technology. Build the core. Run it. Test it. Observe it. Improve it. Replace weak approaches. Optimize intelligently. Expand continuously. Use as much code as the project actually requires—even tens of thousands of lines—but **never chase line count instead of quality**. Do not merely describe what you would build. # BUILD IT. **BUILD → TEST → OBSERVE → ITERATE → EXPAND** Repeat until it genuinely feels extraordinary.

A system prompt was added to support web rendering