FAQ & legal notes
Target API: 5 · Target build:
bbb6l5(2026-11-20, production and preprod) · Status: Verified
Frequently asked questions
Q. Are shader packs an official feature?
The shader-pack feature is accessible from the in-game UI and pack-making appears to be an intended activity. No public official documentation has been found, though — this guide is an unofficial, analysis-based document.
Q. Can packs do anything dangerous?
Packs are pure WGSL — JS execution and network access are impossible by design. Only code that passes validation and compilation runs (Restrictions).
Q. Which games do packs work in?
Most games run in strict mode (no vertex animation, no discard). Vertex animation works only in allow-listed games. The per-title list is in Engine Internals: policy.
Q. Do packs work on mobile?
Only on WebGPU-capable environments (Requirements).
Q. Can I ship my own textures?
Not in a shader pack (the atlas is read-only). That is the texture-pack system’s job (combinations).
Q. Can I keep using an old-version pack?
The current game accepts only apiVersion: 5; older packs are silently deactivated (Compatibility). Migrate via Version History.
Q. Will the API change again?
Engine internals may change with updates — every page names its target build. Saved packs re-validate automatically when the header or registry changes (Compatibility).
Q. What about “cinematic shader” distributions?
A community “cinematic shader” distribution we analyzed turned out to be a texture pack (128×128 textures, no pack.json / .wgsl). Most “shadowy shader-like” looks are texture-side craft (combinations).
Legal & notes
- This is an unofficial guide and does not represent the developers’ views. The API may change without notice
- Created with AI assistance; accuracy is not guaranteed. Verify against actual in-game behavior
- Measured values (texture ids etc.) are snapshots of specific builds and change between builds (names are the API)