This section exists because feedback loops matter. Every plugin, rig, course, and book on anim.works gets better when the people using them share what’s working and what isn’t — so here’s how to make your posts count.
When sharing a review or positive feedback
Be specific about what worked and why. “The locomotion course was great” is nice to hear, but “the section on stride matching in Module 4 changed how I think about walk cycles” is the kind of thing that tells us what to do more of.
Share what you made. If a rig or course helped you produce something, show it. That’s the best possible review.
When reporting a bug or problem
Tag the product category so it lands in the right place — Books, Courses, Plugins, Rigs, Software, or Tutorials.
Include:
- The product name and version (if applicable)
- What you expected to happen
- What actually happened
- Your software version and OS
The more detail you give, the faster it gets fixed. Vague reports get stuck in the queue.
When requesting a feature or suggesting an improvement
Frame it as a problem you’re trying to solve, not just a feature you want. “I need X” is less useful than “When I’m doing Y, I have to Z which takes forever — would love a way to solve that.” Context helps the creator understand priority and approach.
Tagging creators
When you want to flag something directly, tag the creator in your post using @username. This pings them directly and makes sure your feedback doesn’t get lost. Use it for anything time-sensitive — bugs, critical issues, or things you really want their eyes on.
This is a space where the line between community and product team is deliberately blurry. Your feedback shapes what gets built. Use it. 