Skip to content

Pixelbolt v0.9.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 18 Oct 14:47
· 49 commits to main since this release
v0.9.0
2c180d6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.9.0

Fluid effects. A new source format, pixelforge-fluid, runs a small fluid simulation and bakes every frame into palette pixels: smoke, fire, steam, explosions, magic swirls, splashes, waterfalls, drips and a bubbling potion. The result is an ordinary editable recipe, so it inspects, patches and exports like any other, and it never uses a colour outside the palette. Loops are seamless, and the same source gives the same pixels on every machine and in the browser.

  • Liquids can throw spray and foam off the water by their own motion (whitewater), and an emitter can fade toward its rim (falloff) or orbit in an ellipse.
  • Ten presets in examples/*.fluid.json, polished after an art review; each compiles in well under a second.
  • pixelbolt compile, preview and sequence accept fluid sources; MCP pixel_compile compiles them, and pixel_help with topic: "fluid" returns the schema.
  • The studio's Fluid lab (/fluid.html) tunes a preset in the browser and downloads the GIF, sprite sheet, recipe or source.
  • The guide is the "Fluid effects" section of docs/art-workflow.md; the full list of changes is in CHANGELOG.md.

The bundle keeps its 0.8.0 name, pixelbolt.mcpb (checksum pixelbolt.mcpb.sha256). The pixelforge command still works as an alias.

pixelbolt.mcpb contains the local Node.js MCP server, its eight tools, schemas and authoring help. The server makes no network requests.

Download pixelbolt.mcpb and open it in Claude Desktop, or use Settings -> Extensions -> install from file. Choose a workspace for recipes and generated artwork, then ask the agent to call pixel_help. The bundle uses the client's Node.js runtime (20 or newer); it does not include Node.js.

Download pixelbolt.mcpb.sha256 beside the bundle to check its SHA-256:

sha256sum --check pixelbolt.mcpb.sha256
gh attestation verify pixelbolt.mcpb --repo skulitom/Pixelbolt --signer-workflow skulitom/Pixelbolt/.github/workflows/release.yml

On PowerShell, (Get-FileHash pixelbolt.mcpb -Algorithm SHA256).Hash should match the hash in the checksum file.

The GitHub release makes the bundle available immediately. MCP Registry publication is a separate, manually dispatched step after testing; see Publishing.

What's Changed

  • [compass] Remove dead code: unreachable definitions in the poses, autotile and fx schemas by @skulitom in #14
  • [compass] Every product easy to find and understand on GitHub: Pixelbolt's top block, translations, llms.txt and tool descriptions by @skulitom in #15
  • [compass] Docs: link the dated pixel art and sprite MCP server comparison by @skulitom in #16
  • [compass] Clean up tests: cheaper pixel comparisons in the GIF and scene shot tests by @skulitom in #17
  • [compass] Pixelbolt 0.9.0: fluid effects released everywhere Pixelbolt is listed by @skulitom in #18
  • [compass] Pixelbolt 0.9.0: fluid effects released everywhere Pixelbolt is listed (re-cut) by @skulitom in #19

Full Changelog: v0.8.0...v0.9.0

Contributors

skulitom
Assets 4
Loading