LIGHT. MATH. YOUR NEXT BUILD.

Configuration, palettes, and cameras

Start with the selected kit's config.json. Each shader has its own supported controls and ranges; settings are not interchangeable across the entire library.

Shared settings

colors is a three-color palette. speed controls motion where supported. paused stops animation. globalPointer controls supported interaction outside the local preview. Render budgets include maxPixels and maxFPS.

Camera settings include cameraZoom, cameraRotation, cameraX, and cameraY where supported. Some scenes support additional camera tilt. Fur's preview zoom is intentionally fixed for its performance budget. Consult the current shader reference before setting ranges.

background.update({
  colors: ['#08060e', '#8b35ff', '#ff35dd'],
  cameraZoom: 1.2,
  cameraRotation: -15,
  cameraX: 0.1,
  cameraY: 0,
});

These are integration examples, not a promise that every camera field is editable for every shader. Preserve the values from your selected export when a control is locked.

Presets and reproducibility

Presets are named starting configurations. Randomize can change the palette, pattern, and supported camera settings. Keep the generated configuration or seed when you need to reproduce a result.

The website may curate a smaller preset picker than the underlying catalog. For example, Event Horizon's website picker contains Accretion Fire, Monochrome, and Blue Shift. Existing saved configurations remain supported.

Photos and overlays

Supported website editors can integrate an uploaded image or an image overlay. Treat remote URLs as ongoing dependencies; embedded exports include image data in the exported files. Check your rights to any uploaded image before distributing a kit containing it.

The initial Striktly MCP configuration tools do not accept uploaded or remote images. Use the website editor for those options.