This also happens in C3.
If you set the speed of the current animation in events, this speed will not be remembered if there is a change and a return to the animation from which the speed changed.
Changing the speed of the current animation in events only serves for the current cycle of the animation, then the speed values set in the editor will be taken again.
In this gif you can see that by pressing Enter I change the speed of the animation when the sprite has the green animation, then the sprite changes to the blue animation, again the sprite returns to the green animation and now the speed is again the initial.
Attach a Capx
https://www.dropbox.com/s/pt60jrqiuyv7e ... .capx?dl=0
Description of Capx
The capx includes a sprite object with two animations.
Every 3 seconds the animation is alternated between these two animations.
Steps to Reproduce Bug
The speed change set in events is not fixed and will be forgotten when the animation is displayed again.
This prevents that at the beginning of a program you can configure the speed of your sprites in events.
Then you only have the possibility to configure your speeds in the editor.
A change of speed of the animation in the events must be fixed and be remembered for future visualizations of the animation.
Operating System and Service Pack
Construct 2 Version ID
Develop games in your browser. Powerful, performant & highly capable.
Here there is no error and with logic everything is in order.
Animations can have different speeds and preferably do not enter it all the time.
This is currently by design. Changing the animation restores the animation speed. There is also a backwards-compatibility risk to changing this since existing projects may depend on the way it currently works.
In my opinion it is a flaw in the design.
The speed should be permanently changed but I understand that it can not be modified because it affects other projects.