Releases: AristurtleDev/monogame-aseprite
v6.3.0
Contributors
Assets 2
v6.2.0 Release
What's Changed
- Update to use MonoGame 3.8.3 by @AristurtleDev in #114
Full Changelog: v6.1.0...v6.2.0
Contributors
Assets 4
Version 6.1.0 Release
What's Changed
- Update AsepriteDotNet Version Used by @AristurtleDev in #110
Full Changelog: v6.0.7...v6.1.0
Contributors
Assets 2
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
Contributors
Assets 2
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.