pixelkiln 0.53.3 → 0.53.4

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.
package/docs/TILES.md CHANGED
@@ -172,14 +172,27 @@ shape dependency.
172
172
  The texture path is relative to the `.tres`, so the generated PNG and resource
173
173
  can move together inside a Godot project.
174
174
 
175
+ **`terrain`-generator tiles are always square, never isometric.**
176
+ `/create-tileset` places tiles on a rectangular vertex grid (its own docs: "a
177
+ map of W×H cells has (W+1)×(H+1) vertices" — standard square Wang-tiling
178
+ math, with no shape parameter at all, unlike `create-tiles-pro`'s `tile_type`
179
+ enum), and its raw output is fully opaque with no diamond alpha mask,
180
+ confirmed against a downstream consumer's real generated tiles. `terrain`'s
181
+ resolved spec always carries `tileType: "square_topdown"` for exactly this
182
+ reason, so the exporter never falls back to `tiles`' own "isometric" default
183
+ (the real API default for that generator, not terrain's) for a terrain
184
+ asset. The isometric corner-name mapping above is real and does apply — to
185
+ an isometric `tiles`-generator tileset (`tileFeature: "tileset"` with
186
+ `tileType: "isometric"`), not to `terrain`.
187
+
175
188
  Both this `TileSet` and the `SpriteFrames` that `pack --format godot` writes
176
189
  are loaded by a headless Godot 4.7.2 in CI (`npm run test:godot`), which
177
190
  reports the atlas tiles, terrain sets and names, animation names, frame
178
- counts, speeds, and loop flags it sees, and — for both a square and an
179
- isometric terrain set — round-trips an actual peering bit through Godot's
180
- own `get_terrain_peering_bit()` rather than only checking tile/terrain-set
181
- counts. That last check is what would have caught this bug; the counts alone
182
- did not.
191
+ counts, speeds, and loop flags it sees, and — for both a square terrain
192
+ tileset and an isometric `tiles` tileset — round-trips an actual peering bit
193
+ through Godot's own `get_terrain_peering_bit()` rather than only checking
194
+ tile/terrain-set counts. That last check is what would have caught the
195
+ isometric-corner-names bug; the counts alone did not.
183
196
 
184
197
  ## Deliberate limits
185
198
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pixelkiln",
3
- "version": "0.53.3",
3
+ "version": "0.53.4",
4
4
  "description": "Manifest-driven pixel-art generation, review, recovery, and packaging with deterministic provenance.",
5
5
  "type": "module",
6
6
  "sideEffects": false,