Skip to content

Releases: AristurtleDev/monogame-aseprite

Version 6.0.5 Release

31 May 17:28
51cd582
Compare
Choose a tag to compare

Updates internal version of AsepriteDotNet used to 1.8.1

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

Version 6.0.4 Release

02 May 00:57
a80a694
Compare
Choose a tag to compare

What's Changed

New Contributors

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

Version 6.0.3

02 Apr 20:44
Compare
Choose a tag to compare

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

02 Apr 19:05
Compare
Choose a tag to compare

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

02 Apr 17:20
Compare
Choose a tag to compare

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

26 Mar 20:12
910574e
Compare
Choose a tag to compare

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

13 Mar 03:45
7469b3b
Compare
Choose a tag to compare

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

Version 5.1.2 Release

02 Dec 02:41
ce5f41a
Compare
Choose a tag to compare

This version brings the following changes

  • Resolves issue #93 where AsepriteFile.TryGetSlice always returned false even when slice exists

Verson 5.1.1 Release

28 Sep 01:01
3b3a3c0
Compare
Choose a tag to compare

This version brings the following changes

  • Resolved issue where using Linked Cels can cause an out of bounds exception.

Verson 5.1.0 Release

22 Aug 02:36
d3a8804
Compare
Choose a tag to compare

This version brings the following changes

  • AsepriteCel properties were made public (thanks @SephDB)
  • AnimatedSprite now supports setting frame both on initial play and during playback.