Overview
Extracts Aseprite animation tags (ranges such as idle and walk) as a List. Because tag names, frame ranges, and playback directions become data, you can automate range-based work such as processing only the walk frames.
Usage tips
- A practical workflow is to filter with
list_filter, for examplename == "walk", then usefrom_frame/to_frameto control theframeinput ofase_frame_select. - To inspect the tag structure, use
list_getto view one item at a time.
Related nodes
aseprite_load— supplies the documentlist_get/list_filter/list_map— process the tag dataase_frame_select— consumes the frame range
Read this first
tagsis aList<Map>, not text.- You can therefore connect it directly to the P08/P09 nodes:
ListGetListMapListFilter
Contents of tags
Each tag is a Map with the following keys.
| key | Type | Meaning |
|---|---|---|
name |
Text | Tag name |
from_frame |
Int | Zero-based start frame |
to_frame |
Int | Zero-based inclusive end frame |
direction |
Text | One of forward, reverse, ping_pong, or ping_pong_reverse |
repeat |
Int | Repeat count |
Basic workflow
AsepriteLoad
-> AseTags
-> ListGet
This selects one tag so you can inspect its contents.
Example
If the Aseprite document has two tags:
idlewalk
then tags conceptually contains:
[
{
"name": "idle",
"from_frame": 0,
"to_frame": 3,
"direction": "forward",
"repeat": 0
},
{
"name": "walk",
"from_frame": 4,
"to_frame": 11,
"direction": "forward",
"repeat": 0
}
]
When to use it
- To reference Aseprite tag data from the graph
- To retain only a specific tag with
ListFilter - To pass tag names or frame ranges to the UI or variants
Notes
- v1 only reads tag data.
- The tag range is
from_frame..=to_frame, including both endpoints. - Advanced workflows that edit and write tags back are planned for a later stage.