It would also require any plugs that use tags, as well as Construct to be changed.
As Julmust said, changing the animation is just as effective, and allows even more possibilities.
That depends on how they integrated the update. As long the current tags (none, stopped, walking, and jumping) remain intact it's possible to keep the current interoperability between plug-ins and older games intact.* But even if they can't alter the current Construct (or it's not worth it), this is something they should consider in designing Construct 2.0.
But really, they'd have to change Construct? Isn't that the point of feature requests? Any feature request is going to change Construct in some fashion.
Did I post in the wrong forum? Jeeze. >.<
*Those plug-ins that did rely on animation tags, if the authors didn't want to rewrite them, would could update their documentation to say that their plugins only work correctly with default tags and they aren't responsible for bugs related to using custom tags.
Edit: Anyway, I didn't meant to get into a big fight about it. It was just meant to be a friendly suggestion. : / Thanks for the suggestions. I just think usability features count as feature requests.