Pricing suggestion.

0 favourites

    Keep the subscription, with a catch.

    $100 a year. This gets you 1 year of updates and support. It also gives you construct 3 permanently up to the version until your subscription runs out.

    After a year, if you want further updates and support you must pay for that annual subscription again. Otherwise you can continue using the version up to when your subscription expired.

    Personally, that's the only way I can see myself supporting construct 3. I don't use construct as much as I used to. But I love using it for very quick prototyping. Occasionally I'll do a full project in construct, but the exporter issue always bothers me because the mobile market is so massive.

    I simply can't justify $100 annually on something I won't use all time.

    On top of that, I still haven't seen any big changes construct 3 immediately brings to the table that construct 2 is lacking.

    100€ per year is not much at all if you ask me. If you get professional tool with constent updates and healthy community for support its a fair price in my opinion. Plus dont rush, there is still time and who knows what scirra will be reavealing in the near feature. BB engine charges 99€ per month and trust me its not even close to construct 2.

    I think this would be really fair pricing system.

    100€ per year is not much at all if you ask me.

    It isnt much at all, but I really admire the communities passion on these forums the past 48 hours.

    Scirra have done the research, done the math, and they know the target number of subscribers they need. They havent just pulled the idea out of a hat. No amount of anger, petitions or people threatening to leave is going to change anything.

    People here dont even know what they are getting for $99 yet.

    I simply can't justify $100 annually on something I won't use all time.

    That's just a personal thing for you then. If you are using it more than once a year then you will find that the $100/year becomes more reasonable.

    100€ per year is not much at all if you ask me. If you get professional tool with constent updates and healthy community for support its a fair price in my opinion. Plus dont rush, there is still time and who knows what scirra will be reavealing in the near feature. BB engine charges 99€ per month and trust me its not even close to construct 2.

    I've had construct 2 for like 5-6 years now?

    That would be $500+

    That's $300+ I would rather put towards art assets, sounds etc.

    Like I said, myself, I'm not using construct daily. It's mostly a prototype tool. I would LOVE to develop full games with it but no exporters has really hurt my development. It seems intel and cocoon always have some issue or another.

    If I was a daily construct user. My income was coming from my use of construct 2, yes $100 a year isn't much, I still wouldn't like it but I would be fine with that price. For everyone else that isn't a daily user or isn't selling their work from construct 2 the subscription model is incredibly hard to justify.

    I've had construct 2 for like 5-6 years now?

    That would be $500+

    So by your own reckoning youve had 5-6 years of bug fixes and improvements, all for one price. Thats not bad value.

    Like I said, myself, I'm not using construct daily. It's mostly a prototype tool. I would LOVE to develop full games with it but no exporters has really hurt my development. It seems intel and cocoon always have some issue or another.

    So does every other game making platform. There has never ever been a service or workflow that has been 100% bug free all the time. Its impossible. I will admit you have to wrestle with packaging services quite a bit, but that isnt 100% on Scirra.

    If I was a daily construct user. My income was coming from my use of construct 2, yes $100 a year isn't much, I still wouldn't like it but I would be fine with that price. For everyone else that isn't a daily user or isn't selling their work from construct 2 the subscription model is incredibly hard to justify.

    Ill say it again and again: Theres no gun pointing at anyones head. Continue using C2 or the free C3. The only people here that stand to lose anything with the subscription model is Scirra.

    >

    > I've had construct 2 for like 5-6 years now?

    >

    > That would be $500+

    >

    >

    So by your own reckoning youve had 5-6 years of bug fixes and improvements, all for one price. Thats not bad value.

    >

    > Like I said, myself, I'm not using construct daily. It's mostly a prototype tool. I would LOVE to develop full games with it but no exporters has really hurt my development. It seems intel and cocoon always have some issue or another.

    >

    So does every other game making platform. There has never ever been a service or workflow that has been 100% bug free all the time. Its impossible. I will admit you have to wrestle with packaging services quite a bit, but that isnt 100% on Scirra.

    >

    > If I was a daily construct user. My income was coming from my use of construct 2, yes $100 a year isn't much, I still wouldn't like it but I would be fine with that price. For everyone else that isn't a daily user or isn't selling their work from construct 2 the subscription model is incredibly hard to justify.

    >

    Ill say it again and again: Theres no gun pointing at anyones head. Continue using C2 or the free C3. The only people here that stand to lose anything with the subscription model is Scirra.

    Yes, I had 5/6 years of updates for one cost. That's the pricing model that works for me.

    I'd rather pay upwards to $300 upfront for a permanent lifetime license than subscribe.

    I subscribe to cable and Internet. Not the programs on my computer.

    Correct, even unity has bugs from time to time. The fix is as easy as picking and sticking to a stable build and not updating unless you need to. At that point, nearly any risk of an unexpected bug/problem is eliminated.

    Construct, you have many different areas for problems. 1. Construct can be the problem. 2. Cocoon could be your problem. 3. Maybe intel is the issue or switching from one to the other fixes the issue. 4. Maybe it's just a browser issue that doesn't support something.

    Well, you can't fix people's browsers, so that becomes a waiting game.

    Scirra isn't developing for cocoon or Intel etc...so that's a waiting game on those guys and that's if they are actually the issue and not construct somehow being an issue for them. Etc etc. the list goes on.

    Things have gotten much better performance wise over the years but there are still constant bugs and issues, more so than I've had with any other game engine. That's a huge red flag and problem.

    Even as I write this, isn't there currently a major issue with audio working on IOS?

    And scirra can't fix that because it's third party.

    Go and use something like unity or game maker and the issue doesn't exist.

    I absolutely love construct for its speed in development and prototyping. I hate it with a passion for its reliability.

    Finally, I made it pretty clear I'm going to continue to use construct 2. This isn't about that though. The point is if Scirra as a company wants my continued $$$ they will have to re-think and consider a few things.

    With all the threads about this it becomes pretty clear I'm not alone in that mindset.

    If you compare to the competition, game maker 2 beta is available now. Buy once. Native export to all platforms.

    Unity, free with nearly all features. Paid only when you start making money.

    Unreal, free with royalties.

    Godot. Free.

    Clickteam. Pay once.

    Agk pay once.

    $100 a year isn't much.

    But then again, Netflix doesn't cost much either.

    How does Netflix make money? People subscribe. Pay monthly or whatever. And don't use the service.

    Subscription models nickel and dime the consumer knowing they won't use the service full time and stay subscribed for the occasional time they do use the service. Or if you unsubscribe you eventually will re-subscribe.

    Subscriptions are a disgusting price model and I personally don't get value out of a subscription model.

    Software subscriptions mostly work for studio environments where the software is used consistently all the time by a business to make money. That pricing model works against individuals.

    Just charge much more than $200 to buy it and let people pay it off slowly each month.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

    Fundamentally it's not whether or not the price is reasonable. It is for what it is. But it's encouraging and perpetuating a business model that at the end of the day is harmful (in the long term) to content creation and users. A huge concern with rental models such as the one proposed is that the content you create will no longer be accessible to edit if the host company goes bust. Who knows if Scirra will even be around in 5 or 10 years (I do hope they are), but if they fold and take with them all those cloud services (as I understand it, so correct me if I'm wrong) we may never be able to edit our projects again. People who follow trends and try to make a quick buck by churning out games won't care, but for some of us we're pouring our hearts and souls into these projects, and trying to make not just games but art so it is VERY important on a personal level to be able to revisit this stuff, even if the technology it was built on has long since been superseded. The rental model seems geared toward fast development cycles intended to only follow trends and make a quick buck. I need something more permanent, and unfortunately if C3 can't accommodate for that it won't have any future with me.

    The $99 per year price is fair IF you a making use of the exporters (now Cloud Compilers) and looking to make a profit BUT if you're a hobbyist who only uses the editor intermittently but wants access to all the features of the Editor and only uses the web and Scirra Arcade export options (available in the free version) to show off to friends, it's hard to justify an annual cost.

    I suggested elsewhere that instead of kicking us back to the limited free version of the Editor after the subscription ends, we instead retain full access to the Editor so we can still work on our games and just lose access to exporters - even if that means a slight increase in the initial cost.

    Initial Payment $149 = Lifetime access to full features of Editor + 1 year Export License

    Further Payments $99 = 1 year Export License

    Keep the subscription, with a catch.

    $100 a year. This gets you 1 year of updates and support. It also gives you construct 3 permanently up to the version until your subscription runs out.

    After a year, if you want further updates and support you must pay for that annual subscription again. Otherwise you can continue using the version up to when your subscription expired.

    Personally, that's the only way I can see myself supporting construct 3. I don't use construct as much as I used to. But I love using it for very quick prototyping. Occasionally I'll do a full project in construct, but the exporter issue always bothers me because the mobile market is so massive.

    I simply can't justify $100 annually on something I won't use all time.

    On top of that, I still haven't seen any big changes construct 3 immediately brings to the table that construct 2 is lacking.

    I suggested this and others have suggested it as well, but Ashley and Tom have very firmly decided to keep on course with the model they have announced - selling us a trial version of their next software

    Once your subscription period ends - you can no longer edit your projects if they were made in construct 3

    Once your subscription period ends - you can no longer edit your projects if they were made in construct 3

    As far as I know (correct me if I'm wrong) that hasn't been cleared yet. We only know that we'll have full access till the next billing is due. That can mean we'll have some limited access after that (for example not being able to access the cloud, only local files). I'm just speculating of course, but they did say that they don't want to hold our projects hostage.

    > Once your subscription period ends - you can no longer edit your projects if they were made in construct 3

    >

    As far as I know (correct me if I'm wrong) that hasn't been cleared yet. We only know that we'll have full access till the next billing is due. That can mean we'll have some limited access after that (for example not being able to access the cloud, only local files). I'm just speculating of course, but they did say that they don't want to hold our projects hostage.

    I believe Tom said that the free version can open any project in read only mode, when discussing what happens when your subscription ends.

    If you could still edit them, just not export to anything other than what the free version can or access cloud services, then my objections to the subscription are lessened, but don't think that is the case.

    As it stands, you can only edit projects that exceed the free edition limits if you have a valid license.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)