3) No. I saw a lot of SnowBatStills, I'm not sure, may have missed one. I'll go through them again.
If you double click the results that appear in the window, it will take you straight to that piece of code in whatever object it has been found in.
Just go through them line by line and check what sprite is being assigned, what object it is in, what event etc and work out whether it is correct or not in releation to the bug.
4) I went through the debugger. I didn't check sprite_index because I couldn't find where that value was in debugger.
I already told you where it was in post #16, however you don't need to check the value of sprite_index in the debugger because we already know what it changes to from using the code BaBiA Game Studio provided earlier. We want to find WHEN it changes.
As I mentioned previously, add a breakpoint to the code inside the if block where you check for the right mouse button click, run in debug mode and click - the game will pause and the debugger window will open.
Step through the code line by line looking at the flow of execution - it will advance 1 line every time you click to step through.
At some point from here before you get to the Animation End Event you will a line of code see where sprite_index is getting changed
for this instance - note down the object this is an instance of, the event it is in and line number it is on.
If it is being set every step to the same sprite reported in the output from BaBiA Game Studio 's code then you have found the issue - or at least one occurence of it - so try commenting it out and see what happens.
If the issue isn't fixed repeat the above process until you get from the mouse click breakpoint, to the Animation End Event for
the same instance where you check for the sprite that was assigned when you clicked the mouse.
Depending on how many instances you have this could take a lot of clicks, which is another reason why I advised making a new room with just the relevant objects in - less instances executing code means less clicks stepping through the debugger and allows you to isolate the code as much as possible.
You can also press F11 (I think?) to step through - hover the button in the debugger and it should tell you the correct key as I'm just going from memory, but that may be preferable and quicker than a mouse click for you.
7) I saw you posted so I figured I'd return the favor.
Reply whenever you want there's no rush, I just checked the forum before bed so decided to reply but if you don't want to reply for a week that's all good - it's your code!