Describe the bug
When reading .currentframe (DEBUG(sprite.currentframe)), it returns the current frame as if they were
1-indexed. However, when setting .currentframe (sprite.currentframe = 1) they are set as if they were shifted by 1 (similar to 0-indexing, but the first element is now the last one). According to the documentation, frames are supposed to be 1-indexed, meaning that setting .currentframe uses wrong indexing.
Describe the bug When reading
.currentframe
(DEBUG(sprite.currentframe)
), it returns the current frame as if they were 1-indexed. However, when setting.currentframe
(sprite.currentframe = 1
) they are set as if they were shifted by 1 (similar to 0-indexing, but the first element is now the last one). According to the documentation, frames are supposed to be 1-indexed, meaning that setting.currentframe
uses wrong indexing.Code To Reproduce
or
Setup: