Animator Request: Custom Tags

Hi-

I was just requesting that the platform tools included with construct also allowed us to create, modify, use in expressions, and assign to controls (or custom platform states) custom animation tags, instead of being locked into stopped, none, walking, and jumping.

If you try to use the tags it seems to interfere with attack animations or alternate animations because of the way the Platform tools default to stopped. I'm basically having to recreate what the Platform system does automatically with tags to avoid it. I'm setting all my tags to none and then using the event editor to change animations.

Thanks,

Zomd

Edit: Thinking about this more, creating custom (and accessible) Animator tags for a given sprite object is basically integrating handling sprite (or character states) into the platform tools. It could at least be used that way.

Well, the default tags have higher priority over any custom tags you assign animations. So, if you have a guy standing with "stopping" it will override any custom tag you have because it's jacked in directly so to speak.

So, don't use the default tags. You will actually be hampered by it. Just do it by yourself -- it's very easy! Assign "animations names" and use them instead and don't use the tags.

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.

Well, the default tags have higher priority over any custom tags you assign animations. So, if you have a guy standing with "stopping" it will override any custom tag you have because it's jacked in directly so to speak.

So, don't use the default tags. You will actually be hampered by it. Just do it by yourself -- it's very easy! Assign "animations names" and use them instead and don't use the tags.

The nice thing about animation tags (not names) is exactly that, the included platforming tools handles those changes for you. That's the point of my request, extending how smart the platforming tools are to include custom tags and automatically handle those changes.

Yes, I can go through and use the animation names to make the changes by using the none tag and redoing all that logic in event layout or a python script. It's annoying busy work that the framework of sprite objects, platforming behavior, animator and tags should be able to eliminate. Custom tags is basically the next logical extension of their included tools.

So in other words, I'm not asking for help in how to do it. I've mostly figured that out (with the exception of some minor problems with secondary objects keying off the first sprite objects animation). I know it's possible without using tags. Rather this is a feature request to naturally extend the existing framework and concepts in a direction they are already going and make construct more user friendly and intuitive in the process.

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.

As far as feature requests go, sure bring em on, but its kind of late in the game for changes that may interfere with a 1.0.

Construct 2 is another story.