A native pack named by HORIZON_SHADER_PACK (a folder with horizon-shaders.toml or a .hshader in shaderpacks/) is checked, then its post passes run over the world's own target, the one a shaders/ pack reads: no second target and no extra pass, and without a pack the frame only tests one Option. The pack is looked at twice a second; a saved file is checked and rebuilt in place, and a version that fails is refused in the chat while the last good one keeps drawing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6.4 KiB
Horizon shader packs
Horizon has its own shader packs: WGSL written against stages of Horizon's renderer, checked before they run. This page is the guide for pack authors. The design and the pack format are in api/shaders.md; every stage's signature, input, resource and limit is in the generated api/shaders-reference.md.
Shader packs in the Iris/OptiFine format are a separate feature with its own loader; this page is only about Horizon's own format.
| Part | Where | State |
|---|---|---|
| Format, stages, check | crates/horizon-shader-api |
API 0.1, experimental |
| Authoring tool | horizon-shader (same crate) |
new, check, pack |
| Templates | crates/horizon-shader-api/templates/ |
post, sky, material |
| Example pack | crates/horizon-shader-api/packs/golden_hour |
a warm sky and two post passes |
| In the game: the post stage | HORIZON_SHADER_PACK=<name> (for development, until the Shader Packs page) |
post passes, hot reload |
| In the game: sky and material; the launcher and the registry | not yet |
Quick start
cargo install --path crates/horizon-shader-api # or: cargo run -p horizon-shader-api --bin horizon-shader -- <command>
horizon-shader new my_pack --template post # also: --template sky, --template material; --name "My Pack"
horizon-shader check my_pack # what the game, the launcher and the registry will check
horizon-shader pack my_pack # check, then write my_pack-0.1.0.hshader beside the folder
check prints each stage with its cost, and the pack's SHA-256:
golden_hour 1.0.0 (shader API 0.1): ok
sky Warm horizon 99 expressions, 0 texture reads
post Glow 192 expressions, 3 texture reads
post Colour grade 201 expressions, 2 texture reads
sha256 b5e0d98c...
or every problem, at its file, line and column:
my_pack 0.1.0 (shader API 0.1): FAILED
post.wgsl:9:1: expected `;`, found "}"
--json prints the same for tools (ok, id, version, api, sha256, stages, problems).
Trying a pack in the game
Until the Shader Packs page lists them, put the pack folder (or its .hshader) in shaderpacks/ beside options.txt
and start the game with HORIZON_SHADER_PACK=<its folder or file name>. The game checks the pack first, and refuses
one that fails, with its problems in the chat. While it runs, the game looks at the pack twice a second: save a file
and the pack is checked and rebuilt in place ("Shader pack ... reloaded"); if the new version fails, the chat says
where and the last good version keeps drawing. The post passes run today; the sky and material stages are checked
but not drawn yet.
A pack
A folder (or the same files zipped as a .hshader) with horizon-shaders.toml and WGSL files:
schema = 1
id = "my_pack"
name = "My Pack"
version = "0.1.0"
api = "0.1"
[[post]]
file = "post.wgsl"
[[options]]
id = "saturation"
name = "Saturation"
type = "float"
default = 1.15
min = 0.0
max = 2.0
Every key is in api/shaders.md.
Stages
A stage is one function your file defines. Horizon puts its prelude (the structs, frame, the stage's resources and
helpers) before your file and calls the function from its own pass, so the world is still culled, batched and meshed
by Horizon: a pack changes how things look, not how they are drawn.
| Stage | Your function | What it does |
|---|---|---|
[sky] |
fn sky(input: SkyInput) -> vec4<f32> |
the sky's colour along each view ray; the sun, moon, stars and clouds are drawn over it |
[material] |
fn material(input: MaterialInput) -> Surface |
the lit colour of each point of a block's surface, before the alpha test and fog |
[[post]] |
fn post(input: PostInput) -> vec4<f32> |
a full-screen pass over the world's picture (up to 8, in order), under the hand and HUD |
A pack has at least one stage; a stage it leaves out keeps vanilla's look. Each input says what vanilla would draw
(input.color in the sky and post stages; albedo * tint * vec4(lightmap, 1.0) for a material), so a pack can start
from vanilla and change only what it means to.
Every stage can read frame: the camera's matrices and position, the sun and moon directions, the time of day,
vanilla's sky and fog colours, rain and thunder, fog distances, the light at the camera, effects and the dimension.
Post passes also read scene_color, scene_depth, previous (the last pass's output), two samplers and the helpers
depth_at(uv) and view_position(uv, depth).
Rules the check enforces: your files declare no bindings (@group/@binding), no entry points and no names starting
with horizon_. Code shared by several stages goes in files listed in shared, put before every stage.
Options
Each [[options]] entry is a WGSL override of the same name, set when the game builds the pipeline: no text
substitution, no recompiling a different program per value.
override saturation: f32 = 1.15; // type = "float"; bool → bool, int → i32, choice → u32 (the value's index)
The game shows the options on the pack's settings screen. Branches on an option are on a constant, so the GPU skips the side that isn't taken.
What the check does
The game runs the same check when it loads a pack (a pack that fails is refused with the message, and the last good one keeps drawing), the launcher before it installs one, and the registry's CI before a pack is listed:
- The manifest and the package: known keys, valid ids, every file used, sizes.
- Each stage built as the renderer builds it and validated by naga.
- The stage function's signature, and the rules above.
- Each
overridematches its option's type (or has a default); each option is used. - Budgets: 20 000 expressions and 64 texture reads per stage.
- Every entry point translated for Vulkan (SPIR-V), Metal and DirectX 12 (HLSL), with the options at their defaults, minimums and maximums.
[budget] gpu_ms is the GPU time your pack aims to add to a frame; the game's overlay will show each pass's time
against it.
Next
The renderer hooks (shared with the Iris/OptiFine loader), then the post stage in the game with hot reload and the
GPU time per pass, Options > Shader packs listing these packs, then the material and sky stages, and the registry's
shader kind with installs from the launcher.