Version 6.1.0 Release

What's Changed

• Update AsepriteDotNet Version Used by @AristurtleDev in #110

Full Changelog: v6.0.7...v6.1.0

Version 6.0.7 Release

Updates to MonoGame 3.8.2.1105 and net8.0

Full Changelog: v6.0.6...v6.0.7

Version 6.0.6

Bumps internal version of AsepriteDotNet to 1.8.3

Full Changelog: v6.0.5...v6.0.6

Version 6.0.5 Release

Updates internal version of AsepriteDotNet used to 1.8.1

Full Changelog: v6.0.4...v6.0.5

Version 6.0.4 Release

What's Changed

• Add compatibility with FNA by @nobledemon in #106
• Update/asepritedotnet 1.8.0 by @AristurtleDev in #108

New Contributors

• @nobledemon made their first contribution in #106

Full Changelog: v6.0.2...v6.0.4

Version 6.0.3

Description

This updates the version of AsepriteDotNet to 1.7.4 to resolve a critical bug where the Tag Repeat count was not being set properly after the data was read.

Version 6.0.2

Description

This updates the dependency version of AsepriteDotNet to 1.7.3 to resolve a critical bug when processing slice key data.

Version 6.0.1

This release updates the dependency version of AsepriteDotNet used to AsepriteDotNet 1.7.2. This resolves a critical bug due to how Aseprite stores pixel data for a cel outside the bounds of a frame. If you select part of your image and move the pixels outside of the frame, the pixel data for the cel is still there even though its no longer visible or within the frame bounds. The method originally used to detect this was not sufficient enough, and has been adjusted to explicitly only process pixel data of a cel that is within the bounds of a frame, regardless of the cel size.

Version 6.0.0 Release

Version 6.0.0 Release

With this release, the entire processing core has been removed and is now using AsepriteDotNet to perform all of the file processing.

Creation of various types such as Sprite, Spritesheet, TextureAtlas, etc has been sightly adjusted. Please see the examples in the examples directory for information on usage until I can update documentation.

Version 5.1.3 Release

The following changes were implemented:

Updates from 5.1.3-beta-1

• Added MonoGame.Aseprite.Configuration
  • When set to false this will assume frame index gets from the AsepriteFile start at index 1 and not 0. This is so that the frame index you reference visually matches what the Aseprite UI shows for artists that are no programming zero-indexed savvy

Updates from 5.1.3-beta-2

• Removed MonoGame.Aserpite.Configuration
• Moved ZeroIndexedFrames to be property of AsepriteFile
• Added unit testing for AsepriteFile.ZeroIndexedFrames functionality

** Updates from 5.1.3-beta-3**

• Added proper support for new tile rotation introduced in Aseprite 1.3

5.1.3 update

• Fixed issue where Indexed mode would cause exception during load due to Aseprite 1.3.5 file spec change