Cube Engine

Overview

Every cube in this world is drawn by the CPU, not the GPU. Cube Engine is Nurgak's HTML5 voxel sandbox, and its defining trick is that an entire three-dimensional block landscape is rendered onto a plain two-dimensional canvas with no WebGL, no OpenGL, and no hardware acceleration anywhere in the pipeline — just a painter's algorithm sorting faces from back to front while back-face, occlusion, and frustum culling try to keep up. It began as a proof of concept for software 3D in the browser, and the author is blunt in the README that it demands a powerful computer to feel fluid. The world itself is the familiar voxel fantasy: terrain built from 16 by 16 chunks, shaped by a two-dimensional Perlin noise generator that picks one height per chunk and interpolates the gaps, layering grass, dirt, sand, stone, and water as the altitude dictates. There are no mobs, no ores, no tunnels, no trees, and no physics — every spare cycle goes to the renderer, so what survives is pure construction. You place and remove nodes from a large palette of building materials and colored cloth, save the 3 by 3 chunks around you into five local slots or a file, and wander a map that effectively never ends. It appeals most to tinkerers and engine-curious players who want to watch software 3D happen one frame at a time.

How to Play

Move with WASD, rotate the camera with the Arrow keys (Up and Down pitch your view, clamped so you cannot flip over), tap Space to jump, and hold Page Up or Page Down to fly vertically through the world. Click the Lock pointer button if you would rather look around with the mouse. Left-click places a block of whichever material is selected in the Type dropdown — dirt, grass, glass, brick, sand, wood, water, snow, obsidian, cobweb, or any of sixteen cloth colors — and right-click removes the node you are aiming at. On touch screens a virtual joystick mirrors the arrow keys for movement. Start a fresh world by typing a numeric seed and pressing Generate, spawn into the terrain, and build outward from there.

Tips & Strategy

Lower the render-distance slider before anything else, because the software renderer is the single bottleneck and a smaller view is the only real source of performance headroom. Switch render mode from Textured to Plain color when you just want to travel or scout; affine texture mapping is visibly slower than flat-shaded cubes, and Chrome in particular stutters on heavy fill. Turn gravity and collision off while raising tall structures so you can position yourself with Page Up and Page Down and place blocks precisely without tumbling off your own scaffolding. Concentrate early building inside one chunk before you wander, since saving only persists the 3 by 3 grid of chunks around the player — anything raised two screens away will not survive a save-and-reload. Treat numeric seeds as shareable: a known seed reproduces a world exactly, which is handy for revisiting a layout. Toggle the performance graph with P to settle on a render-distance sweet spot before committing to a large build, and remember that flying (Page Up and Page Down) is faster and safer than walking once gravity is off.