Silicon Shader

Find and share Minecraft Java shader setups for Apple Silicon. Browse screenshots and measured results, then let your agent adapt a compatible recipe to your Mac, launcher and mods.

Browse setups · Give your agent the prompt · Share a setup

Get started

Give the starter prompt to Codex, Claude Code or another coding agent with shell access. It detects your hardware and game, compares suitable recipes, and tries changes in a separate copy with rollback. Automatic play needs an agent with working game controls; shell access alone cannot drive Minecraft. A game already in use is left alone. Your current image quality is the starting point. Sharing is optional.

Prefer the CLI? You need Python 3.10+ and your own Minecraft Java installation. There are no Python runtime dependencies or API keys.

git clone https://github.com/fortunexbt/minecraft-apple-silicon-framework.git
cd minecraft-apple-silicon-framework
python3 -m venv .venv
. .venv/bin/activate
python -m pip install .
silicon-shader discover
silicon-shader challenge find --this-mac

Continue with try a setup. Prism has the most direct integration; other launchers use an explicit game directory. The agent skill ships with the CLI and can also be read directly—installation into your agent is optional.

Choose a setup that fits

New challenge submissions use one shared seeded world and scripted flight: one baseline and one candidate flight, about 21 seconds each after warm-up, targeting a repeat comparison under five minutes. One fixed front-facing portrait is taken afterward. Earlier-route recipes remain separate.

Each submission has a screenshot, Minecraft skin, hardware, game/mod versions, resolution, view distance, FPS/frame pacing and a reproducible recipe. Filter by Mac and compare the visual tradeoffs before choosing the highest FPS. There is no universal winner.

The first M4 Wide View recipe includes its exact configuration, patches, route and observed limitations. The hardware inventory covers released Apple Silicon Macs; an inventory entry does not mean that machine has been benchmarked.

What the toolkit does

Configuration writes require an isolated managed copy. The CLI does not launch Minecraft, install arbitrary mods, or upload anything during tuning. External launchers retain control of Java and launch arguments. Unsupported settings need explicit adaptation.

Measurements use CPU frame production, not displayed or generated FPS. The optional sampler needs a confirmed hook for the Minecraft version. A copied setup is only gameplay-checked after a normal launch. How to compare results.

Work on the project

• silicon_shader/ — CLI, configuration adapters and bundled agent skill.
• recipes/ — reproducible shared setups; contributions/ — accepted measurement bundles.
• site/ — static community library; sampler/ — optional Java capture agent.
• docs/ — player guides; docs/reference/ — capture and submission contracts.
• examples/, patches/, evidence/ — input templates, correctness fixes and historical research.

Read AGENTS.md before editing. Run python3 -m unittest discover -s tests -v; sampler changes also run ./sampler/smoke.sh. Keep recipe/code improvements separate from evidence submissions. Preserve existing worlds and configurations.

The repository is the source of the website and accepted submissions. The index is generated, not edited by hand. Preview or host it anywhere:

python3 -m silicon_shader.registry contributions site/data.json
python3 -m http.server 8000 --directory site

Validated current-workload data-only submissions merge and publish automatically; recipe/tool changes still need review. Entries remain self-reported, not certified performance. No database or private backend is required. Historical campaign notes remain in the experiment digest and evidence/.

Original code is MIT licensed. See third-party attribution for mods, shaders and textures. Independent community project; not affiliated with Apple or Prism.

NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED BY OR ASSOCIATED WITH MOJANG OR MICROSOFT.