Construct in 2022: year in review

You're viewing a single comment in a conversation. View all the comments
  • 3 Comments

  • Order by
    • [-] [+]
    • 0
    • Ashley's avatar
    • Ashley
    • Construct Team Founder
    • 0 points
    • *
    • (2 children)

    Remember the 41 suggestions excludes loads of work done elsewhere. For example you recently requested some improvements to the Project Bar - that was done but counted as bug fixes. It also includes features that were difficult and time-consuming to implement, but still count as just 1 suggestion. Further, it's always easy to write, "you should have done more". If we did 100 suggestions, someone could write, "you should have done 200". If we did 200, someone could write, "you should have done 400". It's easy to write such things. It's much harder to do it.

    • [2/2] The thing is we can't add missing ACE or fix editor issues ourself, all we can do in those situations is taking the time to fill suggestions and bug reports and remind how important this is for us in our daily use of the engine. Really hope the priority will continue to grow regarding community suggestions. As you know it's because C3 is our main professional tool that we are so involved and sometimes voice our concerns.

      I wish your team a happy festive season!

    • [1/2] I know there is nothing easier than throwing and writing ideas. As i often say i'm thankful for a bunch of additions you made this year, some of them involved a lot of works and are real gamechangers. I love how fast bugs are handled and I agree that great progress was made this year regarding implementing community suggestions and you managed to prove some of our concerns were wrong. Indeed I had the luck to see some of my suggestions integrated in the engine. (both in the platform, in bug reports, on twitter). So i'm probably not exactly the right person to ask for more and I really don't want to sound ungrateful for your work. I know how much i owe Scirra for my previous and upcoming projects.