pixelkiln 0.55.0 → 0.56.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -310,7 +310,12 @@ every direction on disk.
310
310
  current URLs first.
311
311
  - `pixelkiln gallery` shows the family: states under their base, loops with
312
312
  their direction, mirrors with their source; see
313
- [`gallery`](./CLI.md#gallery).
313
+ [`gallery`](./CLI.md#gallery). With `--edit`, a base or state's drawer
314
+ offers "+ New state" and "+ New animation" under **Character**, the same
315
+ manifest-only write "+ New revision" does — nothing is spent until the
316
+ new entry is generated, and `plan` reports it `blocked` until its parent
317
+ is downloaded, same as one added by hand. `objectPro` families get the
318
+ same two buttons; see [`objectPro`](./GENERATORS.md#objectpro).
314
319
  - `pack --format godot` and `--format aseprite` write each direction as a
315
320
  still and each loop as a looping set at its fps; see
316
321
  [engine formats](./ARTIFACTS.md).
@@ -236,6 +236,11 @@ ignored, since none of them reach the API for an object.
236
236
  the object endpoint has its own `replace_existing` flag, so PixelKiln
237
237
  always passes it rather than fetching the object first to find and delete
238
238
  a prior take (`character`'s own workaround for not having one).
239
+ - `pixelkiln gallery --edit` shows an `objectPro` family the same way it
240
+ shows a cast — states under their base, loops with their direction — and
241
+ a base or state's drawer offers "+ New state" and "+ New animation",
242
+ restricted to the fields above (no `template`/`subject`, since neither
243
+ applies). See [Working with a cast](./CHARACTERS.md#working-with-a-cast).
239
244
 
240
245
  **Cost is not independently measured.** `objectProCost()` assumes
241
246
  `/create-object-pro-flash`/its state/its animation price identically to
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pixelkiln",
3
- "version": "0.55.0",
3
+ "version": "0.56.0",
4
4
  "description": "Manifest-driven pixel-art generation, review, recovery, and packaging with deterministic provenance.",
5
5
  "type": "module",
6
6
  "sideEffects": false,
@@ -150,7 +150,13 @@ identically to `character` pro-flash's own measured formula
150
150
  `template_id`; treat it as a working assumption pending a live check.
151
151
  Batch "pack" generation (PixelLab's Object Creator can make N distinct
152
152
  objects from one call) and `objectPro`'s own place in `pixelkiln adopt` are
153
- not modeled yet.
153
+ not modeled yet. `pixelkiln gallery --edit` offers "+ New state" and
154
+ "+ New animation" on a `character` or `objectPro` base/state's drawer, same
155
+ family, same manifest-only write "+ New revision" does — it writes the
156
+ `asset.state`/`asset.animation` fields above (minus `startFrame`/`endFrame`
157
+ and template `outline`/`shading`/`detail`, which need a manifest-relative
158
+ image the gallery does not offer) and leaves generation to `gen` or the
159
+ page's own budget, same as any other added asset.
154
160
 
155
161
  `isometricTile` wraps a *third*, separate path to isometric content:
156
162
  `/create-isometric-tile`, distinct from both `tiles`' own `tileType: