Appearance
Known bugs
This list was reviewed against the code on 2026-10-03. The bug IDs are kept for tracking.
Medium
| ID | Issue | Details |
|---|---|---|
| BUG-014 | Different input folders can produce the same exported asset name. | Collisions affect selection, animation groups, and formats keyed by name. Including root folder names helps only when those folder names differ. |
| BUG-015 | Windows can rescan after changes to unrelated files. | The watcher filters generated output and temporary files, but Windows notifications do not identify the type of entry that changed. |
| BUG-018 | Packrat does not limit the combined decoded memory used by a project. | Raster images and Aseprite documents have individual 256 MiB limits, and PNG row storage is bounded. Caches and concurrent image decoding can still use more memory in total. |
| BUG-020 | Filenames containing invalid UTF-8 are handled differently across export formats. | JSON, C#, Lua, and C output escape names. XML rejects invalid text, and LibGDX rejects names that its parser could misread. A consistent filename policy is still needed. |
Low
| ID | Issue | Details |
|---|---|---|
| BUG-009 | Display and group names are cut off at 128 bytes without an indicator. | The full names remain stored, but long names can look identical in the UI. |
| BUG-010 | A failed scan can leave the asset list partly updated. | This can happen if a memory allocation fails during the scan. |
| BUG-013 | An export failure can leave a mix of old and new files. | Packrat replaces individual files atomically, but does not replace a complete multi-file export as one operation. |
| BUG-016 | Size diagnostics can overstate the required size or lag behind settings changes. | They use full source canvases rather than effective trim bounds. The header detects source edits even when timestamps stay the same. |
| BUG-019 | APNG imports use only the first image without a warning. | Packrat needs either animation support or a warning for this case. |
Resolved since the review
BUG-021: trim offsets. Exporters that use a top-left origin now convert Packrat's internal bottom-origin Y offsets. LibGDX and Pure C keep their documented bottom-origin convention. Continue checking trim placement with asymmetric images in each target runtime.