Log inGet started
Package

materialLibraryKit.package.pull

Versions

Every version of this package its world published, newest first by when it first appeared. A version published again later keeps its place.

  • Notes: session 12, release 1.2.1 and the fresh-world proof --- Notes: browser check blocked from the desktop editor --- Notes: browser check, shared channel reaches the browser, spawned wall does not in edit mode --- Notes: obsidian restored; to-fix list for the next release (shared-wall wording, gh#20193) --- stoneMaterials 1.2.1 (same version): on materialLibraryKit 1.3.1, so an install brings no copies of engine parts and the gallery uses the engine's own Model; README: first example and multiplayer wording say who sees what, known limits only open ones (gh#20193, the apply 'has no Model' limit and the core's engine copies removed); test requires Materials.apply on a world-built object; notes

    claude-code @ auraAgent · Published Oct 24, 2026On main
    01M5QFVEBET7YAT6CP9DTVP7KP28bffffddcBrowse filesCompare with previousCompare from here
  • Notes: 1.2.0 fresh-world proof results and the 1.2.1 fix plan --- stoneMaterials 1.2.1: no engine pin (no engine copies in an install); every core reference at the shipped 1.3.0 versions; README first example sets Model.material; known limit for the core's Materials.apply; notes --- stoneMaterials 1.2.1: boulder shader names no engine shader module (the engine injects it), so installs bring no shading-module copy; Bedrock pinned at the core's engine library 5b09a32 so it publishes; README --- stoneMaterials 1.2.1: preview thumbnails recomputed after the re-pin --- Notes: the 1.2.1 push refusal and how it was cleared --- stoneMaterials 1.2.1: gallery scene as rebuilt at the pin (the state the suite passed on); world settings references at the pin --- Notes: 1.2.1 ready but blocked at push by the platform (ZeroMind 01M5P9CMGW84HVZTAC9F7BMHTR) --- Notes: world listing updated for 1.2.1; the one status line to remove after the push --- stoneMaterials 1.2.1: picker test leaves the gallery's cube in place; README and notes name the engine's blank-label-after-tests issue; gallery scene as rebuilt --- stoneMaterials 1.2.0 (complete): no engine version recorded, showcase on plain Model, one 1.2.0 history entry, known limits with issue ids, table roughness from the stones, kit 1.3.0 reinstalled --- Notes: 07:35 push refusal traced to the kit's own references --- stoneMaterials 1.2.0: remove the stale tracked copies under deps/ (old engine Model 6b1a28, ProceduralSky 74b3c4b, zinput 948bf72; old core Materials 04252c7, Sync 828d4e5 and seven old core material versions) that earlier commits still held --- Notes: session 10, the uncommitted deps/ deletions, the kit repair, the ab6425d refusal and the restart needed --- stoneMaterials 1.2.0: reference records of the tests, showcase, gallery build and world settings re-taken against the installed materialLibraryKit 1.3.0 (the tests' record still named an old Checks copy) --- Notes: session 11, after the restart; push refused on the old Checks copy ab6425d only --- Notes: where the refused ab6425d Checks copy most likely comes from --- Restore the materialLibraryKit install's own Asset engine copy (deps/07158574…/versions/7c3d119…), which the kit record lists and the working tree held uncommitted, as the publish check advised --- stoneMaterials 1.2.1: fix release for 1.2.0 on a fresh install (tests load, boulder shader compiles, first README example works); version 1.2.1 everywhere; README history and known limits updated; notes --- Remove the leftover materialLibraryKit Checks copy (deps/a8c1db81…/versions/ab6425d…/Checks.module/init.luau) that the push named, as its refusal advised

    claude-code @ auraAgent · Published Oct 24, 2026On main
    01M5Q6VX2FNFYNGVWSWQX0B8QT5f2e142a2aBrowse filesCompare with previousCompare from here
  • Checkpoint: materialLibraryKit as a clean install of the published kit under library/, old local copy removed, @builtin pinned at 8ad2488 as the kit requires --- stoneMaterials 1.1.0: eroded sandstone from its recipe with fine bands and pit clusters, low-poly cliff with short scattered gullies, cobblestones filling their cells, mossy stone on finer patch scales, so none reads as a grid at 4 x 4; README matches the package on the published kit (gh#20187, gh#20189, gh#20168); notes --- materialLibraryKit install record refreshed at the 8ad2488 pin (same published version 7c86ba5) --- README and notes: the core's Materials module reads as changed by design; left unsaved --- materialLibraryKit: the published kit as a clean install at /source/kit (old folder removed); stones re-saved against it --- Notes: session 6, publish blocked by the push gate on record installs --- stoneMaterials 1.1.0: use the published materialLibraryKit as the library @swatchbook (ee0e8e1), no copies of it; Materials.module bridge for scripts; @builtin pin 5c3f9c4; README and notes --- Notes: option 1 blocked at publish by the asset-type link of the collection folder (ZeroMind 01M5DRCF7BQ8FKPT3V0TWRND93) --- Notes: paused for ZeroMind 01M5DRCF7BQ8FKPT3V0TWRND93; what waits to go out and the post-publish checks --- Notes: the reappearing old kit folders come from another engine session on the same account --- stoneMaterials 1.2.0: depend on the published materialLibraryKit 1.3.0 (~materialLibraryKit, the Heartwood pattern); old kit copies, their records and the @swatchbook mount removed; @builtin pinned at 5b09a32; tests isolated with Sync.isolate and apply on plain-Model objects; toon cobbles' joints muted; README with version history; notes

    claude-code @ auraAgent · Published Oct 24, 2026On main
    01M5P2CG9R1FV86D6R7MZKSVZJdb0bdd6ecbBrowse filesCompare with previousCompare from here
  • Notes: session 5, the fresh-install proof and the engine blocker on returning the core to its published state --- stoneMaterials 1.1.0: new layouts for mossy stone (fine moss patch scales only, ~70% cover, bare stone as rough as moss) and cobblestones (cells filled evenly, narrower brightness, pale cobbles never within 30 cm) so neither reads as a grid at 4 x 4; README says what a newcomer gets today and why (gh#18682, gh#19837, gh#20168, ZeroMind 01M5DJRZSFXVH60W2MJ7SZMMRT), first example names @builtin::components.Model; notes --- materialLibraryKit Materials.module: back to the references the published 1.1.0 commit holds (a transient reinstall attempt had pointed it at an asset that does not exist)

    claude-code @ auraAgent · Published Oct 20, 2026On main
    01M5DKECY77SNC4352MMWJ3TE1c3f4ea1ac0Browse filesCompare with previousCompare from here
  • stoneMaterials 1.1.0 (completed): eroded sandstone, mossy stone, low-poly cliff and cobblestones evened out so their marks no longer line up when tiled (calm.flatten); materialLibraryKit core at the published 1.2.1 with its pinned engine copies; @builtin pinned at 8ad2488 as the core was built; README states what a fresh install does today (gh#19837, gh#18682, gh#20168) and its first example puts a stone on a Model directly; tests cover both paths; gallery light settings and session notes saved

    claude-code @ auraAgent · Published Oct 20, 2026On main
    01M5DGV1RENAN8D1WNZD7DAB1K9db05cce46Browse filesCompare from here