Add support for Tilesets and Tilemap layers. #11
Conversation
These features are new in Aseprite 1.3, and with this in place, then `.aseprite` becomes a viable format for making 2D game maps that get loaded in the browser after being parsed by this library.
Aseprite.js
Outdated
| bitmaskForXFlip, | ||
| bitmaskForYFlip, | ||
| bitmaskFor90CWRotation }; | ||
| return { ...chunkInfo, tilemapMetadata, rawCelData }; |
There was a problem hiding this comment.
Same as the comment in readImageCelChunk.
Aseprite.js
Outdated
| @@ -349,6 +402,7 @@ class Aseprite { | |||
| }) } | |||
| }), | |||
| palette: this.palette, | |||
| tileset: this.tileset, | |||
There was a problem hiding this comment.
This should be tilesets: this.tilesets,
Aseprite.js
Outdated
| this.layers.push({ flags, | ||
| type, | ||
| layerChildLevel, | ||
| blendMode, | ||
| opacity, | ||
| name}); | ||
| name, | ||
| tilesetIndex}); |
There was a problem hiding this comment.
I'm not a fan of adding a property that could be undefined.
We could create an object at the top of this function and then add each property in it instead of creating variables and resolve it that way.
|
FYI I've also finished testing the work of using these changes to load tileset/tilemap data into a WebGL renderer. The aseprite data is loading properly with no issues - I'm just working through other issues downstream in the renderer before I commit my work up for others to see. |
|
Looks like you'll have to resolve the conflicts in your branch. Should be fairly easy if you merge the Once that's done, I'll merge it and start a new release for NPM. Thanks again for your work. |
|
I think I've resolved the conflicts correctly, but please give it another check to be sure. |
|
I'll re-review it tonight and then merge it in. Thanks again for the work and sorry for the delay 😅 |
These features are new in Aseprite 1.3, and with this
in place, then
.asepritebecomes a viable format formaking 2D game maps that get loaded in the browser
after being parsed by this library.