Tom's Forum Posts

    8,000 unique people tried it in the first 24 hours.

    [quote:2m609svv]Now how many of those were unique users because I opened C3 at least 10 times that first day trying to get things to work?

    Your questions are posed in an aggravating way.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Also Lamar, if you feel we've disrespected you - feel free to leave like you have suggested. No one is stopping you. At this point we'd rather be spending more time working on the software than answering the never-ending spool of questions you've been throwing at us for the last several weeks.

    I guess Tom and Ashley could tell us what the unique download or use numbers have been for C3 and that would give us at least an idea of how many people tried the beta?

    I would be interested in seeing that number?

    Like how many tried it the first day and how many new people are trying it each day?

    Here's some numbers for you:

    https://twitter.com/ConstructTeam/statu ... 2038028289

  • AFAIK a page reload won't do the trick, you have to close + open a new tab due to service workers.

    > Which threads were unjustly locked that you are referring to?

    >

    Good point, I unfairly lumped locked and closed together in one there.

    I am more so concerned about closed bugs (which I mistakenly believed were locked) which were closed simply for not fitting within the tight guidelines on bug submissions.

    How would you like us to deal with bug reports that don't meet the minimum requirements to investigate? Do you have a link to some of them that concern you?

    We talk to our customers too, it's part of our charm as a small indie team. The same applies for Scirra, not participating in the discussions just proves everyone who says Scirra doesn't listen is right, although I guess ignoring their concerns and locking their threads / bug reports does the same too

    Which threads were unjustly locked that you are referring to?

  • Support for SDK is in the new release. Documentation coming shortly, will open a Javascript SDK forum now where docs will be posted when available.

    Locking this thread, you've asked Ashley in the other thread and he will reply in due course if he feels like it. No need for another. Please bear in mind, I personally have probably spent several hours of my time replying to your questions over the last weeks. Be patient.

    All I'm going to say is yes construct has a workflow that I and many others love. I posted this thread to show that you can make great content. But the biggest concern for those of us who do complete a project is "what now?"

    Can you put it on Android? iOS? Steam? Consoles? The short answer is yes. But we now know it's way too reliant on other services and support. So regardless of how great it is to work in Construct, you have to wonder if it's worth it in the end when there are now various documented cases where a project is completed and the devs are left frustrated to the point of porting through other engines.

    We all want to see Construct succeed but we'd like to be able to succeed as well.

    Each person has their reasons for being here. I'm simply sharing my story.

    And if i didn't care, i wouldn't have said anything and just moved on

    Thank you for sharing your story, we have all read it and we appreciate you taking the time out to post it.

    I still think it's hilarious that I can't log in to the browser app. Always says unable to yada yada. I even cleared my cache several times since day 1, created a new password on the forum to use, and it still won't let me log in. "Serious" developers want to log in, amirite?

    Not aware of any issues here, submit a bug report if you're having trouble.

    Benefit of logging in via editor is it can unlock all your features if you're a licensed customer without having to fiddle with c2license.txt files. >50% of our support emails are spent with issues on the license file itself which we're hoping to significantly reduce by making the whole process easier.

    That's qualitative data on from a subset of the community. I get some people are unhappy, but we're going to try what we've planned. That's the last thing I'm going to say about the subscription pricing for now as I'd rather be getting on with working on the website.

    Addon package is an interesting idea but it's not on the road-map for now. The export to mobile options we're building for C3 rely on external servers which have cost to keep running so any addon would have to be subscription based.

    What data is that Tom?

    In our database and analytics

    Where is the thread with glowing reports and requests for a browser based subscription engine?

    Are you suggesting that because you think people don't want a browser based engine, we should just bin it and start again? Or is your complaint only about the fact it's subscription based?

    To the few people above that said they will get C3 for a year just long enough to export their C2 projects I suggest you look at the bug reports.

    It's first week of the public beta, this is all expected. Re-judge the state of it when we launch.

    I think if they had been a bit more strategic and less secretive about the whole thing they wouldn't now be stuck with a huge alienated userbase and a product that doesn't fit. Had they openly asked the community what they thought of a browser based subscription system, they would probably get much of the same answers they're getting now and they wouldn't have wasted all that time investing in it.

    There are obviously some users who don't like our direction, but to call our user-base alienated is hyperbole. Secondly, we haven't wasted all our time investing in this. We're receiving a lot of positive feedback as well.

    [quote:rmtbfn9i]They have also been offered many well thought out suggestions for tailoring their subscription system so that it is win win for both their customers and themselves and these seem to fall on completely deaf ears. It's one thing to have a vision and stick to it, but there is also stubbornness and pride and if they could drop some of that we'd probably all end up with a better product.

    It's not falling on deaf ears. We're going to execute what we've planned, and what our data shows us is this a rational path. To change direction before we've even tried the model would be irrational. We were obviously expecting some users to not like the model.